Configuring the process spawner

You can configure an Application Server to spawn processes externally to the Application Server process. If you configure an Application Server in this way, a separate dedicated process (the process spawner) is used only for spawning processes. When the Application Server needs to spawn a process, it contacts the process spawner, which starts a new child process. The Application Server transfers the necessary information to the child process. Spawning processes externally can be beneficial for memory management. Primarily, an Application Server spawns processes for Network Shell Script Jobs and some types of extended objects.

Note

The process spawner was used in TrueSight Server Automation 8.6 and earlier versions to improve performance of the NSH Script jobs on the Solaris SPARC platforms. We recommend not to use the process spawner in 8.6 and later versions. 

To configure the process spawner, perform the following procedures:

To configure an Application Server to use the process spawner

  1. Start the Application Server Administration console for the Application Server that you want to execute the NSH jobs. For example:
    blasadmin -s JobServer1
    For more information about methods for starting this console, see Starting-the-Application-Server-Administration-console.

  2. To specify that processes be spawned externally from the Application Server process, enter the following:
    set ProcessSpawner SpawnExternally true
    Setting this value to false indicates the process spawner runs within the Application Server process. By default, this value is set to false.

    Note

    If you set the ProcessSpawner SpawnExternally value to true, BMC recommends that you run the following command before starting the Application Server service (to avoid connection refused failures for any scheduled jobs):
    run/etc/init.d/blprocserv start (UNIX)
    net start "BladeLogic Process Spawner" (Windows)

  3. Specify a port for communicating with the process spawner. Enter the following:
    set ProcessSpawner RegistryPort #
    where # is the number of a port. The default port is 1067 and is the port recommended by TrueSight Server Automation.
  4. Restart the Application Server.

To configure the process spawner

  1. Start the Application Server Administration console for the process spawner deployment.
    blasadmin -s _spawner
    For more information about methods for starting this console, see Starting-the-Application-Server-Administration-console.
  2. Set the Registry Port for the process spawner to match the port specified to the when you configured the Application Server to use the process spawner. Enter the following:
    set AppServer RegistryPort #
    where # is the number of a port. The default port is 1067 and is the port recommended by TrueSight Server Automation.
  3. Restart the process spawner.
  4. Do one of the following:
    • On Windows, from the Start menu, select Settings > Control Panel.
      1. Double-click Administrative Tools, and double-click Services.
      2. Right-click TrueSight Server Automation Process Spawner and select Restart from the pop-up menu.
    • On a UNIX system, enter the following:
      /etc/init.d/blprocserv restart

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*