Planning › CA EEM and CA Workflow Installation Planning › CA Workflow Considerations

CA Workflow Considerations

Before you install CA Workflow, consider the following information to help ensure a successful implementation:

• CA Workflow is installed on the following CA SDM servers, depending on your CA SDM configuration:
  • Conventional: Primary or secondary server
  • Advanced availability: Any one of the application servers
• CA MDB Database User or Password—Consider the following information:
  • If you change either the CA MDB database user or password after the initial CA SDM installation, rerun the CA Workflow installation so CA Workflow applies the changes and can communicate with CA SDM. When you rerun the CA Workflow installation, CA SDM automatically sets the new user name or password for CA Workflow and you are not able to change the values manually during the CA Workflow installation.

    Note: Oracle environmental variables must be set before installing CA Workflow on UNIX and Linux. If the ORACLE_HOME variable is not set, you receive an error message when clicking the install link.

  • If you are migrating to a new database, run the Workflow Migration Utility.
• IPV6—If your Linux server is configured for IPv6 support, you might be unable to log in to the CA Workflow IDE. To correct this situation, modify the ide.sh script file located in $NX_ROOT\site\Workflow\Client by changing the second line which reads: "VMARGS=" to read: "VMARGS=-Djava.net.preferIPv4Stack=true". Then, save the script file and start the CA Workflow IDE again.
• Tomcat—Consider the following information:
  • If you have any difficulties with Tomcat being started, and as a result, the CA Workflow and web interface are not available, increase the Tomcat memory.

    Note: For information about how to address this situation, search for the Knowledge Base Article TEC418959 on http://ca.com/support.

  • During the installation of CA Workflow, CA SDM and CA EEM share a separate port number for Tomcat. If you have any difficulties with Tomcat when installing or using CA Workflow, stop and restart the service.
  • The CA Workflow host name that you specify in options manager must match the NX_LOCAL_HOST variable in the NX.env file of the server where you installed CA Workflow. The host name must also match the correct case sensitivity.
  • If you have installed and changed the installation defaults for the Tomcat port (8080) or the default privileged userid/password (ServiceDesk/ServiceDesk), make the following changes to the default CA Workflow definitions/actors so they work properly.
  • Log on to Workflow IDE.

    Complete the following steps to modify the default Service Desk Web Service Actor:

    1. Click the Actors tab.
    2. Expand the Web Service tree.
    3. Right-click the Unicenter_Service_Desk_Web_Service actor and select Properties.
    4. Select and copy the content of the WSDL URL entry.
    5. Modify the name of the actor and click OK.
    6. Right-click the Web Service Tree and select Add Actor.
    7. In the Name field, enter Unicenter_Service_Desk_Web_Service.
    8. In the WSDL URL entry, paste the previously copied content.
    9. Modify the port number in the URL to match the port number selected during the Tomcat configuration.
    10. Click OK.
  • After you install CA Workflow on the CA SDM server, complete the following steps so that the integration between CA SDM and CA Workflow works successfully:
    • Log in to the CA Workflow IDE to modify the default CA SDM Web Service Actor.
    • Select the Actors tab, expand the JavaScript tree, and click USDInitializer.
    • Double-click Get Global Attributes.
    • Enter the CA SDM privileged user name and password in the following fields under the script section:

      USD_Username = ""

      USD_Password = ""

    • Modify these values in the $NX_ROOT/data/workflow/actors/r12_Service_Desk_Actors_en_US.xml file.

More information:

How to Install CA Workflow