Setting up global configurations

Application administrators can use the following information to understand what to configure and where to configure it so that Global Configuration Management (GCM) works with the IBM® Engineering Lifecycle Management (ELM) applications that are enabled for configuration management.

Prerequisites

About this topic

This topic describes a typical deployment, which has one GCM instance (regardless of the number of Jazz Team Server instances) across the deployment. If your organization has teams with isolated ELM deployments that need to collaborate across multiple lines of business, you can set up multiple GCM instances in a deployment so that teams can share global configurations. This is an advanced feature. To set up your deployment in this way, read this topic carefully, and then see Enabling GCM servers to contribute configurations to other GCM servers.

Note: A GCM installation has a self-signed certificate for the local host (localhost), but users access GCM through the fully qualified domain name. Therefore, browsers display a warning if the site is untrusted. Even after you add a security exception, the browser might block key dialog boxes, such as those that list configurations from ELM applications. Either of the following solutions fix the problem:
  • Request a certificate that is signed by a trusted certificate authority (CA). The signed certificate eliminates the warnings from the browser. For details, see Installing a security certificate.
  • Generate a self-signed secure sockets layer (SSL) certificate for the host name. Additionally, each user must follow the steps in Configuring a browser to work with self-signed certificates. Because Google Chrome uses the certificates that are set in Microsoft Internet Explorer, Chrome users can follow the instructions for Internet Explorer and then restart Chrome.

Setup

  1. Run the Jazz Team Server setup, which registers and sets up all the ELM applications that you installed on the Jazz Team Server, including GCM. In a distributed environment, you must run the Jazz Team Server setup on the other Jazz Team Server instances to ensure that the applications are registered correctly. For details, see Completing the installation of Jazz Team Server and ELM applications.
  2. If the ELM and GCM applications are registered to the same Jazz Team Server, activate configuration management as described in Setting up ELM applications to use local configurations. Otherwise, follow the steps in Additional steps for a multiple Jazz Team Server topology.

Additional steps for a multiple Jazz Team Server topology

Some distributed deployments have multiple Jazz Team Server instances, which can improve scalability, increase redundancy, or avoid a single point of failure. To set up global configurations in a distributed deployment, you must complete the following steps.

Note: If your browser blocks pop-up dialog boxes that you need to log in to GCM or ELM, see Pop-up blocker preventing GCM or ELM login.
  1. Set up a directional friend relationship from GCM to each contributing ELM application.
    1. Add the applications that GCM needs as friends.

      Set friend relationships. On the Application Administration - Global Configuration Management page, on the Application tab, in the Communication section, under Friends (Outbound), add a friend relationship to each ELM application.

      Ensure that you accept each incoming friend relationship from within the respective ELM application, in the following way.
      • For the RM application: Authorize the friend relationship on the OAuth Consumers page of the Jazz Team Server of the RM application, not on the RM Administration page. On the toolbar, click Administration > Jazz Team Server Home > Manage Server > Consumers (Inbound).
      • For other applications: Authorize the friend relationship on that application's administration page: Application Administration page > Consumers (Inbound) > OAuth Consumers page.

      For details, see Configuring friends.

    2. Set a functional user for each row that shows the authorized friends you just added.

      On the same OAuth Consumers pages, set the functional user for the friend (/gc for the GCM application) that was authorized for each ELM application.

      The functional user does not require any privileges and can be any user on the Jazz Team Server of that GCM instance. For convenience, you can use the pre-defined application users, such as ccm_user, qm_user, rm_user, and dm_user for the respective ELM application.

      For details, see Editing consumer keys.

  2. Set up a directional friendship from each contributing ELM application to GCM.
    1. Add GCM as a friend to each ELM application.

      Ensure that you accept each incoming friend relationship from within the GCM application on the GCM Application Administration page > Consumers (Inbound) > OAuth Consumers page.

      For details, see Configuring friends.

    2. Configure the user that the ELM application uses to make requests to GCM.

      On the same OAuth Consumers page, set the functional user for each friend that GCM authorized (one for each ELM application).

      The functional user does not require any privileges and can be any user on the remote Jazz Team Server. For convenience, you can use the pre-defined functional user, gc_user.

      For details, see Editing consumer keys.

  3. Set the Global Configuration Provider URL property for each Jazz Team Server in the topology, except the one that GCM is registered to, so that contributing applications use the correct GCM instance.

    This property is on the Jazz Team Server server properties page, in the Global Configuration SDK set of server properties. The URL must have a fully qualified domain, for example, https://example:9443/gc/.

    For details, see Configuring advanced properties.

  4. Specify the link index (LDX) provider URL on the Jazz Team Server properties page for each Jazz Team Server in the topology, except the one that LDX is registered to.

    Edit the Link Index Provider URL property in the Links Component set of server properties. The value must be a URL with a fully qualified domain, for example, https://example:9443/ldx/.

    For details, see Configuring advanced properties.

  5. Activate configuration management as described in Setting up ELM applications to use local configurations.

The setup is complete.


video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki