Setup and Installation › › › Start the Services Using Oracle WebLogic/IBM WebSphere

Start the Services Using Oracle WebLogic/IBM WebSphere

Start the CA Clarity Application (app) and CA Clarity Background (bg) services. The configuration of the services uses Oracle WebLogic or IBM WebSphere as the application server.

Follow these steps:

1. Log in to CA Clarity System Administration.
2. Open the Installation menu, and click Install and Upgrade.
3. Click Package Application Ear.
4. Click Create Package.

   The application creates a package and the niku.ear.

5. At the command prompt, run the following command:

   admin general upload-all-config
   

6. Deploy the (niku.ear) package using the J2EE application server administration console.

Apply the Add-In

You can review changes to installed add-in items and review add-in updates using the details page for an add-in. The details page is available from the add-in page in Studio. If you have configured views when you install the add-in, the configurations remain and are not overwritten. You can decide which views to apply. If you are upgrading to the current add-in version, use the page to select new or modified items and apply them. Applying a view overwrites the configuration of the view.

Note: When you apply content from the add-in page, the access rights of your CA Clarity PPM system administrator user (admin) are used to install the content. Before using the add-in page to install content, grant or verify that the admin user has the appropriate Edit access rights for the type of content you are applying. For example, if you are applying project-based portlets, verify that the admin user has the Project - Edit Management – All access right.

This page lists all of the items that are included with the add-in. The following columns display on the page:

Status

Indicates if the add-in item is applied or not in CA Clarity PPM.

Values:

• Not Installed. New items that are new to the add-in version or that you did not apply from a previous add-in version.
• Upgrade Ready. Modified items that you applied from a previous add-in version and then configured. An update to the item is included in the current add-in version.

  Important! Consider the configurations that you have made to items before applying them. Applying modified items overwrites your configurations.

• Installed. Items that are installed.

Type

Indicates the item type.

Values: Object, Lookup, Tab, Query, Portlet, Page, Custom View, Group, Menu, Project, Process, Role, and Report/Job

ID

Displays the add-in item code, which is the identifier of the applied add-in item.

Follow these steps:

1. Log in to CA Clarity PPM.
2. Open Administration, and from Studio, click Add-ins.

   The add-ins page appears.

3. Click the name of the add-in to apply items.

   The details page for the add-in appears.

4. Review the items in the list and select for applying.

   Note: By default, when you upgrade to the current add-in version, the items that are new or modified are selected.

5. (Upgrade Only) For all active process instances with the "Upgrade Ready" status, cancel and delete the process instance.

   Contact your CA Clarity PPM administrator or see the Administration Guide for more information.

6. Click Apply.

   Note: If a selected item has dependencies on other items, the dependencies are also updated.

   A list of updated items displays on the confirmation or install page.

7. Click Yes.

   If a user has previously changed an item listed on the confirmation or install page, publish the item before displaying the update to the users.

   For more information, see the Studio Developer’s Guide.

The Default Remedy Clarity Integration Process

The Default Remedy Clarity Integration Process is included with this add-in. This process is built on the philosophy that you do your work in one place (that is, Remedy) and cost it in another (that is, CA Clarity PPM).

This process transfers cases from Remedy into CA Clarity PPM as incidents only after the assignee changes the case status to "Closed". If the assignee subsequently changes the case, you can run the process to transfer cases to CA Clarity PPM again. However, once a cases is transfered to CA Clarity PPM, effort or changes you make to the case in Remedy are not tracked in CA Clarity PPM.

More information:

Fault Handling During Connection

Configure the Default Remedy Clarity Integration Process

Fault Handling During Connection

You can incur errors during the connection and transfer of cases from Remedy to CA Clarity PPM incidents. The following is a list of possible errors and how the Default Remedy Clarity Integration Process process handles them:

• The Remedy resource attached to the incoming case does not exist in CA Clarity PPM.

  Handling: The incident is created and assigned to the Remedy Admin user. A message is logged in the process context. All such messages are mailed in a single batch to the Remedy Administrator.

• The Remedy category attached to the incoming case does not exist in CA Clarity PPM.

  Handling: A new incident category is created with the specified name. A warning message is logged that states that the new category was created.

• Generic incident XOG error.

  Handling: The error is logged and the CA Clarity PPM incident is not created or updated.

Configure the Default Remedy Clarity Integration Process

This Default Remedy Clarity Integration Process is designed to be useful and appeal to the widest possible audience. However, your company likely has unique requirements. You can configure this process to meet your company's needs.

You must configure the Default Remedy Clarity Integration Process to operate in your environment. To facilitate custom action process development, you can modify custom action scripts while the process is in Active mode or running.

Note: It is recommended that you save a copy of the process before configuring it so that you can later restore the process settings. To do this, click Save As, enter a different Process Name, ID, and Description for the process copy, and then click Save.

Contact your CA Clarity PPM administrator for more information.

Follow these steps:

1. Open the Administration Tool.

   The administration home page appears.

2. Open the Data Administration menu, and click Properties.

   The available processes page appears.

3. Click the name for the Default Remedy Clarity Integration Process.

   The properties page of process definition appears.

4. From the Properties menu, click Steps.

   The process definition page of steps appears.

5. For each step, do the following:
   1. Click the step name.

      The step details page of process definition page appears.

   2. In the Actions section, click Edit Custom Script.
   3. Open the Properties menu, and click Custom Script Parameters.

      The custom script parameters page appears.

   4. Enter the appropriate values:

      Step 1: Get Remedy Cases

      RemedyMidTierURL

      Defines the URL of the Remedy Mid-Tier application (including protocol, host address and port).

      Example: http://remedyweb.bigcorp.com:8080

      RemedyHost

      Defines the Remedy Action Request System server host address. This is not necessarily the same host used in the Mid-Tier URL.

      Example: remedy.bigcorp.com

      RemedyUsername

      Defines the username used to invoke the Remedy web service for reading Help Desk cases.

      RemedyPassword

      Defines the password for the Remedy user.

      Step 2: Create Incidents

      XOGURL

      Defines the application URL (including protocol, host address and port).

      Example: http://myApp.bigcorp.com

      XOGUsername

      Defines the user name for invoking the XOG web service for creating incidents.

      XOGPassword

      Defines the password for the XOG user.

      RemedyAdmin

      Defines the username of the user performing the Remedy Administrator role.

      Example: remedyadmin

      Step 3: Send Email

      EmailFrom

      Defines the email address from which notifications from in the process are sent.

      EmailFromName

      Defines the name associated with the email address above.

      EmailTo

      Defines the email address to which notifications from the process are sent.

   5. Click Save and Exit.
6. Open the Default Remedy Clarity Integration Process.

   The properties page of process definition appears.

7. From the Properties menu, click Validation.

   The process validation page appears.

8. Click Validate All and Activate to check for errors and activate the process.

   Note: There should be no validation errors in the default process. For any validation errors, address them prior to continuing.

   Your changes are saved.