TO find Hostname /IP Address

http://www.hcidata.info/host2ip.cgi

Oracle Password Crack

http://www.petefinnigan.com/tools.htm

Default Oracle DB Password

Connected to: Personal Oracle9i Release 9.2.0.1.0 - Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.1.0 - Production SQL> @\petefinnigan.com\password\marcel-jan\osp_exec.sql ********************************************* * * * Welcome to the Oracle Security Probe * * * ************************************* Connectstring (destination database): sans Password of oraprobe?: Connected. Oracle accounts with default passwords ====================================== Username: SYS Password: CHANGE_ON_INSTALL ----------------------------------------------- WARNING! The password of SYS is a default password. It is well known to hackers Additional information: SYS is Oracle's most powerful database management account. It allows to read, change and destroy all data in your database. Username: SYSTEM Password: MANAGER ----------------------------------------------- WARNING! The password of SYSTEM is a default password. It is well known to hackers Additional information: SYSTEM is Oracle's database management account. It allows to read, change and destroy all data in your database. Username: SCOTT Password: TIGER ----------------------------------------------- WARNING! The password of SCOTT is a default password. It is well known to hackers Additional information: This is a training account. It should not be available in a production environment. Username: DBSNMP Password: DBSNMP ----------------------------------------------- WARNING! The password of DBSNMP is a default password. It is well known to hackers Additional information: DBSNMP is an account for the Oracle Intelligent Agent. Under certain circumstances it allows to read passwords from memory. Username: QS_ES Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED(TIMED) ----------------------------------------------- WARNING! The password of QS_ES is a default password. It is well known to hackers Additional information: This is a training account. It should not be available in a production environment. Username: WMSYS Password: WMSYS Status: LOCKED ----------------------------------------------- WARNING! The password of WMSYS is a default password. It is well known to hackers Additional information: Username: ORDSYS Password: ORDSYS Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of ORDSYS is a default password. It is well known to hackers Additional information: The account ORDSYS (Oracle Time Series) has a limited number of risky system privileges, amongst which those to use external libraries and run code on the operating system. Username: ORDPLUGINS Password: ORDPLUGINS Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of ORDPLUGINS is a default password. It is well known to hackers Additional information: ORDPLUGINS is an administrative account for Oracle Time Series. Username: MDSYS Password: MDSYS Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of MDSYS is a default password. It is well known to hackers Additional information: The account MDSYS (Oracle Spatial administrator) has DBA-like privileges, which allow to read, change and destroy all data in your database. Username: CTXSYS Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of CTXSYS is a default password. It is well known to hackers Additional information: CTXSYS (Oracle Text/Intermedia Text/Context option) is an account with DBA privileges and therefor allows to read, change and destroy all data in your database. Username: XDB Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of XDB is a default password. It is well known to hackers Additional information: Username: WKSYS Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of WKSYS is a default password. It is well known to hackers Additional information: WKSYS is an administrative account of Oracle9iAS Ultrasearch. Username: WKPROXY Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of WKPROXY is a default password. It is well known to hackers Additional information: WKPROXY is an administrative account of Oracle9iAS Ultrasearch. Username: ODM Password: ODM Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of ODM is a default password. It is well known to hackers Additional information: Username: ODM_MTR Password: Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of ODM_MTR is a default password. It is well known to hackers Additional information: Username: OLAPSYS Password: MANAGER Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of OLAPSYS is a default password. It is well known to hackers Additional information: OLAPSYS is an administrative account for the OLAP Services option. Username: RMAN Password: RMAN Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of RMAN is a default password. It is well known to hackers Additional information: RMAN is an account for the Oracle Recovery Manager. This account might be misused to write unwanted changes to the database to the backups. Username: QS_CS Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of QS_CS is a default password. It is well known to hackers Additional information: This is a training account. It should not be available in a production environment. Username: QS_CB Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of QS_CB is a default password. It is well known to hackers Additional information: This is a training account. It should not be available in a production environment. Username: QS_CBADM Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of QS_CBADM is a default password. It is well known to hackers Additional information: This is a training account. It should not be available in a production environment. Username: QS_OS Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of QS_OS is a default password. It is well known to hackers Additional information: This is a training account. It should not be available in a production environment. Username: HR Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of HR is a default password. It is well known to hackers Additional information: This is a training account. It should not be available in a production environment. Username: OE Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of OE is a default password. It is well known to hackers Additional information: This is a training account. It should not be available in a production environment. Username: PM Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of PM is a default password. It is well known to hackers Additional information: This is a training account. It should not be available in a production environment. Username: SH Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of SH is a default password. It is well known to hackers Additional information: This is a training account. It should not be available in a production environment. Username: QS_ADM Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of QS_ADM is a default password. It is well known to hackers Additional information: This is a training account. It should not be available in a production environment. Username: QS Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of QS is a default password. It is well known to hackers Additional information: This is a training account. It should not be available in a production environment. Username: QS_WS Password: CHANGE_ON_INSTALL Status: EXPIRED & LOCKED ----------------------------------------------- WARNING! The password of QS_WS is a default password. It is well known to hackers Additional information: This is a training account. It should not be available in a production environment. SQL>

Longtime pending comparison - SharePoint 2007 and LiveLink

Of late, I am extensively working on 2007 but LiveLink is the leader in our company.

SP 2003 and MOSS 2007:
------------------------
the less said the better about 2003. so i will jump to 2007.

1. MOSS enterprise edition a gimmick. I can as well build a .net interface to SAP/SIEBEL/etc systems and talk with MOSS to storing content from my application. BDC does not give anything new except to have a placeholder in enterprise edition.

2. Same with excel services. It is a good tool, but I can suppose we can do the same thing in .net in very easy fashion.

3. Same with advanced info path forms. I can as well as build a .net app and talk to sharepoint. Why bother to buy enterprise edition at all?

4. So enterprise edition does not give anything new except to make money for our beloved Mr.Softee.

5. Scalability a huge issue. Also even if your data reaches 1TB, you have to put in place a strong dba, a strong administrator and a strong architect just to keep things going. These guys cost easily close to 100 per hour each and they constantly move for better billing rates!!!!

6. If you are looking at 5TB to 20TB (a fairly medium, i wont say big because big means greater than 50TB as LiveLink installations continuously notch up huge installations), then you are seeing a mess of front end's and application servers.

7. If you touch anything then it is a .net work and that means a dedicated sharepoint developer.

8. Storing all content within the db is shocking. Imagine maintaining 2TB database for even basic document management storage!!!! Whoa.. dba where are ya!!!!

9. One good thing is UI in 2007 is good. But most content/doc mgmt system's user interface has dramatically improved in their latest versions. This includes Documentum 5 and 6 and LiveLink 9.2, 9.5 and 9.7

LiveLink:
--------------
1. A massively scalable system with relatively small server footprints.

2. No need to even have an admin to be present once you get the infrastructure and modules in place.

3. Zero dba needed. Zero architect needed after inital work.

4. Very very very very low maintenance baby.

5. Can scale massively to ten's of terrabytes of data with just small footprint of front end web servers. Content stored externally means zero database worries.

6. Neat UI in their latest version a huge advantage

7. No standard/enterprise edition gimmicks

8. Strong support from even basic OpenText support. cheap becomes cheaper.

9. Licenses can be negotiated as low as $100 per user license.

10. Can be easily exposed to extranet's/internet via their servlet option.

11. OScript is a rare skill but with few API's to catchup, a developer can easily be trained on this.

12. Perhaps the most powerful workflow engine out there among cont/doc mgmt systems.

If I were to recommend, I will do LiveLink over anything. I have not worked in Documentum and so cannot comment on it.

Enterprise Service Bus (ESB)

Distribute information across an enterprise quickly and easily.
Mask differences among underlying platforms, software architectures, and network protocols.
Ensure information delivery even when some systems or networks may go off-line from time to time.
Re-route, log, and enrich information without requiring applications to be rewritten.
Provide incremental solution implementations so all enterprise services and applications need not change immediately or all at once.

A new term has appeared in the field of application integration: the "Enterprise Service Bus" (ESB). This term was used by the Gartner Group to define a new type of application integration middleware: "An Enterprise Service Bus (ESB) is a new architecture that exploits Web services, messaging middleware, intelligent routing, and transformation. ESBs act as a lightweight, ubiquitous integration backbone through which software services and application components flow." (Source: Roy Schulte, Gartner)

This definition is very similar to that of "Enterprise Application Integration" (EAI) tools, apart from three significant terms, which we shall come back to later: Web services, ubiquitous and lightweight.

Enterprises are only just starting to measure the impact of application integration on their information systems and organization. The more advanced companies have recently started deploying EAI solutions or have launched pilot projects. Given the speed with which trends seem to succeed each other, it is not unreasonable forus to wonder whether the ESB concept is actually a legitimate one.

The emergence of the ESB Concept is closely linked with the lasting trends that have been slowly transforming the EAI market for the last few years: standardization of infrastructures with J2EE, Microsoft .NET and Web services, and the redistribution of roles of integration software component vendors.

In this article, we shall look at the motivations behind ESBs, and their likely impact on the middleware and software market.

What's wrong with traditional EAI solutions?

An EAI solution is designed to integrate applications according to the principle of loose coupling, whereby applications can, to an extent, evolve and operate independently from one another. The stack of middleware usually provided by EAI solutions includes:

Connectors, able to introspect the data model and services of a given application, and to open them up to other applications connected to the EAI bus. A connector generally handles some or all of the following tasks: authentication, transaction, conversation management, security context, rights management, and so on.
Asynchronous middleware (or bus) which handles guaranteed asynchronous delivery of messages for applications connected to the bus. Security aspects are also managed by this layer.
Service manager, able to apply added-value services handled by the integration architecture and not the functional side of applications (e.g. routing, message transformation, transcoding, etc.)
Process manager, able to orchestrate inter-application message exchanges in order to execute business processes. The presence of a human workflow tool is also desirable here.
Repository, to guarantee consistency and configuration of components deployed in the EAI solution.
Administration console, able to supervise the operation of technical components in the EAI solution, along with business processes.

Vendors of EAI solutions have, through their R&D investments and, more often, through external acquisitions, managed to feature the full abovementioned middleware stack in their solution. Functional richness is therefore not a concern for enterprises investing in this type of solution.

However, EAI solutions are criticized for certain shortcomings:

Proprietary development interfaces: The integration logic (process, transformation rules, workflow services, etc.) cannot today be ported between EAI solutions. This fact means that enterprises are closely linked to vendors with regard to a structural aspect of the IS, sends the price of specialized consultants through the roof, and weakens the durability of integration-related developments.
Proprietary communication protocols: Although there is no difficulty in transferring and monitoring messages within an EAI solution deployed on a wide scale, the same does not hold true between EAI solutions from different vendors. At present, it is not possible to supervise a business process from end to end if it's executed on two separate EAI platforms. While the SOAP/HTTP does provide a bridge between EAI solutions for interoperability, it only tackles the rudimentary issue of the sessionless RPC, overlooking the other fundamental architecture services, (security, guaranteed delivery, etc). This limits interoperability between two enterprises with different EAI solutions.
Lack of consistency between application servers and EAI solutions: Vendors often put forward the argument that connectors are able to integrate existing applications without altering their code. This is true. However, the fact that an application communicates with an "intelligent" network often impacts on its functional scope, which often needs to be improved. For example, an application may have to communicate with the EAI workflow manager, or simply deliver a message to a remote server connected to the EAI solution's bus after a transaction has been executed. Interfaces for access to integration services via application servers are often proprietary (e.g. in the form of C or Java APIs). Some standard XML interfaces may be available, such as SOAP/HTTP, but are still too rudimentary to fully meet requirements.
Excessive license cost: The main EAI vendors base their strategy on functional richness. The resulting high R&D costs lead to high prices, which make EAI solutions inaccessible to all but the large corporations. An EAI middleware stack is also voluminous (e.g. number of connectors), and costly to maintain.
Lack of scalability: Most EAI solutions have based their architecture on the principle of a centralized, hub-and-spoke architecture. Expanding an EAI architecture on a large scale becomes difficult with this model. The move to a bus-type architecture, which deports all or part of the central integration logic to "smart" connectors based on a distributed asynchronous middleware, has nonetheless been achieved by the leaders on the EAI market. We should point out, however, that a bus architecture is more complex to deploy and administer, but can also be configured as a hub & spoke architecture.

Fig 1: Moving EAI solutions from the hub & spoke topology to the bus topology

Fig 2: Break in QoS between EAI solutions from different vendors

In addition to the problems related purely to EAI solutions and the other standards in force, difficulties may arise in relation to the design and implementation of this type of architecture. For example:

Difficulty reconciling the data models and security models of each application
Difficulty making the application modules of an architecture functionally independent, in the form of components
Communication difficulties between the different teams involved in an EAI project
Political difficulties relating to redistribution of power caused by the urbanization of the IS
Difficulties for developers and administrators to integrate a new architecture paradigm, in an economic context marked by reduced budgets and workforce

For these reasons, "35% of EAI projects are not completed in accordance with deadlines and budgets", estimates Forrester Research, and the term "EAI" is has found itself the blacklist of buzzwords that IT managers no longer want to hear. Many EAI solution vendors have also banned this term, to replace it with others such as "application integration", "integration architecture", etc.

Whatever the term or the technology used, the problem of application integration remains a difficult, long-haul affair. Strictly EAI-related difficulties can nonetheless be resolved by vendors and standardization bodies. The market does seem to be moving in this direction, giving rise to a new time of software: ESBs.

ESBs, or the quest for the universal integration middleware

Before we look at the market solutions that claim to offer ESBs, let us sketch out the ESB in its fullest form (able to meet both the internal and external integration problems of enterprises).

The diagram below shows an ESB. It does not invent any new architecture concepts, but instead uses standard Web services interfaces between its components, thus differentiating it from a proprietary EAI solution:

Web service-compatible integration server: An application wishing to invoke a component on the network or expose its services on the network will do so via an integration server designed for the purpose. Quality of service aspects relating to the service's exposure on the network will be declared by the application, and managed transparently by the integration server.
Standardized interfaces between applications and the integration server: An application created using a given language can invoke the services of the integration server (e.g. delivery of a message to the server http://ACME.com:5555/endpoint1 delivered once only, Triple DES encryption and request for notification of receipt, in the context of a distributed transaction). This service is requested using a standard API linked to the language used (e.g. Java, C# or Perl), which isolates the application from any proprietary integration server API.
Standard Web service communication protocol which natively integrates the notions of quality of service which are essential for wide-scale application integration (confidentiality, integrity, non-repudiation, guaranteed delivery, transaction, sessions, administration, etc). This 100% XML protocol makes it possible to progressively integrate other integration servers in the architecture, from other vendors, and to integrate a network of compatible servers from a partner, without harming quality of service. This is where the notion of "ubiquity" comes in, as put forward by Gartner.
A container for Web services and orchestration incorporated in the integration server mentioned above, in order to support various components relating to the integration logic (message transformation, enrichment, management of long processes, etc). These components are additional standards for Web services, which isolates them from the proprietary aspects of the container.
A standard administration protocol, enabling a third-party administration console to supervise a Web-Service compatible server or a network of Web service servers, thanks to a standardized XML administration protocol.

Fig 3 : The complete ESB middleware

This holy grail of the "universal middleware" has been sought many times - just think back to DCE or CORBA, which encountered many problems. The concept of ESB is another attempt to achieve this ideal, and there are three reasons why ESB has a good chance of meeting its goal, at least to an extent:

Application integration is today at the heart of many strategic interests: e-CRM, extended enterprise, automation of business processes, etc.
The route followed by Web service standards takes a bottom-up approach: the layers in the Web services stack may be used as required, according to their maturity. The basic technical line-up of SOAP-WSDL/HTTP limited to the RPC, will be gradually extended by optional functions. This pragmatic approach is encouraging, and will enable many companies to avoid needless complexity ¯ hence Gartner's use of the term "lightweight".
The XML language is used at the heart of Web services: Web services are based on the W3C's XML schema recommendation, which is unanimously supported by the middleware industry.

So, the ESB architecture is inventing nothing new, offering something as standard that has been offered for years by proprietary middleware. The success of the ESB will therefore depend on the market's ability to deliver reliable Web service standards, and truly interoperable implementations.

The stack of Web service standards is still a house of cards...

It is usual to associate Web services with the SOAP/WSDL/UDDI standards trio, together with HTTP. This trio only resolves basic application integration problems, i.e. the notions of service contract, stateless RPC and directory. Below is a list of the architecture services required by ESBs, as well as the solid standards proposed by the main standardization bodies and vendors:

Service	Related standard(s)
Transport	HTTP
Messages	SOAP
Service contract	WSDL
Directory	UDDI
Delivery guarantee	HTTPR, WS-Reliability, ebXML Messaging Service
Graphical interface	WSUI, WSIA, WSRP
Encryption	XML Encryption, WS Security
Signature	XML digital Signature, WS Security
Single Sign On	SAML
Access control list	XACML
Transaction	BTP, XAML, WS-Transaction, WS-Coordination
Management of public/private keys	XKMS (XKISS, XKRSS)
Process representation	BPEL, BPML, XLANG, WSFL, WSCI, WS Choreography
Administration	OMI
XML dialects of business messages	fpML, CML, etc
XML dialects of business processes	RosettaNet, etc

This overview is incomplete, it being difficult to give a complete list of standards as they are issued by a number of different standardization bodies (the most active being the W3C and OASIS) or vendor consortiums (IBM, Microsoft, BEA, Sun, etc). Many standards meet head-on in competition, and a number of them are likely never to be implemented. All these standards are playing for huge stakes, as they are the key to the adoption of Web services, and therefore to the rise in sales of compatible middleware.

The standardization bodies therefore see very ambiguous relationships playing out between software vendors. A consensus is required in order to establish standards that will send software sales skyrocketing, and every vendor is trying to use their powers of persuasion in order to get a head start when it comes to implementation. The battle will be even tougher given that standardization will no doubt be followed by the appearance of open-source solutions, to the great advantage of customers and service companies.

Still missing from the Web services implementations on the market are the vital standards covering the guarantee of asynchronous message delivery and security. The HTTPs standard does not provide high enough security for Web services and the RPC connotation of SOAP/HTTP contradicts the notion of loose coupling on which Web services are based. The Reliable Messaging and Web service Security standards (in particular, based on XML Digital Signature and XML Encryption from the W3C) from the OASIS are excellent candidates to address these issues, and are likely to enable Web services to take off. While it is true that the other standards are important, they do remain secondary in terms of requirements.

The propagation of standards will inevitably be followed by a streamlining of middleware vendors, and a redistribution of suppliers' roles...

The impact of ESBs on the integration middleware market and on software vendors

The current vision of an integration solution whose components come from the same middleware vendor has now been overturned. Standards, which are more or less mature, are converging towards a "compound" view of the ESB, which will be an assembly of software components from specialized vendors:

Connector standards will make it possible to obtain an application connector from the vendor best positioned to develop it (e.g. Oracle DBMS JDBC connector from Oracle Corp, JCA R/3 connector from SAP, JCA CICS connector from IBM, etc). Part of the integration middleware market will then legitimately fall into the camp of specialized system and software vendors.
Administration standards will enable integration platforms to be administered from an external environment such as Patrol or TNG,
Business process standards will make it possible to use third-party process managers, orchestrating Web services and workflow, based on a standardized Web service bus
Messaging standards will make it possible to free oneself from the asynchronous middleware used, which will become interchangeable
... and so on..

We are already seeing vendors of EAI solutions leaving the connector market and moving towards application servers. The asynchronous messaging system is also becoming a commodity component. Examples of such positions are multiple: WebMethods is opening its system to J2EE JBoss and is clearly putting its money on Web services, SeeBeyond is offering a new version of its architecture, called ICAN, completely based on JCA and compatible with J2EE application servers and the latest Web service standards, Vitria is integrating the Tomcat server, Sonic Software has based its integration solution on Web services, XSL, JMS and JCA. Some newcomers such as SonicXQ or Kenamea are already embryonic forms of ESB. We should point out that, on the whole, application and asynchronous messaging system vendors are very well placed to address the ESB market. BEA's solution is a good example of a unified middleware stack handling different integration problems. The limits between application servers, message-oriented middleware and EAI solutions will therefore fade.

As well as the creation of connectors, the software market is also undergoing a gradual, profound transformation. The strategic turnaround by Siebel illustrates this trend particularly well. Instead of deploying its business components in a confined technical environment, Siebel will extract the business processes from its software package in order to deploy them in standard form in EAI and Web services environments, so as to resolve the integration problems traditionally encountered in CRM projects. To do this, Siebel is using partner integration solutions, particularly those of WebMethods and SeeBeyond. SAP is also following a similar approach with its xApps, although it is less clear on the technical architecture that will be used. JD Edward and Peoplesoft have not escaped the tidal wave, and are respectively offering EPI (Extended Process Integration) and AppConnect. The gradual disappearance of barriers between applications will bring some vendors to reconsider their functional scope. A new hand looks likely to be dealt...

The vision of an ESB that we describe in this article will take some time to become reality, as experience has shown that this type of architecture takes a long time to standardize. The future of EAI solutions, in their current guise, is far from certain. ESB is therefore a lasting movement which falls into the architecture standardization logic that began with J2EE and .NET, and is continuing with Web services.

Nonetheless, neither ESBs nor EAI can reduce the crucial analysis phases that must come prior to any integration project, in order to study the urbanization of the information system. Initially, and if feasible, it would therefore be reasonable to embark on these analysis phases, without investing too much in over-extensive integration solutions, and to start building the foundations that will one day hold an ESB.

Vork - Open Source PHP

Vork is an open-source PHP framework designed for rapid development of performance-oriented scalable applications.

The mission of Vork is to provide an MVC architecture and full-featured toolkit in a gimmick-free no-frills approach without adding overhead, creating slow abstraction layers or re-inventing native PHP functionality.

Rapid Application Development

Native PHP interface with intuitive naming convention, no need to learn new terminology or syntax
Hello World! in 5-minutes or less with LAMP/WAMP configuration
developers that already know PHP and have an understanding of MVC can use Vork productively within minutes

Performance-Oriented and Scalable

Enterprise-grade Vork platform has no slow abstraction layers or re-invented PHP functionality
Out-of-the-box Hello World! including making a database connection is typically just 0.0065 seconds! Load time can be further reduced with our suggested production configuration (see documentation.)
Built-in support for multiple master/slave database configurations with interface tools to enforce security, minimize redundant SQL code and increase SQL-statement efficiency
Only loads code & objects that are needed for that instance and nothing more

Standards-Compliant

Full MVC stack including layouts and components
All tools produce valid XHTML 1.1
Accessibility is automated as much as possible to meet Section 508 and W3C WAI standards
Object-oriented source code is E_ALL | E_STRICT and adheres to the Zend Framework Coding Standards (except uses "one-true-brace" consistently throughout)
CSS-reset with default styles to provide cross-browser display consistency verified in Firefox, Safari, Google Chrome and IE6, 7 and 8
CakePHP and Zend Framework objects can be imported into Vork; Vork Helpers and components can be used within Zend Framework and CakePHP
Universal database support without abstraction layers; ability to easily change database brands at any time
Code is open-source, built for PHP 5 and fully documented using the phpDocumentor DocBlock standard
Concise URL format is ideal for search engine optimization and is easy to communicate verbally

Extensive Toolset

Simplified use of Google tools: Charts, Analytics, AdSense, Sitemap, Payments
Amazon Web Services connection interface with automated caching mechanism
E-commerce tools to validate credit cards, accept PayPal payments, get UPS shipping rates, track a package & more!
Forms maintain state automatically + ample tools including a feature-rich WYSIWYG textarea that produces valid XHTML 1.1 markup and works in every browser
One-line of code turns any controller or action into a full-featured Wiki
Universal log-in/log-out/forgot-password utility
User input validity is verified both in JavaScript (for user-experience) and in PHP (for security) - form validation rules are only written once
Extensive HTML helper functions including simplified embedding of Flash and YouTube videos
Consistent interface to many third-party tools including sharing boxes like:
Email tools including outgoing-mail templates that operate like MVC-elements and email address display tools that prevent harvesting
Image management tools to add a watermark to an uploaded image and generate multiple images in different sizes (fullsize, thumbnail, etc.)
POST utility to simplify connecting to web services
Default 404 "not found" page has a Google Search box pre-populated to search your site for content related to the missing page
RSS layout makes it easy for any PHP array to become an RSS 2.0 or Atom feed
Debugging tools that output to your Firefox Firebug console

http://vork.us/

Now Google competing...

New! Google Search Appliance 6.0

The Google Search Appliance (GSA) provides fast, relevant search for your intranet or website. An on-premise, easy-to-deploy solution, the GSA provides your organization with high relevancy right out of the box, can be customized to meet your specific needs, and scales easily as your content grows.

New! Limited time offer - Buy a GSA with a 1 million doc license and get two free days of onsite deployment services. Learn more

New! Compare relevance across two or more enterprise search configurations with Side-by-Side

Google Search Appliance 6.0 comes with a brand new architecture, (GSA)ⁿ, which enables new heights of scalability, customization, and search quality. Learn more about the new features, or read a technology review of GSA 6.0 from research analyst Butler Group.

Intranet
Search across websites, intranets, portals, fileshares, content management systems, and business applications to deliver true "universal" search for your organization. Learn more

Website
Convert your website visitors into satisfied customers by delivering the information they need to facilitate purchase decisions, streamline support, and engage fully with your online brand. Learn more

Demos

View an upcoming webinar about the GSA with live Q&A.

Livelink Certification Programs

All Programs include a review of the pre-requisite material, projects and exams. Livelink ECM mentors provide dedicated support throughout the duration of the program.

Livelink ECM Certification Programs are intense and interactive sessions designed to maximize participants understanding of the Livelink ECM product functionality. Participants will find the experience challenging, but highly rewarding.

Livelink ECM Certification »

These Programs are intended for those users who have completed the pre-requisite courses.

Livelink ECM Certification - »

These sessions are comprised of a combination of accelerated learning and practical experience and networking. Materials used in each course may include, eLearning, instructor-led classroom sessions, lectures from field experts, case study solutions, role playing with a customer, the development and presentation of a proof of concept, and final certification exams.

Certification Program -

Certification is awarded to participants that obtain a passing grade for the program materials and certification exams.

Certification Regulations: »

All Livelink ECM Certification Programs will be supervised by an Open Text Approved Instructor or Facilitator.
To receive Certification, the candidate must obtain 70% overall score in the program and 70% on each of the certification exams.
If a participant fails an exam, they have the option to re-write it once at a fee of $400 USD. If the second exam is failed, the participant needs to attend another certification (including the project), for the standard fees.
All 're-write' exams must be held in an Open Text regional facility or supervised by an Open Text Approved representative.
Participants who pass an exam cannot take the exam again to improve their results. No 'make-up' exams are permitted.
Disclosure of exam content and other acts of misconduct during or after the Program completion are strictly prohibited. If such an act occurs, Certification will not be awarded or may be revoked.

Thin Client Content Viewer Solutions

Thin Client Content Viewer Solutions provides Ability to View, Markup, Hundreds of Document Formats and Collaborate Online with Partners, Suppliers and Customers
A global leader in enterprise content management (ECM), today announced the latest versions of Open Text Desktop Viewer and Open Text Thin Client Viewer, with expanded support for new file formats. The solutions help enterprises lower costs and improve productivity by providing a simple way to manage the creation, capture, viewing, markup and publishing of content across departments and the enterprise. Using the Open Text Thin Client Viewer, customers can view, share, distribute and collaborate on documents online with partners, suppliers and customers via a Web browser.

Open Text Desktop and Thin Client Viewer solutions offer viewing and markup capabilities for hundreds of different file formats without the need to have the originating application installed on users’ desktops. The ability to handle the majority of document viewing requirements, including native file viewing, 3D CAD model viewing, direct scanning and cleanup of paper documents, and document markup and revision, makes Open Text viewer solutions among the most frequently selected viewing tools on the market. The new versions introduce support for a number of new file formats, including Excel 2007, Solidworks 2008, AutoCAD 2009 and Auto Desk Inventor 2009.

These releases demonstrate Open Text’s commitment to continued development and innovation of content viewing solutions from recently acquired Spicer Corporation, the original developer of these applications, formerly known as Imagenation and ViewCafe. In addition to continuing to extend stand-alone viewer capabilities, Open Text plans to further integrate content viewing and markup functionality into upcoming versions of the Open Text ECM Suite.

Open Text Web Solutions Add Global Website Deployment Capabilities

Web Solutions for Multi-Sites Helps Customers to More Cost-Effectively Localize and Manage Multiple Global Web Sites Waterloo, a global leader in Enterprise Content Management (ECM), today announced availability of the latest release of Open Text Web Solutions. Available to customers now, this new release offers a number of additional enhancements to what is already a core strength of Open Text Web Solutions: Helping customers translate, manage and synchronize multiple websites worldwide. Web Solutions is an integral component of the Open Text ECM Suite, the industry’s most comprehensive suite of content services used by tens of thousands of organizations worldwide.

The enhanced functionality is part of a complete solution called Open Text Web Solutions for Multi-Sites that gives customers everything they need to develop a global Web presence. It helps large enterprises to more efficiently share corporate information, leverage existing translation memory tools such as Across Systems® or SDL TRADOS®, and to personalize the user experience. For small and mid-size businesses, it provides a simple and cost-effective tool for expanding globally.

The challenge of managing global websites across many markets is growing as companies work to establish their brands across many diverse markets in an increasingly competitive global arena. Customer communication in a local language is growing in importance in marketing and sales, and is critical for companies trying to expand in key markets. Websites are a critical part of this equation but many organizations are overwhelmed by the processes involved in managing multiple sites across many countries.

"The challenges of building an effective Web presence across diverse markets around the world are greater than ever, as user expectations become increasingly sophisticated," said Daniel Kraft, Senior Vice President, Corporate Strategy at Open Text. "With the latest release, we've made it easy to share and distribute content on a global basis to ensure consistent branding, and to attract and engage visitors in their native language on a site that is personalized to reflect their culture and needs."

For organizations with a global presence, Web Solutions for Multi-Sites adds new content distribution services that make it easy for Web localization teams to share and update content via a centralized content pool. Team members are automatically notified when content changes or updates become available. Once localized content is added to this pool all countries that use the same language can use this content for their local websites. A new Content Translation Management module offers translation workflow integration, expanded support for computer-aided translation tools, and export to standardized XLIFF formats. XLIFF, which stands for XML Localization Interchange File Format, streamlines the exchange of localization data among companies, vendors and across software tools.

Phoenix Contact GmbH & Co. KG, a world industry leader in electronic interface and industrial automation technologies, uses Open Text Web Solutions in conjunction with the firm's SDL TRADOS Translation Memory system to ensure prompt translation of content.

"We manage 43 websites in 27 languages with Open Text Web Solutions," said Carsten Rheker, Internet Project Leader for Phoenix Contact. "For our Web editors the system is very easy to use because all the workflows can be driven through the same Open Text user interface. With just a few mouse clicks the language can be selected and the translation process started. From there, it runs automatically."

Open Text, with more than a decade of experience in leading Web Content Management (WCM) software, provides Web Solutions to create, manage and deliver the content that drives business. The content management and delivery solutions are recognized throughout the industry for their legendary ease of use and feature leading multilingual support; enterprise Web 2.0 capabilities; content integration; and contextualized delivery. From mid-market to enterprise, more than 2,600 organizations around the world rely on this expertise to create, manage and deliver personalized Web experiences for their intranets, extranets and Web sites.

Open Text Extends eDiscovery Offering

Open Text Web Solutions Add Global Website Deployment Capabilities

LegalTech 2009 – New York - 2009-02-03 - A global leader in Enterprise Content Management (ECM) software, today announced that it has extended its new eDiscovery solution to its Open Text eDOCS customers. Now organizations, particularly corporate legal departments, will be able to significantly minimize the need for third-party processing and control the high costs of legal reviews by culling irrelevant information.

Open Text eDiscovery Early Case Assessment is being offered through a strategic relationship with Recommind, the leader in search-powered information risk management (IRM). The solution combines Recommind’s Insite Legal Hold application with the Open Text ECM Suite. The combination not only addresses the critical need for eDiscovery in an age of growing regulatory and legal challenges, it also lets customers tightly integrate eDiscovery within their broader ECM initiatives. Open Text eDOCS customers will gain expanded eDiscovery capabilities woven into their overall content, records and email management practices.

“This announcement furthers our commitment to Open Text eDOCS customers and expands on our leadership within the legal industry,” said Kirk Roberts, EVP & President of Integrated ECM Group at Open Text. “Additional eDiscovery support meets a critical need for law firms and corporate legal departments to be able to assess, collect, preserve and process electronically stored information that resides in Open Text eDOCS, which is often an organization’s system of record.”

“Extending the functionality of the Early Case Assessment solution to include Open Text eDOCS is a key development in addressing the need to minimize information risk and increase litigation and investigatory efficiency for many companies,” said Robert Tennant, CEO of Recommind. “This is a natural extension of the Open Text eDOCS search capabilities we developed for our MindServer Search customers and an important next step in our Open Text partnership to deliver the Early Case Assessment solution to a wider range of enterprises and offer our current and prospective customers new levels of speed and accuracy for their data management and eDiscovery initiatives.”

Open Text is a leading global provider of ECM solutions for law firms. The company offers a full range of applications and legal industry expertise to support law firms’ business practices and proactive compliance needs throughout the matter lifecycle – from client intake through to final disposition. Currently, 70 percent of the AmLaw 100 firms are using Open Text’s content management solutions.

Livelink Enterprise 9.7 Release

	undefined - A Sneak Peek at Livelink ECM Enterprise Server 9.7

	Found at bee mp3 search engine

SOA

Service Oriented Architecture

SOA is primarily a re-use initiative aimed at increasing IT and Business agility.

SOA is not “only” Web Services
SOA is not about XML
SOA is not “only” a Technology initiative

SOA is a fundamental change in the way we deliver business value.

Through governance of architectural and technical principals, a solid SOA enables IT and business agility. When SOA is fully embraced, the focus shifts from tactical to strategic delivery. Services are designed (or redesigned) using well established SOA Principles for strategic Service Resuability throughout the enterprise. Integration of these services is also a strategic Endeavour. It's no longer a point in time solution for a single use case. Integration is now a true first class citizen in the Enterprise Architecture, not just some aging product or little known standard.

The two key components of SOA are people and technology. People are the primary component because all of us need to organize, plan, architect, govern, and manage business processes for re-use. Technology is secondary to SOA architecture in that it is the implementation of the business processes. Using SOA technology by itself, will not lead to re-use and associated benefits. As we start to consolidate and reuse existing processes and systems, business agility will increase while the time to market and the costs associated with the design, development, implementation, and maintenance of our business systems will decrease.

Using the SOA principle of Service Resuability, Company will be able to leverage modeled business process to quickly assemble new solutions , track and measure key process indicators in real time, and have the ability to adapt and change system behavior rapidly and simply. Therefore decreased time to market will increase revenue.

Connecting Students and Teachers in a Safe and Secure Environment

When Keith Pomeroy joined the Olentangy Local School District, located in southern Delaware County, Ohio as the director of technology, the support for the networks and applications was being handled by outside consultants. In order to get better control of Olentangy's IT environment, serving 13,000 students from preschool through twelfth grade, Pomeroy knew he needed to take back the district. He evaluated the district's IT infrastructure and operational processes and concluded that a more efficient and integrated IT platform was required. His goal was to create a scalable and flexible environment for the teachers, staff and students that would meet all their communication, collaboration and knowledge sharing requirements.

Pomeroy made a decision to use technology from Open Text to enable school districts to create collaborative online communities that connect students, teachers, administration and parents within a secure environment. With Open Text, Olentangy Local School teachers, employees and students now have access to the latest technologies for district-wide email, online learning communities, safe social networking, student-teacher collaboration, curriculum development, and much more. In fact, Pomeroy estimates the savings to the district from using Open Text at almost $2 Million over 5 years by eliminating additional software packages and outsourcing costs.

~Harsha

New Module for Recruiting Mgmt:
Open Text Recruiting Management for Microsoft SharePoint Simplifies and Automates Hiring Processes; Native Microsoft Office SharePoint Server 2007 Application Streamlines Complex Hiring Processes, Minimizes Time Required for Hiring Managers Involved in Recruiting

Search This Blog

AbsurdThinker

Livelink