Skip to content
CA Workload Automation DE - 12.0
Documentation powered by DocOps

Starting the Server

Last update October 4, 2018

This section contains the following topics:

Server Recycling

To recycle the server, you must stop it and then restart it. You can stop the server through the Command Line Interface (CLI) or from the computer where the server is installed. However, you cannot restart the server from the Command Line Interface (CLI). To restart the server, you must start it from the computer where it is installed.

Note: Recycling the server does not start or stop the default agent.

Start the Server on Windows

To use the server, you must first start it.

To start the server on Windows, select Start, Programs, programgroup, CA WA Server, startServer.

  • programgroup
    Specifies the Program Group in the Windows Start menu where the server shortcuts are located.

A console window opens and closes. The server runs as a Windows service.

Note: Alternatively, if you did not create Windows Start menu shortcuts during installation, you can start the server as a service by opening the Services dialog in Windows, right-clicking the service name for the server, and selecting Start from the pop-up menu. You can also start the server in console mode by running the startServer.exe program in a command prompt window. The startServer.exe program is located in the bin directory where the server is installed. In console mode, the server stops running if the command prompt window is closed.

Start the Server on UNIX

To use the server, you must first start it.

To start the server, change to the following directory and enter the ./startServer command.

install_dir/bin

  • install_dir
    Specifies the server installation directory.

A message is displayed indicating that the server started.

Alternatively, if you created a service for CA Workload Automation DE, you can start the server using Linux System Services. For example, to start the server on RHEL7, run the following command:

Systemctl start service_name

  • service_name
    Specifies the name of service that you created for CA Workload Automation DE on UNIX.

Cold and Warm Start

The server starts with either a warm start or a cold start. By default, the server starts with a warm start. You rarely need to perform a cold start. However, if required, you can perform a cold start on the server in a single server (stand-alone) configuration or in a CA WA High Availability configuration.

Important! When you perform a normal cold start, the server deletes all active workload and associated states, and you lose all active processing data.

When the server starts, it uses the start type specified in the runonce.properties file, which is located in the directory where the server is installed. If the runonce.properties file is named runonce.properties.bak, the server does not process the file and uses a warm start by default. The runonce.properties.bak is a backup file.

The following table describes the impact of a warm and normal cold start on active workload, Events, resource status, and global variables:

Area Impacted Effect of Normal Cold Start Effect of Warm Start
Active workload Deletes any active workload and associated states. Reads active workload from the time the server shuts down. At startup, the server continues running workload from this point onward.
Events Does not process Events that have not been processed at the time of shutdown. Reads and schedules Events that have not yet been processed at the time of shutdown and continues monitoring for Events that are to be processed.
Resource status Reverts the status of all logical resources to their original definition. Reads the status of all logical resources from the time of shutdown and continues managing resource states from this point onward.
Global variables Reads the global variables and continues managing them. Reads the global variables and continues managing them.
Note: You can configure the server to delete global variables and contexts in a warm or cold start. However, we recommend that you delete variables and contexts by using the CLI (Command Line Interface). For more information about using the CLI, see Command Line Interface (CLI). For more information about configuring the server to delete global variables and contexts in a warm or cold start, see Starting the Server.

Perform a Cold Start on a Single Server

You can perform a cold start on a server in a single server (stand-alone) configuration when you want to restart the server and delete all active workload and processing data.

Follow these steps:

  1. Stop the server.
  2. Do one of the following:
    • On Windows, open the following file in a text editor:

      install_dir\conf\runonce.properties.bak

    • On UNIX, open the following file in a text editor:

      install_dir/conf/runonce.properties.bak


      install_dir
      Specifies the directory where the server is installed.

  3. Update the start.type parameter to the following:

    start.type=COLD

  4. Modify the following parameter:

    start.type.level=level

    • level
      Specifies the cold start level. Options are the following:
      • -2
        Specifies that the server starts with a normal cold start, but scheduled Events that were not yet processed at the time of shutdown are rescheduled (a SCHEDULEALLEVENTS request). Events that require a manual trigger are not preserved.
      • -1
        Specifies that the server starts with a normal cold start and the generation count for all Applications is set to 0 (zero).
      • 0
        Specifies a normal cold start.
      • 1
        Specifies that the server starts with a cold start, but all scheduled Events are preserved. Events that were not yet processed at the time of shutdown continue to trigger after the server starts. Events that require a manual trigger are also preserved.
      • 2
        Specifies that the server starts with a cold start, but active workload is preserved. Workload that was running at the time of shutdown continues to run after the server starts.
      Default: 0
      Example: start.type.level=-1
  5. Save and close the file.
  6. Remove the .bak extension from the file name.
    The file is renamed to runonce.properties.
  7. Start the server.
    The server is cold-started.

    Note: When the server starts, it renames the runonce.properties file to runonce.properties.bak.

Perform a Cold Start in a CA WA High Availability Configuration

You can perform a cold start on the Primary and Standby servers in a CA WA High Availability configuration when you want to restart the servers and delete all active workload and processing data.

Note: Both Primary and Standby servers must be stopped. Otherwise, the cold start cannot take effect.

Follow these steps:

  1. Stop the Standby server.
  2. Stop the Primary server.
  3. Do one of the following:
    • On Windows, open the following file in a text editor:

      install_dir\conf\runonce.properties.bak

    • On UNIX, open the following file in a text editor:

      install_dir/conf\runonce.properties.bak


      install_dir
      Specifies the directory where the Primary server is installed.

  4. Update the start.type parameter to the following:

    start.type=COLD

  5. Modify the following parameter:

    start.type.level=level

    • level
      Specifies the cold start level. Options are the following:
      • -2
        Specifies that the server starts with a normal cold start, but scheduled Events that were not yet processed at the time of shutdown are rescheduled (a SCHEDULEALLEVENTS request). Events that require a manual trigger are not preserved.
      • -1
        Specifies that the server starts with a normal cold start and the generation count for all Applications is set to 0 (zero).
      • 0
        Specifies a normal cold start.
      • 1
        Specifies that the server starts with a cold start, but all scheduled Events are preserved. Events that were not yet processed at the time of shutdown continue to trigger after the server starts. Events that require a manual trigger are also preserved.
      • 2
        Specifies that the server starts with a cold start, but active workload is preserved. Workload that was running at the time of shutdown continues to run after the server starts.
      Default: 0
      Example: start.type.level=-1
  6. Save and close the file.
  7. Remove the .bak extension from the file name.
    The file is renamed to runonce.properties.
  8. Start the Primary server.
    The Primary server is cold-started.

    Note: When the server starts, it renames the runonce.properties file to runonce.properties.bak.
  9. Start the Standby server.
    The Standby server is cold-started.

Delete Global Variables in a Cold Start

When you perform a cold start of the server, global variables and contexts are not deleted. The global variables are stored in the relational database. When the server starts, it reads the global variables and continues managing them. To delete global variables and contexts, we recommend that you use the CLI (Command Line Interface). However, if you want to delete all global variables and contexts in a cold start, you can change the default start behavior.

Follow these steps:

  1. Stop the server.
  2. Open the following file in a text editor:
    • On Windows:

      install_dir\conf\runonce.properties.bak

    • On UNIX:

      install_dir/conf/runonce.properties.bak

    • install_dir
      Specifies the server installation directory.
  3. Uncomment the following parameter in the file:

    global.variables.cold.start=true

  4. Save and close the file.
  5. Rename the runonce.properties.bak file to runonce.properties.
    The file is renamed to runonce.properties.
  6. Start the server.
    The server starts running. The global variables and contexts are deleted.

    Note: When the server starts, it renames the runonce.properties file to runonce.properties.bak. The global variables and contexts are preserved the next time the server starts.
Was this helpful?

Please log in to post comments.