Configuring MCS on WebSphere Portal

Configuration files are used to set up Multi-Channel Server (MCS) software on WebSphere® Portal. A script is used to make the necessary updates to the files.

About this task

MCS uses the following configuration files:

mcs-config.xml
This file contains the MCS configuration parameters. The parameters in this file are described in the topic Administering Multi-Channel Server in the Multi-Channel Server information center.

In addition, the associated XML schema definition (XSD) file, mcs-config.xsd.
mcs-jlog.xml
This file controls the MCS logging level and enables tracing. See the topic Message logging and trace information in the Troubleshooting section of this information center for more information about this file.

Note: Ignore the file mcs-log4j.xml.

During MCS installation, mcs-config.xml and mcs-config.xsd are copied from the wp_profile_root/PortalServer/wp.mobile/wp.mobile.mcs directory and deployed into the Multi-Channel Server enterprise archive (EAR). The EAR is expanded into the wp_profile_root/installedApps/node_name/mcs.ear directory. The mcs-config.xml and mcs-config.xsd files appear in the mcs.war/WEB-INF subdirectory.

Note: Do not directly update the versions of the wp_profile_root/installedApps/node_name/mcs.ear/mcs.war directory, because your changes will be overwritten the next time that the mcs.ear file is redeployed.

Perform the following procedure to modify the mcs-config.xml configuration file.

Procedure

Copy the mcs-config.xml file from the wp_profile_root/installedApps/node_name/mcs.ear/mcs.war/WEB-INF directory to the wp_profile_root/PortalServer/wp.mobile/wp.mobile.mcs directory.
Edit the mcs-config.xml file appropriately.
Note: If you are using a Mobile Portal Accelerator cluster, you need to edit the MCS files and run the configuration procedure on only one node in the cluster. However, you must synchronize all nodes in the cluster after you update the MCS EAR. For information about synchronizing nodes in a cluster, see the WebSphere Application Server Network Deployment information center.
Save the changes.
Run the following Multi-Channel Server configuration update process, which deploys an updated file into the Multi-Channel Server EAR (mcs.ear).
1. Make sure that the WebSphere_Portal application server is running.
2. Run the following command to ensure that the WebSphere environment is set up correctly:
```
. wp_profile_root/bin/setupCmdLine.sh
```
  Attention: There is a space between the period (.) and the rest of the command.
```
wp_profile_root\bin\setupCmdLine
```
3. Change your working directory to wp_profile_root/ConfigEngine.
4. Run the following command:
```
./ConfigEngine.sh init mcs-update-config
```
```
ConfigEngine init mcs-update-config
```
  Note: For security reasons, if you do not want to store the WebSphere Portal admin password and WebSphere Application Server admin password in the wkplc.properties file, you can specify the passwords on the portal server command line. For example, when this topic directs you to enter the ConfigEngine script or batch file, you would add parameters to the command to specify the password values as shown here:
```
./ConfigEngine.sh init mcs-update-config
-DPortalAdminPwd=WP_admin_password_value
-DWasPassword=WAS_admin_password_value
```
```
ConfigEngine init mcs-update-config
-DPortalAdminPwd=WP_admin_password_value
-DWasPassword=WAS_admin_password_value
```
  where
  - WP_admin_password_value is the value of the WebSphere Portal admin password
  - WAS_admin_password_value is the value of the WebSphere Application Server admin password if WebSphere Application Server security is enabled
5. Restart the portal server using the following commands:
```
wp_profile_root/bin/stopServer.sh server_name -username WAS_admin -password WAS_admin_password_value
```
```
wp_profile_root/bin/startServer.sh server_name
```
```
wp_profile_root\bin\stopServer server_name -username WAS_admin -password WAS_admin_password_value
```
```
wp_profile_root\bin\startServer server_name
```
  where server_name is the name of the WebSphere Application Server instance (for example, WebSphere_Portal).