Under Target Metadata Repository, click the icon to display the Select metadata

Deploying WebCenter Applications 7-19 13. If required, specify additional deployment options such as the Web modules to include in your application or security migration settings.

14. In the Deployment Plan section, click Edit Deployment Plan to optionally edit the

currently selected Deployment Plan.

15. In the Deployment Plan section, click Save Deployment Plan to optionally save

the currently selected Deployment Plan for reuse when you redeploy the application.

16. To start the deployment process, click Deploy.

Fusion Middleware Control displays processing messages.

17. Click Close in the Deployment Succeeded page.

The WebCenter application and its deployment plan is now deployed on the WebLogic Managed Server instance. 18. If you restart the WebLogic Managed Server on which you deployed the application during your Fusion Middleware Control session, refresh the Farm from the Farm menu to update the application status.

7.1.6.5 Deploying Applications Using WLST

To deploy a WebCenter Portal application using the WLST command line, WLST must be connected to the Administration Server. You must invoke the deploy command on the computer that hosts the administration server. To deploy a WebCenter Portal application using WLST: 1. Start the WLST shell. For information on starting the WLST shell, see Section 1.13.3, Oracle WebLogic Scripting Tool WLST. 2. Connect to the Administration Server of your WebCenter installation: Note: If any target producers are not reachable as the application starts for the first time, the import fails. After the portlet producer becomes reachable, restart the application and try to import again. If you do not modify producer connections using the Configure ADF Connections page and they are pointing to incorrect but reachable producer locations for example, a producer in a development environment, portlets are imported to the incorrect producers. To remedy, after deployment use Fusion Middleware Control see Section 23.2.1, Registering a WSRP Producer Using Fusion Middleware Control and Section 23.4.1, Registering an Oracle PDK-Java Producer Using Fusion Middleware Control or WLST commands see Section 23.2.2, Registering a WSRP Producer Using WLST or Section 23.4.2, Registering an Oracle PDK-Java Producer Using WLST to modify the producer URL endpoint, and then redeploy the application as described in Section 7.3.2, Redeploying WebCenter Applications Using Fusion Middleware Control . Note: If you configured connections during deployment these are not stored as part of the deployment plan. You must specify these connection details again the next time you deploy. 7-20 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter connectuser_name,password,host_id:port Where: ■ user_name is the user name to access the Administration server for example, weblogic. ■ password is the password to access the Administration server for example, weblogic. ■ host_id is the host ID of the Administration Server for example, myserver.example.com. ■ port is the port number of the Administration Server 7001 by default You should see the following message: Successfully connected to Admin Server AdminServer that belongs to domain wc_domain. 3. Retrieve the MDS configuration by running the following command: archive = getMDSArchiveConfigfromLocation=ear_file_path where ear_file_path is the path and file name of the EAR file you are deploying for example, tmpmyEarFile.ear. For more information, see the getMDSArchiveConfig command in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. 4. After retrieving the MDS configuration information from the EAR file, you must set the proper MDS schema information according to your WebCenter setup for example, your application might be using a database connection based on a specific schema. To set the MDS schema information, run the following command: archive.setAppMetadataRepositoryrepository=respository,partition=partition ,type=DB,jndi=jndi Where: ■ repository is the name of the database schema for example, mds-Feb23demo ■ partition is the individual entity in the repository to allow each application to have its own namespace for example, webcenter. ■ jndi is the path and name used to allow access by the application servers other components for example, jdbcmdsFeb23demo 5. After setting the MDS repository information, save function the MDS configuration information with the following command: archive.save 6. Deploy the WebCenter Portal application using the WLST deploy command. deployapp_name, path, [targets] [stageMode], [planPath], [options] Where: ■ appName is the name of the WebCenter Portal application to be deployed for example, composerWLSTApp. ■ path is the path to the EAR file to be deployed for example, tmpcustomApp.ear.