Configuring Relationship Service

In the Relationship Service tab, you configure settings for the SBM Relationship Service, which enables you to view and analyze relationships between items in separate applications.

Tip: If you do not have a JBoss cluster for SBM Common Services, you do not need to change any of the settings on the Relationship Service as part of the initial configuration process. You can use the information below to configure Relationship Service settings any time thereafter.

Serena recommends that you wait to start the SBM Relationship Service on the Manage Services tab until after you have finished promoting all of the Release Manager process apps. (This service does not start automatically when you click Apply to finish the configuration process.) The initial loading that begins when the service starts consumes server resources and takes time to complete; therefore, start the service after you promote the apps in order to allow the promotion process to complete as quickly as possible.

The Relationship Service and database are installed on the server that hosts SBM Common Services. Therefore, there is only one active Relationship Service instance per SBM instance.

The Status section displays the current status and activity of the Relationship Service. For example, if you have never started the SBM Relationship Service on the Manage Services tab, the Relationship Service database is empty and not in use. That information is reported in the status section. After you start the service and the initial loading of data begins, the status is updated.

In the Database Server Settings section, enter the HTTP port that will be used to connect to the Relationship Service database. The default port value is 7474.

In the Database Settings section, configure the following settings:

Confirm or change the Database location that hosts the Relationship Service database. This database stores the relationships that exist between items in separate applications. Click Change to specify a different directory. If you change the directory after the initial load is finished and the database has been successfully created, you can choose to either copy the database to another location (for example, if the size of the database requires that you specify a different directory) or you can initialize a new loading process in another location.
Important: You must click Apply to begin the actual copy or loading process.
Enter a Backup Location for the Relationship Service database.
Tip: Once the backup database folder has been created, consider saving it to another server or separate partition in order to safely preserve your data.
Click Backup Now to create a backup copy of the database immediately in the directory that you specify.
Tip: Use this option if you need to create a backup of the database folder and move it to a new machine. For example, if you decide to create a cluster for SBM Common Services and as a result, you need to migrate the Relationship Service database to a new server, use the Backup Now option to create a backup of the directory that you need to move.
Click Schedule to open the Scheduler window and configure the backup frequency.

Configuring Relationship Service in a JBoss Cluster

You can improve Relationship Service performance by clustering the SBM Common Services component on multiple servers. When you create a cluster for SBM Common Services, the Cluster Settings group box appears in the Relationship Service sub-tab.

Each node in the cluster is capable of running Relationship Service; however, only one node in the cluster can actually run the service. You will enter the database settings on this node. All other nodes in the cluster must know the location of the node that will run the Relationship Service. No other Relationship Service configuration is required on these nodes.

To configure Relationship Service in a JBoss cluster, perform the following steps:

Define the nodes in your SBM Common Services cluster according to the steps described in "Clustering the JBoss Server Components" in the SBM Installation and Configuration Guide.
On the node that will run the Relationship Service, select the local host name in the drop-down list that appears.
On each node that will not run the service, select the host name of the node that will run the service.
Click Apply to save your changes.