IBM Support

The unit test environment (UTE) server not start properly after installing the Lotus WebForm Server

Troubleshooting


Problem

Why does the unit test environment (UTE) server not start properly after I have installed the Lotus WebForm Server, which is packaged with WebSphere Integration Developer and WebSphere Dynamic Process Edition, into the UTE server profile in WebSphere Integration Developer and WebSphere Dynamic Process Edition?

Symptom

UTE server does not start properly

Cause

The WebSphere Process Server UTE server profile uses embedded Derby for the common WebSphere Process Server database so that it supports only one connection at a given time. However, if Lotus WebForm Server is installed into the same profile as the WebSphere Process Server UTE server, both servers for Lotus WebForm Server and WebSphere Process Server must connect to the WebSphere Process Server database while running. This situation means that WebSphere Process Server cannot function properly if Lotus WebForm Server is already connected to the database.

Resolving The Problem

The following two solutions are available for this issue:

  • You can create another profile (a WebSphere Application Server profile is sufficient) and install Lotus WebForm Server into that profile.

  • You can reverse the order in which the two servers are started. Complete the following steps:
    1. Open the Windows Control Panel and select Administrative Tools > Services.

    2. Stop WebSphere Application Server V7.0 for Lotus WebForm Server if it is started and change its startup type from automatic to manual.

    3. Open WebSphere Integration Developer and start the test server in WebSphere Process Server.

    4. Verify the log and console to ensure that the server started successfully without any exceptions.

    5. In Services, start the WebSphere Application Server instance for Lotus WebForm Server.


Note: You will see exceptions in the system log for Lotus WebForm Server for failed connections to the database for WebSphere Process Server. However, Lotus WebForm Server functions properly because it does not depend on functions from the underlying profile for WebSphere Process Server.

[{"Product":{"code":"SSQQFK","label":"WebSphere Integration Developer"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Test and deployment tools","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"7.0.0.5;7.0.0.4;7.0.0.3;7.0.0.2;7.0.0.1;7.0;6.2.0.3;6.2.0.2;6.2.0.1;6.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSBN76","label":"WebSphere Dynamic Process Edition"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Installation","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0.1.1;7.0.1;7.0.0.3;7.0.0.2;7.0.0.1;7.0;6.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21614705