How to install MCS, Services Builder on WebSphere

Technical Note USA12067
Created 06-Apr-2006

Applies To
Last reviewed date: 06 April 2006

This document has been written using the following components:

Attachmate Synapta Services Builder for Screens v.3.0
Microsoft Windows 2003 Standard Edition Server
IBM WebSphere Application Server, 6.0.0.1

Goal

How to install MCS, Services Builder on WebSphere

Fix

Prerequisites:

- Verify that your Windows local administrator password is not null.
- Install WebSphere, accepting all the default settings, and set the WAS service to run automatically. (By default it is set to Manual.)
- Obtain the msc.war file by following these steps:

1. On the Synapta Services Builder 3.0.0.0 CD, locate the file named Synapta_IBM-30.tar.gz, and copy it to a temporary folder.

2. Using a zip utility, such as Winzip, open Synapta_IBM-30.tar.gz and uncompress the Synapta_IBM-30.tar file into a subfolder of your temporary folder.

3. The subfolder of your temporary folder contains a folder named Synapta_IBM-30.tar. Browse the msc folder within this folder for the file named mcsinst.tar.

4. Using a zip utility, such as Winzip, open mcsinst.tar and extract the file named mcs.war.
STEP I. Modify the mcs.war file to a format that WebSphere can install and use:
1. Use the mcs.war file (extracted in the Prerequisites section #4).
2. Delete the /org/w3c directory from WEB-INF/lib/xerces-deprecated.jar.
3. Open "WEB-INF/lib/xml.jar" and remove the org/ directory from it.
4. Add an empty file named "placeholder" to the "installscripts" directory.
5. Jar or zip the contents of this directory into an mcs.war file.

NOTE: Do not use the original mcs.war file extracted from the mcsinst.tar; always follow the steps listed under Step I to modify the msc.war file.

STEP II. Install mcs.war:
1. Log into the WebSphere console.
2. Click Applications.
3. Click Install New Application.
4. Enter the path to the mcs.war file that you created in Step I.
5. Enter mcs in the "Context Root" field.
6. Click Next.
7. Accept all the default values, unless you have specific reasons to change them. Click Next until you reach the Finish panel.
8. Click Finish.
9. Click Save to Master Configuration.
10. Click Save.

STEP III. Configure the mcs_war application:
1. Log into the WebSphere console.
2. Click Applications.
3. Click Enterprise Applications.
4. Select "mcs_war" or whatever name you gave to the MCS application when installing.
5. Set the Classloader Mode to "PARENT_LAST".
6. Click Apply.
7. Select Web Modules.
8. Select mcs.war.
9. Set the Classloader Mode to "PARENT_LAST".
10. Click Apply.
11. In the "Messages" box at the top of the screen, click Save.
12. Click Save.

STEP IV. Edit ServerMgtBootStrap.properties:
1. Locate the MCS web application on the file system. This should be "/path/to/WebSphere/AppServer/profiles/default/installedApps/HostNameNodeName/mcs_war.ear/mcs.war".
2. Open "WEB-INF/classes/ServerMgtBootStrap.properties" in your favorite text editor (for example, WordPad).
3. Set LocalServer.MCSRootDir to the MCS web application path you discovered in Step IV-1.
4. Set LocalServer.Port to 9080 or whatever HTTP port you have configured for your WebSphere installation.
5. Enter the IP address of the local machine for LocalServer.IP.
6. Enter the local machine name for LocalServer.HostName.
7. Enter WebSphere for LocalServer.WebServerName.
8. Leave the remaining settings empty.

Note the following:
- DO NOT use double quotes (") for the LocalServer.MCSRootDir and use the 8.3 notation. For example, LocalServer.MCSRootDir=C:/Progra~1/IBM/WebSphere/AppServer/profiles/default/installedApps/VP2003SEWS6Node01Cell/mcs_war.ear/mcs.war
- Use forward slashes as in the example above.
- Or, you can use backslashes, but you need to use double backslashes in the path. For example,
C\:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\default\\installedApps\\VP2003SEWS6Node01Cell\\mcs_war.ear\\mcs.war

STEP V. Start MCS:
1. Log into the WebSphere console.
2. Click Applications.
3. Click Enterprise Applications.
4. Select the mcs_war check box.
5. Click Start.

STEP VI. Copy jar and xml files to prepare for Package Installer:
1. In the Synapta_IBM-30 folder, locate the following files:

Synapta_IBM-30/scrman/clientconfig.xml
Synapta_IBM-30/scrman/clientconfig.jar
Synapta_IBM-30/scrman/connectordeploy.xml
Synapta_IBM-30/scrman/connectordeploy.jar
Synapta_IBM-30/scrman/screenconnectors.xml
Synapta_IBM-30/scrman/screenconnectors.jar
Synapta_IBM-30/scrman/addscreen.xml
Synapta_IBM-30/scrman/addscreen.jar


2. Copy the files to <path to WebSphere>/AppServer/profiles/default/installedApps/HostNameNodeName/mcs_war.ear/mcs.war/installscripts.

3. Delete the file named "placeholder" in the /installscripts folder.

STEP VII. Install Services Builder for Screens Runtime:
1. Install the Services Builder for Screens Runtime by running setup.exe.
2. Answer the questions as if you were installing it normally, but for the MCS server information, enter the MCS server and port 9080 (or the port you entered during the MCS installation).

STEP VIII. Install MCS Components:
1. Connect to MCS (for example, HTTP://webserver:9080/mcs.).
2. Log in using the following userid and password information:
Userid = system
Password = 12345
(12345 is the system's default password.)
3. Click Services > Server Management.
4. Select Package Installer.
5. Install the packages in the following order:

connectordeploy.xml
clientconfig.xml
addscreen.xml
screenconnectors.xml

6. After running the package installer to install a new package or TD, copy the WEB.XML found at:

<path to WebSphere>/AppServer/profiles/default/installedApps/HostNameNodeName/mcs_war.ear/mcs.war/WEB-INF

to:

<path to WebSphere>/AppServer/profiles/default/config/cells/HostNameNodeName/applications/mcs_war.ear/deployments/mcs_war/mcs.war/WEB-INF

NOTE: The web.xml may not get updated (this step may be required only for Terminal Viewers). You should review the web.xml file's timestamp and, if updated, make the copy as suggested above in Step VIII-6.

STEP IX. Once all the packages are installed, restart WebSphere.

NOTE: If you want to use EJBs, you will need to install CTD 16 or higher. .