Click the edit icon for Configure ADF Connections to check connection settings

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. Deploying WebCenter Applications 7-21 ■ targets specifies the target Managed Servers to which to deploy the application for example, CustomAppServer. You can optionally list multiple comma-separated targets. To enable you to deploy different modules of the application archive on different servers, each target may be qualified with a module name, for example, module1server1. This argument defaults to the server to which WLST is currently connected. ■ [stageMode] optionally defines the staging mode for the application you are deploying. Valid values are stage, nostage, and external_stage. ■ [planPath] optionally defines the name of the deployment plan file. The file name can be absolute or relative to the application directory. This argument defaults to the planplan.xml file in the application directory, if one exists. ■ [options] is an optional comma-separated list of deployment options, specified as name-value pairs. For more information about valid options, see the WLST deploy command in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. When you see the following message, the application has been successfully deployed and is ready to be accessed: Completed the deployment of Application with status completed

7.1.6.6 Deploying Applications Using the WLS Administration Console

You can use the WLS Administration Console to deploy a WebCenter Portal application or a portlet producer application. However, the Console does not offer a means to change ADF connections, including the essential MDS connection. To use the Console to deploy a WebCenter application, the MDS connection in the EAR file must be configured to the target deployment repository. Follow steps 1-5 in Section 7.1.6.5, Deploying Applications Using WLST , then follow the steps below to deploy a WebCenter Portal application or portlet producer application using the WLS Administration Console. Note: Since WLST does not prompt you to modify connections during deployment, the connection information in the EAR file is used to identify the target producer location in the last start-up. If that location is unreachable, correct the location after deploying the application by bringing up the target producers and restarting the application. Migration of portlet customizations starts automatically. If the producer connections point to incorrect producers for example, development producers, and those producers are reachable, the migration of portlet customizations starts using those producers. Since the migration completes, although incorrectly, restarting the application does not automatically restart the migration process. To remedy this, 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.