How do I configure Jazz for Service Management

You can configure a central user registry, such as a Lightweight Directory Access Protocol (LDAP) registry, for Jazz for Service Management user management and authentication.

Configure WebSphere Application Server to use a central federated repository with an LDAP user registry. After configuration, you can add users to the federated repository. For more information, see Configuring Jazz for Service Management for a central user registry.

You can configure the integration services for single sign-on, so that users can access Jazz for Service Management applications by logging in only once. For more information, see Configuring Jazz for Service Management for SSO.

During installation, the global security configuration is enabled that applies to the security policy for all administrative functions in each Jazz for Service Management application server. The configuration is also used as a default security policy for user applications.

Administration Services is configured during installation.

You can reconfigure the connection to the Registry Services application. You can manually install task bundles for other integration services because of installation problems.

For more information, see Configuring Administration Services.

Dashboard Application Services Hub is configured during installation.

For installations of Dashboard Application Services Hub with large user populations, you can set up a load balancing cluster of console nodes with identical configurations to evenly distribute user sessions.

You can choose to configure Dashboard Application Services Hub to use Tivoli® Access Manager WebSEAL Version to manage authentication.

You can also configure the Context Menu Service (CMS) to use a remote database, which can be used by products to share information outside of the Dashboard Application Services Hub environment.

You can modify the Apache ActiveMQ polling intervals properties to change the frequency of polls that handle data provider events, which are sent to the web clients.

For more information, see Configuring Dashboard Application Services Hub.

Registry Services is configured during installation.

You configure Registry Services for secure access to all its features. You can also configure Registry Services to support the HADR mode and configure specific settings to avoid performance issues.

You can work with these configuration tasks through either administrative console or command-line interface. Use the Registry Services CLIs to configure specific Registry Services settings. For example, you can define a public URL, set the Registry Services operation mode, customize Resource Shape definitions, and more.

For more information, see Configuring Registry Services.

Security Services is configured during installation except for single sign-on with LDAP, which is done by configuring Jazz for Service Management for SSO. You can update the configuration, for example, applying new versions of tokens.

For more information, see Configuring Security Services.

After you install Tivoli Common Reporting, prepare your report packages to be able to generate, publish, and edit your reports.

You can configure database connection details to a data source other than DB2®.

You can configure sample audit reports to view information about user and report activity.

For installations of Tivoli Common Reporting with large user populations, you can set up a load balancing cluster of console nodes with identical configurations to evenly distribute user sessions.

For more information, see Configuring Tivoli Common Reporting.