Skip to main content

WebCenter Deployment Architecture

By
The main components of the deployment architecture are:


• WebLogic Server
• Portlets deployed in Portlet Container
• Metadata storage for customization information
• Enterprise Content Management solution with Content Adapters
• WebCenter Services
• WebCenter Search
• Identity Management

 
 
 
 
WebLogic Server, which is a Java EE–compliant application server, is at the center of WebCenter. WebCenter applications are Java EE applications that are deployed to WebLogic Server. WebCenter Spaces is a prebuilt custom application using WebCenter Framework and Services.

Portlets :
WebCenter applications can consume portlets. Portlets are deployed into a Portlet Container and are accessed by various HTTP-based network protocols such as WSRP and SOAP. Oracle WebCenter supports several portlet APIs such as JSR 168 and PDK Java.
 
Metadata Services :
WebCenter applications can be customized or personalized at run time. Customization data is stored in Metadata Storage, typically in a database schema, but for development purposes it can be stored in the files of a file system.
 

Content Integration :
Oracle Content Integration strategy is based on Java Content Repository standard (JCR 1.0 or JSR 170). This API provides uniform access to various content management systems.Oracle WebCenter supports several content management systems, such as file system, Oracle Portal, and Oracle Universal Content Management.
 
Oracle provides adapters to each of the supported content management systems, which implement JCR 1.0 API on top of the content management system’s API and access protocol.Oracle WebCenter also supports third-party content management systems, such as Lotus Domino, SharePoint, and Documentum, by providing an appropriate content adapter.
Note: File system–based content management is recommended only for testing purposes.

WebCenter Services
WebCenter applications can use a wealth of Web 2.0 services. This slide shows services provided with WebCenter. Each of these services is accessed by an adapter and uses a unified connection description. Many of the services require a back-end server.
 

Search Service
WebCenter applications can use a global search service, which searches in the content management system and also in the services’ data, such as forums on a Discussion server or tags associated with various objects.
 

Identity and Permission Management :
Users of WebCenter applications are stored in identity management systems. WebCenter supports a range of identity management solutions, including a simple file-based user repository, industry-standard LDAP servers, or various Single Sign-On solutions.
Application-specific permissions are also stored in this system.Web 2.0 services are typically wired to the same identity management solution used by the custom applications. Various protocols ensure secure identity propagation between custom
applications and the services.
 

The whole architecutre with all the components is


 

 


 
 
 
 
 
 
 
 

 

Comments

Post a Comment

Popular posts from this blog

Passivation and Activation in ADF (Application Module )

By
1. For performance reasons, ADF keeps a pool of application modules in memory. It tries to give each session the same application module as the session used during the last request; however, this might not be possible during peak load of your application. 2. In this case, ADF saves the application modules state in a database table so the application module can be used by another session. This is called passivation . 3. When the first session needs the application module again, its state is retrieved from the database process known as activation . 4. If you have made an error in your code and depend on some variable that is not persisted correctly when your application module state is stored, you will experience mysterious errors under high load.   Enable/Disable Application Module Pooling : Right-click on your application module, choose Configurations.By default, each application module has two configurations. Ensure that the one ending in …Local is selected and then click
1 comment
Read more

Get modified rows from Entitiy Cache

By
To get the modified rows from entity cache we have getEntityState() method at EntityImpl class. Refer to my previous blog  Accessing EO impl methods from VO impl  where i am overriding the getEntityState() in EOimpl and calling it in VOImpl. We can use methods written or overridden in VOImpl class to AMImpl class. There are different states associated with an entity object. STATUS_UNMODIFIED STATUS_MODIFIED STATUS_NEW STATUS_DELETED STATUS_DEAD We have to check the state or row in our AmImpl class by using the VOImpl method and through this we can distinguish the rows present at vo. Add below code in AMImpl class along with my previous post. public void geCachedRowsCount(){         JobsVOImpl jobsVo = (JobsVOImpl)this.getJobsVO();         RowSetIterator iter = jobsVo.createRowSetIterator(null);             while(iter.hasNext()){             Row row = iter.next();             byte state = jobsVo.getEntityState(row);             System.out.println("Job_id -&
2 comments
Read more

The file store "WLS_DIAGNOSTICS" could not be opened

By
WLS_DIAGNOSTIC ERROR weblogic.store.PersistentStoreException: [Store:280073]The file store "WLS_DIAGNOSTICS" could not be opened because it contained a file with the invalid version 1. A file of version 2 was expected. When you get this error while running your application on internal weblogic server delete the following file WLS_DIAGNOSTICS000000.DAT search the file in following path C:\jdev_work\system11.1.1.5.37.60.13\DefaultDomain this file is in DefaultDomain folder of your jdev. and delete the WLS_DIAGNOSTICS000000.DAT file . and run your applicatuon
1 comment
Read more