Launching the stand-alone Applications Manager and System Management Console

The stand-alone Applications Manager client eliminates the dependency on a browser and other related issues. Therefore, to access the Applications Manager and System Management Console, it is recommended that you use the stand-alone Applications Manager client.

You can generate the stand-alone Applications Manager client by using the om-base container image.

Before you begin

Set up an om-base container by following the instructions provided in Customizing and generating container images.

Note:
  • A stand-alone Applications Manager that is built from a specific version of the om-base container can connect to Sterling™ Order Management System Software of the same version. To check the product version, see the About box in the application that is deployed.
  • Whenever the base product version changes, you must repeat the build steps to obtain a new stand-alone Applications Manager.
  • The single sign-on YCPSSOManager login with stand-alone Applications Manager is applicable from the 10.0.2306.2 release.
  • If you override the default web.xml for Application Console in the INSTALL_DIR/repository/eardata/smcfs/extn/web.xml location, you must compare the existing web.xml from the 10.0.2306.2 release and merge the changes. This is required for the passcode login to work.

About this task

You can launch the stand-alone Applications Manager from the command line to connect to any Sterling Order Management System Software environment that is on the same product version.

Procedure

  1. Browse to <runtime>/bin of the om-base container and run the following command:
    ./sci_ant.sh -f buildApplicationManagerClient.xml.
    The AppManager_10.0.zip file is generated inside the <runtime>/ApplicationManagerClient directory.
  2. Browse to the ApplicationManagerClient folder in the om-base container.
  3. Copy and extract the contents of AppManager_10.0.zip to the target environment where you want to launch the Applications Manager.
  4. Browse to the directory where the client_10.0.jar is present.
  5. Launch the applications by running the following commands:
    • To launch the stand-alone Applications Manager, run the following command:
      java -jar client_10.0.jar
    • To launch the System Management Console, run the following command:
      java -jar client_10.0.jar -mode SMC

    The following table lists the flags that you can pass to the JVM when running the program:

    Flags passed to the JVM Description
    URL The URL of the application server. For example, https://localhost:9080
    U The username of the user. For example, admin.
    P The password of the user. For example, password.
    CR The context root of the application. For example, /smcfs.
    mode The application to start.

    The valid values are:

    • <nothing> - Not passing this flag launches the Applications Manager
    • SMC - System Management Console
    • YCD - YCD Applications Manager
  6. If the single sign-on is implemented by providing a class that implements the YCPSSOManager interface and by setting the yfs.yfs.security.singlesignon.enabled property to Y in customer overrides, complete the following steps.
    1. Select the Passcode Login checkbox.
    2. Update the IP address and port in the Application Console URL field, and copy the URL.
    3. In a browser, paste the URL and log in to the Application Console.
    4. Open another tab in the browser. The Login window opens. In the Open Following URL in browser field, paste the URL.
    5. Copy the passcode that is displayed in the showpasscode page and paste it in the login dialog for the stand-alone Applications Manager.
    6. Click OK to confirm.