LinuxAIX

Changing the process execution properties

Altering the process execution properties is a required step in the federation process.

About this task

After you federate a WebSphere Commerce application server node into a cell, you must change the process execution properties for node agents and for the application servers.

Complete the following procedure for each node that is added to a deployment manager cell.

Procedure

  1. Ensure that you are logged in to the application server node as the non-root user.
  2. On the application server node, from the WC_profiledir/bin directory, start the node agent if it is not already started. Running the addNode command when federating nodes starts the node agent automatically, so the node agent might already be running. See:
  3. Ensure that you are logged in as the user that can start your deployment manager application server.
  4. On the WebSphere Application Server Network Deployment machine, start the deployment manager application server.
  5. Open the WebSphere Application Server Administrative Console.

    Ensure that you are accessing the administrative console on the WebSphere Application Server Network Deployment (deployment manager) machine and not a WebSphere Application Server (node) machine.

  6. Complete the following steps:
    1. In the Navigation area, expand Servers and click Application Servers. The Application Servers page displays.
    2. On the Application Servers, click the name of the application server. For WebSphere Commerce, the application server name is server1.
    3. In the Server Infrastructure section, expand Java and Process Management. Click Process Execution. The Process Execution page displays.
    4. In the Run as user field, enter the non-root user ID that was created before WebSphere Commerce was installed.
    5. In the Run as group field, enter the user group to which the non-root user ID belongs.
    6. In the UMASK field, enter 027.
    7. Click OK.
    8. Click Save in the administrative console taskbar.
    9. Click Review to save your changes.
    10. On the Save page, select Synchronize changes with Node.
    11. On the Save page, click Save.
    12. Restart the application server to make this configuration change take effect.
  7. Configure the node agent by completing the following steps:
    1. In the Navigation area, expand System Administration and click Node Agents.
    2. Select the node agent for the node on which the WebSphere Commerce application is running.
    3. In the Server Infrastructure section, expand Java and Process Management. Click Process definition. The Process definition page displays.
    4. Click Process execution. The Process execution page displays.
    5. In the Run as user field, enter the non-root user ID that was created before WebSphere Commerce was installed.
    6. In the Run as group field, enter the user group to which the non-root user ID belongs.
    7. In the UMASK field, enter 027.
    8. Click OK.
    9. Click Save in the administrative console taskbar.
    10. Click Review to save your changes.
    11. On the Save page, select Synchronize changes with Node.
    12. On the Save page, click Save.
    13. Restart the node agent to make this configuration change take effect.
  8. Configure the deployment manager by completing the following steps
    1. In the Navigation area, expand System Administration and click Deployment Manager.
    2. In the Server Infrastructure section, expand Java and Process Management. Click Process definition. The Process definition page displays.
    3. Click Process execution. The Process execution page displays.
    4. In the Run as user field, enter the non-root user ID that was created before WebSphere Commerce was installed.
    5. In the Run as group field, enter the user group to which the non-root user ID belongs.
    6. In the UMASK field, enter 027.
    7. Click OK.
    8. Click Save in the administrative console taskbar.
    9. Click Review to save your changes.
    10. On the Save page, select Synchronize changes with Node.
    11. On the Save page, click Save.
    12. Restart the deployment manager to make this configuration change take effect.
  9. Exit the WebSphere Application Server administrative console.
  10. Stop the node agent. For information about how to stop the node, see stopNode command.