Deploying the data source adapters

You can install the adapters for IBM® Rational® Publishing Engine data service on an existing instance of IBM WebSphere Application Server version 6.0. If you have more than one machine for the data sources, you need to repeat these steps for each machine.

Before you begin

Deploying on IBM WebSphere Application Server: Make sure that you have chosen the recommended machines for installing IBM IBM Rational Publishing Engine data service.

Deploying the data source adapters: You must first install the data service and then deploy the plug-in files for the adapters on the web application server.

Procedure

Deploy the data services war file on WebSphere Application Server.

  1. Start the IBM WebSphere Application Server profile management tool. To launch the profile management tool select Start > All Programs > IBM WebSphere > Application Server [version] > Profile Management Tool.
  2. Create a new profile named DataServices. To create a new profile in the tool:
    1. Click Next. Select Advanced profile creation, click Next.
    2. Select to Deploy the administrative console and click Next. Do not select Deploy the default application.
    3. Specify the profile name DataServices, click Next. Do not enable administrative security (you can do this later), click Next.
    4. Select Run the application server process as a Windows service, click Next and click Create.
  3. Start the WebSphere Application Server.
  4. Start the administrative console for the DataServices profile.
  5. On the Map modules to servers page, click Next.
  6. On the Map virtual hosts for Web modules page, click Next.
  7. On the Summary page, click Finish and Save.
  8. If you are using the RequisitePro Adaptor, configure generic JVM arguments. If you are using any other adaptor, continue to the next step.
    1. Login to the Admin console.
    2. Click Application servers > custom ServerName > Server Infrastructure > Java and Process Management > Process Definition > Java Virtual Machine.
    3. Set the Generic JVM arguments value to: -DRJCB_IN_MTA_ONLY='RJCB' -Xquickstart
  9. Restart the WebSphere Application Server.
  10. In the administrative console, click Enterprise Applications.
  11. Select DataServices.war and click Start.
  12. Add the adapter plug-ins to the web application by copying the adapter archive files to library directory of the web application.
    1. Locate the plug-ins for the adapters. By default, the plug-ins are installed in a subdirectory of the C:\Program Files\IBM\Rational\Rational Publishing Engine\RPEn.n\web services\data services directory. For example, the default location for the ReqPro plug-in is C:\Program Files\IBM\Rational\Publishing Engine\1.1.2\web services\data services\eclipse\plugins.
    2. Locate the features for the adapters. By default, the features are installed in a subdirectory of the C:\Program Files\IBM\Rational\Rational Publishing Engine\RPEn.n\web services\data services directory. For example, the default location for the ReqPro feature is located at C:\Program Files\IBM\Rational\Publishing Engine\1.1.2\web services\data services\eclipse\features.
    3. Locate the file system directory of the web application. By default the eclipse directories of web applications are located at below directory C:\Program Files\IBM\WebSphere\AppServer1\profiles\profile name\installedApps\Node Name\DataServices_war.ear\DataServices.war\WEB-INF\eclipse.

      The location depends on your deployed instance of WebSphere Application Server. To find the location for your installation, you can search the profiles directory of your WebSphere Application Server application server for a folder named DataServices.war.

    4. Copy the contents of the eclipse directory of substep a. and b. to the directory of substep c. Make sure that the contents of the eclipse/features and eclipse/plugins directories are copied to the target location. Do not to delete any files in the deployed web application. The features and plug-ins for each adapter must be merged with the features and plug-ins of the web application.
  13. Restart the web application server.

Feedback