This chapter includes the following sections:
For information about how to deploy producers using Fusion Middleware Control, Oracle WebLogic Server Administration Console, or WLST, see the "Deploying Portlet Producer Applications" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
For more general information about deployment of applications, see Chapter 69, "Deploying and Testing Your WebCenter Portal: Framework Application."
You can deploy your portlet producer to any Oracle WebLogic Managed Server that is configured to support WebCenter Portal portlet producers.
Before you can deploy your portlet producer to a WebLogic Managed Server, there are a couple of steps you must complete:
Create and provision a WebLogic Managed Server instance that contains all the required shared libraries. For more information, see the section "Creating a Managed Server" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
Create a WebLogic Managed Server connection for instances that reside outside JDeveloper. For more information, see Section 22.214.171.124, "Creating a WebLogic Managed Server Connection."
To deploy your portlet producer to a WebLogic Managed Server, you must first create an application WAR deployment profile.
Before you deploy the portlet producer, you must remove the
test-all application role if you enabled the automatic grants feature in the Configure ADF Security wizard. Because the
test-all role makes all ADF resources public, its presence increases the risk that your application may leave some resources unprotected. You must therefore remove the role before you migrate the application-level policy store.
For more information, see the section "How to Remove the test-all Role from the Application Policy Store" in the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.
To deploy portlet producers to a Managed Server that resides outside JDeveloper, you must create a deployment profile to indicate how the producer and its associated files should be packaged. To do this, you must create a Web Application Archive (WAR) file.
To create a WAR deployment profile:
In the Application Navigator, right-click the project folder, for example, Portlets, and choose New.
In the New Gallery, expand General, select Deployment Profiles, then WAR File, and click OK.
In the Create Deployment Profile -- WAR File dialog, enter a name for your deployment profile and click OK.
In the Edit WAR Deployment Profile Properties dialog, select Specify Java EE Web Context Root, enter a context root, then click OK.
In the Project Properties dialog, under Deployment Profiles, select the WAR file you just created and click OK.
After you have created the deployment profile and deployment descriptor, you can deploy your portlet producer to the managed server.
To deploy a portlet producer to a WebLogic Managed Server:
In the Application Navigator, right-click the project folder, for example, Portlets, and choose Deploy, then the deployment profile (WAR file) that you created in Section 61.2, "Creating a WAR Deployment Profile."
In the Deploy dialog, on the Deployment Action page, select Deploy to Application Server, then click Next.
On the Select Server page, select the connection to the Managed Server, then click Next.
On the WebLogic Options page, select the Managed Server, for example, WLS_Portlet, and click Finish.
If your application contains JSR 286 portlets, the Select deployment type dialog displays. Click Yes to add the configuration required to expose this application as a WSRP service.
Deployment started displays in the Deployment - Log window. If the application is successfully deployed to the targeted server instance, the message
Deployment finished displays in the log.
If you are deploying your portlet producer in a cluster environment, you will receive the following warning:
WARNING: oracle.webcenter.lifecycle.exception.LifecycleLockedException: A lock exists that prevents export set import.
This is expected behavior. When you deploy your application, the producer metadata exported into the EAR file (as a MAR file) needs to be imported into an MDS schema for use in the production environment. Importing the metadata occurs automatically during deployment. This import only needs to happen with one node in the cluster, so a lock is created to prevent other nodes in the cluster trying to perform the same operation.