Accessing the product

You need to start the IBM® Product Master services to access the product.

Starting the product

When you start the Product Master, you also start all the related services, and the application servers including the application server of the Global Data Synchronization feature.
Important: Before you start the product, you must ensure that you have configured the Global Data Synchronization application server in the [services] section of the env_settings.ini file.
You need to run the start_local.sh script to start the product and all of the services that are needed to run the product; and the rmi_status.sh script to verify that the application is running. You also need to start the messaging service of the Global Data Synchronization feature to send and receive XML messages. An environment, which provides graphical support (for example, VNC) is recommended. In case, global security is enabled in WebSphere® Application Server, but if the admin_security=false parameter is specified in the env_settings.ini file, you are prompted with a window to provide the WebSphere Application Server administrative user name and password. If you use an environment like PuTTY, which does not have graphical support, the execution of the command appears hung.

To start the services, proceed as follows:

  1. Run the start_local.sh script at the <install directory>/bin/go directory. If the admin_security=true parameter is set in the env_settings.ini file, but the user name and password are not provided in the [appserver] section, you should specify these values in the command line as follows:
    start_local.sh --wsadminUsername=<was_admin_user>
    --wsadminPwd=<was_admin_password>
  2. Run the gdsmsg.sh script at the <install directory>/bin directory with the start parameter if you have enabled the Global Data Synchronization feature. You can use the status parameter to fetch the status of the Global Data Synchronization listener service.
    $<Install_Dir>/bin/gdsmsg.sh start
  3. Run the rmi_status.sh script to verify that the application is up and running, and that the services have started. The following information is displayed:
    admin_<name of instance>
appsvr_<name of instance>
eventprocessor_<name of instance>
queuemanager_<name of instance>
scheduler_<name of instance>
workflowengine_<name of instance>

    This process takes approximately 30 - 40 seconds, depending on the speed of the processor.

Example
Following are the examples of the after running the rmi_status.sh script showing that all services have started on pimserver1
  • When Global Data Synchronization feature is enabled:
    [pim1@pimserver1 pim1]$ /opt/pim/pim1/pim900/bin/go/rmi_status.sh
[success] rmistatus (Mon Mar 8 14:00:49 PDT 2010)
//pimserver1:17507/samplemart/admin/admin_pimserver1
//pimserver1:17507/samplemart/appsvr/appsvr_pimserver1
//pimserver1:17507/samplemart/queuemanager/queuemanager_pimserver1
//pimserver1:17507/samplemart/workflowengine/workflowengine_pimserver1
//pimserver1:17507/samplemart/scheduler/scheduler_pimserver1
//pimserver1:17507/samplemart/eventprocessor/eventprocessor_pimserver1
  • Global Data Synchronization feature is not enabled:
    [pim1@pimserver1 pim1]$ /opt/pim/pim1/pim900/bin/go/rmi_status.sh
[success] rmistatus (Mon Mar 8 14:00:49 PDT 2010)
//pimserver1:17507/samplemart/admin/admin_pimserver1
//pimserver1:17507/samplemart/appsvr/appsvr_pimserver1
//pimserver1:17507/samplemart/queuemanager/queuemanager_pimserver1
//pimserver1:17507/samplemart/workflowengine/workflowengine_pimserver1
//pimserver1:17507/samplemart/scheduler/scheduler_pimserver1
//pimserver1:17507/samplemart/eventprocessor/eventprocessor_pimserver1

Logging in to the product

Product Master provides a browser-based user interface that you can use to manage and administer your system. You log in with the user name, password, and company that you created from the demonstration scripts.
  1. Open your web browser and enter the URL and port for the web server. It is important to enter a fully qualified host name along with "/utils/enterLogin.jsp". The URL is similar to the following:

    http://<DNS name or IP address>/utils/enterLogin.jsp

    Where,

    <DNS name or IP address> is the DNS name or the IP address of the system on which the product is running, and the port is defined in the common.properties file.

    Note: During the product installation, the web server port was set to 7507 in a two tier configuration. If a different port is used, change the port reference in the file server.xml for a three tier configuration.
  2. Use the user name, password, and company that was created from running the demonstration test scripts. For example, enter the following information:
    User name: Admin
    Password: trinitron
    Company Code: acme

    For more information, see Creating test company.

    Note: The ID and password information was hardcoded when you created the company by using the script, and hence are case-sensitive.

    If the product home page loads, the installation was successful. Log out of the application.

Stopping the product

To update or change the runtime configuration of the Product Master, you must stop the product and all the related services, and the application servers including the application server of the Global Data Synchronization feature.

You need to run the abort_local.sh script to stop the product and all of the services. You also need to stop the messaging service of the Global Data Synchronization feature. An environment, which provides graphical support (for example, VNC) is recommended. In the case where global security is enabled in WebSphere Application Server, but the admin_security=false parameter is specified in the env_settings.ini file, you are prompted with a window to provide the WebSphere Application Server administrative user name and password. If you use an environment like PuTTY, which does not have graphical support, the execution of the command appears hung.

To stop the product, proceed as follows:
  1. Run the abort_local.sh script at the <install directory>/bin/go directory. If admin_security=true parameter is set in the env_settings.ini file, but the user name and password are not provided in the [appserver] section, you should specify these values in the command line as follows:
    abort_local.sh --wsadminUsername=<was_admin_user>
    --wsadminPwd=<was_admin_password>
  2. Run the gdsmsg.sh script at the <install directory>/bin directory with the stop parameter, if you have enabled the Global Data Synchronization feature.
    • stop parameter - Use to complete processing the messages that have been picked from the message queue and then stop the Global Data Synchronization messaging service.
    • abort parameter - Use to stop the Global Data Synchronization messaging service immediately without processing the messages that have been picked from the message queue.
    $<Install_Dir>/bin/gdsmsg.sh stop