IBM BPM, V8.0.1, All platforms > Install IBM BPM > IBM BPM Advanced for z/OS: Process Server > Configure IBM BPM Advanced for z/OS: Process Server > Completing the stand-alone configuration

Starting the server and verifying the installation

After you configure the DB2 database, load the database with system configuration, and update the server configuration values, you can start the stand-alone server, and verify the IBM BPM installation.


Procedure

  1. From the MVS™ console, start the server by running the z/OS START command with the following syntax:

    START appserver_proc_name,JOBNAME= server,ENV= cell. node. server

    where:

    • appserver_proc_name is the JCL procedure name in the proclib used to start the stand-alone server.
    • server is the short name of the server, or the step name used to start the procedure.
    • cell. node. server is a concatenation of the cell short name, the node short name, and the server short name.

    For example:

    START WCID1Z1,JOBNAME=WZID1Z1,ENV=ID1CELL1.NODE1.WZID1Z1

  2. From a browser window, access the administrative console by typing the web address of the server that you want to view. Use the following format:

    http:// server_name. domain_name: port_number/ibm/console

    where server_name is the name of the server, domain_name is the domain name, and port_number is the administrative console port number.

  3. Log on to the administrative console.
  4. Verify that you can see IBM BPM on the Welcome page.

    You can click IBM BPM for more information.

  5. Navigate around the administrative console to check that the enterprise applications and messaging engines are started. Also test the data source connections.

    If any application or process has failed to start, you can look in the Servant and Adjunct job logs for "SEVERE" or "WARNING" messages that provide details about the failure.

    Tip: In the default server log output, only the Sourceid and ExtendedMessage Trace lines are displayed. To display more detailed information about "SEVERE" or "WARNING" messages in the log, complete the following steps:

    1. In the administrative console, click Environment > WebSphere variables.

    2. Create a cell-scoped variable named private_bbor_condense_java_trace with a value of 0.
    3. Restart the server.

      If you view the log again, you should see additional lines for ThreadId, FunctionName, and Category.


What to do next

If all the messaging engines initialized correctly, and you do not see any other errors related to opening JDBC connections, you can continue to customize your configuration of IBM BPM.

For further information about how you can verify that the server is set up correctly, see Starting the cluster and verifying the installation.

Completing the stand-alone configuration


Related information:

Starting, logging on, and logging off the administrative console