Updating mcs-config.xml when MCS is installed with WebSphere Portal (DB2)

You must edit the mcs-config.xml file.

1. 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.
2. Edit wp_profile_root/PortalServer/wp.mobile/wp.mobile.mcs/mcs-config.xml and make the following changes:
   1. Comment out the <local-repository> element near the beginning of the file by adding XML comment delimiters <!-- and --> around the element as shown here:

      <!--
          <local-repository>
          <jdbc-repository>
            <connection-pool
                maximum="20"
                poll-interval="3600000"
                keep-alive="false"
            >
              <anonymous-data-source
                  user="db2inst1"
                  password="ibmdb2"
              >
                <mcs-database
                    vendor="db2"
                    host="localhost"
                    port="50000"
                    source="mcs"/>
              </anonymous-data-source>
            </connection-pool>
          </jdbc-repository>
        </local-repository>
      -->

   2. Uncomment the following <jndi-configuration> and <local-repository> elements. Remove the XML comment delimiter (<!--) line that appears before <jndi-configuration>, and remove the XML comment delimiter (-->) line that appears after </local-repository>. The elements that should be uncommented are shown here.

      <jndi-configuration>
        <initial-context name="mcsContext">
        </initial-context>
      </jndi-configuration>
      
      <local-repository>
        <jdbc-repository>
          <jndi-data-source
                initial-context="mcsContext"
                 name="datasource-jndi-name"/>
        </jdbc-repository>
      </local-repository>

   3. Replace datasource-jndi-name with the JNDI name of the MCS data source (for example, jdbc/mcsDS).
3. 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).