Wednesday, September 28, 2011
Find Weblogic Password (Encrypted)
Friday, May 28, 2010
Side By Side Deployment for Applications
In the past there has to be a downtime when a application needs to be deployed or a new version of the same application needs to be deployed.
Today application downtime has become zero. Zero downtime can be achieved in various ways. Oracle Weblogic Server provides a neat mechanism of deploying the new version of application without affecting the existing version of application and existing user sessions. At the same time it makes sure that once all the user sessions end (or after a specified timeout period) old version of application is retired automatically.
Once new version of application is deployed using "Side By Side Deployment" mechanism, all new user requests will be served by the new version of the application.
Prerequisite to deploy the application using "Side By Side Deployment" mechanism is that the previously deployed application has to be versioned. If previously deployed application is not versioned then the new application cannot be deployed using "Side By Side Deployment" mechanism. If attempted, it will throw weblogic.management.ManagementException: [Deployer:149081]You cannot deploy application, '[Your-App-Name]', with version '[App-Version]'. The application was previously deployed without version.
To version an application, the attribute "Weblogic-Application-Version: x.xx" should be present in manifest file.
Once the new version of application is deployed successfully and all user sessions requesting old version of application is closed, the old version of application will go into "Retired" state automatically. An application which is in "Retired" state can be made "Active" by clicking the "Start - Serving All Requests". If old version of application is made active, the new version of application will go into "Retired" state, provided all the user sessions requesting new application is closed.
Applications in "Retired" state has to be manually undeployed.
Thursday, January 14, 2010
How to encrypt password using weblogic?
- Open a DOS or UNIX command prompt
- Change directory to the weblogic server domain home
- Set the weblogic server environment
- Run the command to encrypt text vinaybarnwal
- Command:/>java weblogic.security.Encrypt vinaybarnwal
- And it should print the encrypted value for vinaybarnwal
Thursday, December 24, 2009
Saturday, December 19, 2009
Generate a certificate using keytool
To generate the trusted certificate:/>
keytool -genkey -keypass
What is your first and last name?
[Unknown]:
What is the name of your organizational unit?
[Unknown]:
What is the name of your organization?
[Unknown]:
What is the name of your City or Locality?
[Unknown]:
What is the name of your State or Province?
[Unknown]:
What is the two-letter country code for this unit?
[Unknown]:
Is CN=Unknown, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?
[no]: yes
To import the trusted certificate:/>
keytool -export -keypass
Sunday, November 22, 2009
Clipper Portlet, IFrame Portlet & WSRP Portlet
A clipper portlet is a portlet that renders content (full or part) from another web site. A clipper portlet can include all or a subset of another web site’s content using a process called “web clipping.” You can clip all or part of another web site. Users can effectively view and interact with content from another web site without leaving the portal. The session of Clipper portlet is independent of session of the weblogic portal application.
IFrame Portlet
Also called Browser (URL) Portlets, display HTML content from an external URL; no development tasks are required to implement them. You can clip all or part of another web site. Users can effectively view and interact with content from another web site without leaving the portal.Browser portlets, also called Content URI portlets, are basically HTML portlets that use URLs to retrieve their content. Unlike other portlet types that are limited to displaying data contained within the portal project, browser portlets can display URL content that is outside from the portal project.
WSRP Portlet
Also called, remote portlets conform to the WSRP standard; they can be hosted within a producer application (simple producer or complex producer), and surfaced in a consumer application. WSRP Portlet (or Remote portlet or producer portlet) are the ones who are actually remote portlet and are supported by weblogic portal. All portlets that are created as part of weblogic portal application are by default remote portlets and available to be consumed by the consumer portal. Pages and Books can also be made remote and can be consumed as part of consumer portal. By setting the property "isRemote" for the portlet, it can be prohibitted to be available as remote portlet.
Which one to choose when?
Clipper and Browser porlets are not recommended to use for transactional purposes, they are meant to be for displaying view only contents from third party sites (part or full). However remote portlets (producer portlets) are available for the purpose of publishing as remote porltets and consuming them through consumer portlets. Separate sessions are maintained for each of these consumer and producer portal applications however Weblogic portal platform is responsible to maintain the session between the producer and consumer portals.
Oracle Weblogic Simple Producer
Oracle Weblogic Simple producer is a light version of Oracle Weblogic Portal + Oracle Weblogic Federated resources. From here onwards simple producer will be used to indicate Oracle Weblogic Simple Producer. Remote portlets deployed on producer can be consumed by the consumer portal using WSRP protocol.
A simple producer can be created using the following steps:
Step 1: Create the simple producer domain
Step 2: Create the simple producer project
Step 3: Move the existing application to simple producer project or create new application as required.
Step 4: Generate simple producer portlets, books, pages etc.
Step 5: Deploy the simple producer application on simple producer domain
Step 6: Consume the simple producer portlets and you are done.
Following features are supported by Simple Producer:
- Page flow & struts portlets can be created and published as remote portlets
- URL Rewriting is supported
- Java, JSP, HTML, Clipper or Iframe portlets are not supported
- Registration of remote portlets are not supported
- No portal administration is available for simple producer
- No Backing file support is available for simple producer
- No event support is available for simple producer and thus inter portlet communication is also not available.
- Render dependency file is not supported by simple producer
- Portal APIs are not supported by simple producer