Jazz for Service Management Version 1.1. Offering Guide

Transcription

1 Jazz for Service Management Version 1.1 Offering Guide

2

3 Jazz for Service Management Version 1.1 Offering Guide

4 Note Before using this information and the offering it supports, read the information in Notices on page 25. This edition applies to Version 1.1 of Jazz for Service Management and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2012, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures v Tables vii Chapter 1. Jazz for Service Management overview OSLC and Jazz for Service Management Jazz for Service Management integration services.. 3 Administration Services Dashboard Application Services Hub Registry Services Security Services Tivoli Common Reporting Jazz for Service Management architecture Getting started with Jazz for Service Management 12 Chapter 2. Jazz for Service Management references Common directory locations Notices Support information and feedback Index Copyright IBM Corp. 2012, 2013 iii

6 iv Jazz for Service Management: Offering Guide

7 Figures 1. Integration through Jazz for Service Management Jazz for Service Management physical architecture Jazz for Service Management software dependency diagram Copyright IBM Corp. 2012, 2013 v

8 vi Jazz for Service Management: Offering Guide

9 Tables 1. Summary of tasks to plan and install Jazz for Service Management Summary of tasks to configure Jazz for Service Management Summary of tasks to administer Jazz for Service Management Summary of tasks to integrate with Jazz for Service Management Copyright IBM Corp. 2012, 2013 vii

10 viii Jazz for Service Management: Offering Guide

11 Chapter 1. Jazz for Service Management overview Jazz for Service Management brings together the Open Services for Lifecycle Collaboration (OSLC) community's open specifications for linking data and other shared integration services, including administrative, dashboard, reporting, and security services. It underpins client-defined management scenarios such as cloud, performance monitoring, and IT Service Management. Through these facets, Jazz for Service Management accelerates deployment, integration, and workflow automation across IBM, partner, and third-party tools. Its open and standardized approach to linking data means that clients and partners can rapidly deploy and improve collaboration across interdependent roles and functions with less labor and cost, and regardless of the source and the management scenarios applied. Furthermore, this approach significantly reduces the risk of broken integrations, because it is not version or vendor API specific. The integration services provide key features that include: v Shared data repository for products that integrate through Registry Services in Jazz for Service Management v Consistent dashboard and visualization experience through IBM Dashboard Application Services Hub in Jazz for Service Management v Simplified administration of products and solutions that integrate through Administration Services in Jazz for Service Management v Ad hoc, self-service reporting through IBM Tivoli Common Reporting in Jazz for Service Management v Lightweight Third-Party Authentication (LTPA) single sign-on participation by non WebSphere IBM and partner application servers that integrate through Security Services in Jazz for Service Management Jazz for Service Management adds value through: v Open architecture for integrating IBM and other vendors products to deliver overall solution value v Single point of configuration and administration of all solutions v End-to-end view of IT resource, application, and business relationships v Linked IT resources to management capabilities v Real-time, dynamic federated data v Provision of unique insight Copyright IBM Corp. 2012,

12 Figure 1. Integration through Jazz for Service Management OSLC and Jazz for Service Management Jazz for Service Management is the result of participation by IBM in the Open Services for Lifecycle Collaboration (OSLC) community. The integration through Jazz for Service Management is based on the OSLC approach of loosely coupled integration, which follows these principles: v v v v Build on the architecture of the WWW and follow the Representational State Transfer (REST) architectural pattern. Keep things simple, building on a few simple concepts and adding only the minimum needed to support identified scenarios. Accommodate different domain-specific schemas, representing everything as resources and properties. Services can provide information about resource shape and properties. Align with the W3C Linked Data initiative and the Resource Description Framework (RDF). Use Universal Resource Identifiers (URIs) as names for things. Use HTTP URIs so that people can look up those names. When someone looks up a URI, provide useful information, by using the standards. For example, RDF. 2 Jazz for Service Management: Offering Guide

13 v Include links to other URIs so that they can discover more information. Accommodate different representations, such as RDF/XML, JavaScript Object Notation (JSON), and HTML. RDF/XML is the minimum required. Jazz for Service Management enables a flexible approach to information, interface, and functional integration across IBM and third-party tools, including: v v v Registry Services is OSLC-compliant and enables reconciliation of data across multiple sources. Linked data allows pulling details from source, rather than always duplicating them locally. Standardized OSLC interfaces enable third parties and partners to more easily integrate with IBM interfaces. OSLC Core Specification Version 2.0 OSLC Reconciliation Wiki OSLC community Jazz for Service Management group at Service Management Connect Chapter 5 Representational State Transfer, Architectural Styles and the Design of Network-based Software Architectures. Fielding, Roy Thomas. Doctoral dissertation, University of California, Irvine, 2000 W3C Linked Data Jazz for Service Management integration services Jazz for Service Management has a number of integration services: Administration, Registry, IBM Tivoli Common Reporting, Security, and IBM Dashboard Application Services Hub. Administration Services Administration Services in Jazz for Service Management is an integration service that simplifies the administration of Tivoli products, solutions, or third-party solution in your environment. Through Administration Services, you can manage various aspects of these products and solutions in your environment, such as health, configuration, availability, lifecycle, and serviceability. Administration Services has a common and consistent administrative interface that simplifies a wide range of administrative tasks to manage the products and solutions, representing service management systems. Administration Services provides the following benefits: v Provides comprehensive visualization of the health of your integrated management environment v Reduces the dependencies on highly skilled personnel to administer a heterogeneous collection of service management products v Enables teams to use knowledge from subject matter experts v Reduces the time to detect, isolate, and resolve problems v Improves predictability and repeatability v Reduces the time to upgrade existing service management capabilities v Improves user experience in the administration of service management products in the environment Chapter 1. Jazz for Service Management overview 3

14 Administration Services components Administration Services has a user interface, command-line interface, and a set of reusable and pluggable components to manage the integration services in Jazz for Service Management and the resources in your integrated service management environment. Administration service provider The administration service provider is an Administration Services component that integrates with Registry Services to register service management systems as resources. It also manages data about the configuration tasks that are associated with these managed resources. The administration service provider is deployed to the Jazz for Service Management application server during installation to administer other integration services. It can also be deployed to a stand-alone Administration Services server, when it is used to administer a service management system in an enterprise s environment. The administration service provider is an OSLC service provider and provides Administration Services features by using RESTful services. Administration Services client The Administration Services client provides a command-line interface to manage registration of the administration service provider, its managed resources, and tasks. Administration Services UI The Administration Services UI provides the visualization of service management systems and their configuration status as dashboards deployed to Dashboard Application Services Hub. Administration Services task bundles Administration Services provides task bundles for the following integration services, which represent service management systems: Registry Services, Dashboard Application Services Hub, and Tivoli Common Reporting. When you install Administration Services with Registry Services, Dashboard Application Services Hub, or Tivoli Common Reporting, Administration Services registers the integration services as managed resources and registers the respective task bundles. Task Bundle Builder The Task Bundle Builder is an Administration Services tool. It defines the task bundle structure, tasks, and metadata in the task bundle, so that you can easily create and build a task bundle for a service management system. Dashboard Application Services Hub Dashboard Application Services Hub provides visualization and dashboard services in Jazz for Service Management. It has a single console for administering IBM products and related applications. 4 Jazz for Service Management: Offering Guide

15 Robust integration platform Provides a Web 2.0 based Systems Management integration platform that has the following features: v Support for data processing and rendering of content from multiple sources, which is integrated and presented in interactive dashboards v Support for multiple user personas, for example, system integrators, administrators, users, and application developers v Support for single sign-on and a unified security model Highly customizable Supports proportional dashboard creation that allows users with appropriate permissions to create dashboards by using a self-service palette. They can arrange widgets to be dynamically displayed in proportion to their size. Multiple widgets can be arranged on the dashboard in a very flexible and proportional manner. Supports fluid dashboard creation that allows users with appropriate permissions to create dashboards using a self-service palette. Widgets are dynamically be rearranged depending on the available screen size. This type of dashboard is suitable for mobile devices, including tablets and smart phones. Enhanced UI experience Employs a series of intuitive icons to access non-core customization, administration, and user management tasks, thereby providing more area for displaying user content Eliminates siloed product consoles that require users to move between separate applications to carry out service management tasks. Users can start from one application to another within the same dashboard view and drill down into different aspects of their managed enterprise. Implements a IBM One UI standards-compliant UI that provides a number of user assistance paths, as follows: v A Welcome page that provides access to a tour of the UI. It also provides shortcuts to common administrative tasks such as creating pages or managing user roles. v Configuration and administration pages includes inline user assistance, which is supported by online help. v The Dashboard community at Service Management Connect is linked directly from the UI. Registry Services Registry Services is an integration service that provides a shared data repository for products in an integrated service management environment. Products that discover and manage shared IT resources can register these IT resources and the services they offer with Registry Services. Other products can consume data by querying Registry Services for the managed resources or the associated service providers of interest. Registry Services provides these benefits: v Accommodates different domain-specific schemas. v Simplifies resource management tasks. It is built on simple concepts and adds only the minimum concepts that are required to support various scenarios. Chapter 1. Jazz for Service Management overview 5

16 v v Supports different data representations, such as RDF/XML and JSON, being JSON supported as data representation in Provider Registry only. Enables products to provide their own Resource Shape definitions and properties. Registry Services concepts Registry Services has fundamental concepts that you must know before you manage the integration of services and the resources in your integrated environment. Service Provider Record A record that contains information about the Service Provider resource that represents a registered OSLC service provider of a product. It contains inline resources that describe the services of the service provider and the creation, query, and delegated UI capabilities of each service. Registration Record A record that contains information about a resource that is managed by a product and a URL which refers to the product record for that resource. Registration Records indicate that there is an OSLC provider with information about a resource, along with a reference to the domain-specific record in the provider repository. Resource Record A record that contains a merged representation of the data from different Registration Records that refer to the same resource. It includes the union of resource properties from the Registration Records and URLs pointing to the records in the product repositories. These URLs can provide more domain-specific details. Resource Shape definitions Definition of a resource type, including descriptions of properties that are expected for specific operations, such as create, update, and query, including their value types, allowed values, and cardinality. It also includes identification rules, which are used to construct reconciled Resource Records from Registration Records. Getting started with Registry Services Jazz for Service Management community at Service Management Connect OSLC community OSLC Reconciliation Wiki OSLC Core Specification 2.0 OSLC Automation Specification Version 2.0 Dublin Core Metadata Element Set, Version 1.1 Hypertext Transfer Protocol (HTTP/1.1) RDF/XML Concepts and Abstract Syntax RDF / XML Syntax Specification (Revised) URI Generic Syntax Namespaces in XML 1.0 (Third Edition) XML Schema Part 2: Datatypes Second Edition 6 Jazz for Service Management: Offering Guide

17 Registry Services components Registry Services has an application, database, and command-line interface that provide set of features to manage the integration of services and the resources in your integrated environment. Provider Registry A directory to contain services that are provided by multiple products across different domains. It is implemented as an OSLC container for managing Service Provider resources. Resource Registry A directory to contain resources that are managed or tracked by multiple products across different domains. It is implemented as an OSLC container. Registry Services application An enterprise application that exposes and manages the Provider Registry and the Resource Registry. It is deployed to the Jazz for Service Management application server. Registry Services database A DB2 database in which the primary Registry Services records are stored. Registry Services command-line interface A set of commands to run from the command line that configure and administer the Registry Services application and database. Security Services Security Services in Jazz for Service Management enable the servers of non-websphere based IBM and partners to participate in LTPA based single sign-on with WebSphere servers. When multiple products and user interfaces are integrated together, the transition from one UI to another should appear as seamless as possible. One aspect of this integration involves single sign-on (SSO) functionality, which allows a user to navigate among various products and user interfaces without being required to enter authentication credentials, such as username and password, more than once. WebSphere products include SSO functionality based on IBM's Lightweight Third-Party Authentication (LTPA) technology. When properly configured, this functionality supports navigation among WebSphere-based applications, passing authentication information as LTPA tokens in HTTP cookies. A user is prompted for authentication credentials only once, and any subsequent authentications are automatically handled under the covers by using the LTPA tokens included in the associated Web requests. Authentication Service in Security Services provides user registry and LTPA single SSO integration with non-websphere applications. Security Services provide the Authentication Service that supports issuing and validating LTPA tokens. It is based on the Web Services Trust (WS-Trust) specification and is deployed as an application to the WebSphere Application Server on the Jazz for Service Management server. The Authentication Service authenticates users through the provision of a user name and password (basic authentication) or a token assertion. It defines a WS-Trust profile to request security tokens (RST) and respond to these security Chapter 1. Jazz for Service Management overview 7

18 token requests (RSTR) that support both basic authentication and token assertion. The Authentication Service performs authentication against a Lightweight Directory Access Protocol (LDAP) user registry. After successful authentication, the Authentication Service returns the security token, user, and group information as required. Related information: OASIS Web Services Secure Exchange (WS-SX) Technical Committee Security Services components Security Services provides the Authentication Service and a Software Development Kit to develop Authentication Service clients. Authentication Service This component provides user registry and LTPA SSO integration with non WebSphere applications. It supports issuing and validating LTPA tokens. The Authentication Service is based on the Web Services Trust (WS-Trust) specification and is deployed as an application to the WebSphere Application Server on the Jazz for Service Management server. The Authentication Service authenticates users through the provision of a user name and password (basic authentication) or a token assertion. It defines a WS-Trust profile to request security tokens (RST) and respond to these security token requests (RSTR) that support both basic authentication and token assertion. The Authentication Service authenticates against a Lightweight Directory Access Protocol (LDAP) user registry. After successful authentication, the Authentication Service returns the security token, user, and group information as required. Authentication Service client Software Development Kit This component provides a set of API packages with JAR files that security developers can use to develop Authentication Service clients in Java. It also provides a sample application package that contains a sample Authentication Service client application and its source code. Related information: OASIS Web Services Secure Exchange (WS-SX) Technical Committee Tivoli Common Reporting Reporting Services in Jazz for Service Management is an integration service for users to administer, run, edit and create Tivoli reports. It is a follow-on implementation of the Tivoli Common Reporting component. Reporting Services provide web based, launch-in-context report administration and editing. 8 Jazz for Service Management: Offering Guide With Tivoli Common Reporting, you get the following advantages: Simplified interaction Simplified interfaces and interactions for report writers to create, customize, and publish reports faster and easier. Reporting workspaces, with free form layout, lets users drag and drop sections from different reports to create workspaces with reporting content and enhance interactivity. Powerful report formats Built-in interactivity provided by Active Reports format. users an active report, which has interactive functions that the users can use offline. Interactive functions include clickable charts, sorting, tabs and radio buttons, and check box filtering.

19 Trending capabilities Provides ability to add trending to a report by using bar, line, area, bubble, and scatter charts, and with just a few clicks. Supports averages across series or for each series. Mobile device support Supports viewing and running reports on mobile devices, including Apple ipad, iphone, Android, Blackberry and Windows. Uses native applications for ipad and Blackberry. Users can also interact offline with Active Reports with the ipad application. On-demand and self-service reporting Bridges gap between business and professional report authors. Enable report users to create and save multi-query ad hoc reports through the drag and drop features, without the need for professional report writer s involvement. Supports enhanced user experience through easy modification of layout and format. Users can drag and resize widgets. They can filter data with a few clicks. Users can choose from a greater variety of charts to support trending. Compatible with IBM Cognos Report Studio. Cross-product report linking Extends the capability of cross-product report linkage for seamless flow between related reports of various Tivoli products. Robust Reporting Engine Simplified configuration with Java Database Connectivity (JDBC) support. Optimized SQL generation of complex queries for better runtime performance. Tivoli Common Reporting components Tivoli Common Reporting consists of data stores, reporting engines, their corresponding web user interfaces displayed in Dashboard Application Services Hub, and a command-line interface. Tivoli Common Reporting provides a flexible structure that can be adapted for load balancing. The core components are as follows: Cognos-based Tivoli Common Reporting engine The dispatcher is the entry point for IBM Cognos service requests sent by a web server gateway or other software. The dispatcher handles the routing requests and balances the load of user requests to the various IBM Cognos services. Cognos gateway A portal for communication between Tivoli Common Reporting Server and the Cognos-based Tivoli Common Reporting engine. Cognos Content Store A database that contains data that IBM Cognos uses to operate. The data comprises report specifications, published models, and the packages that contain them; connection information for data sources; information about the external namespace, and the Cognos namespace itself; and information about scheduling and bursting reports. Chapter 1. Jazz for Service Management overview 9

20 Common Reporting user interface A web user interface that is based on Dashboard Application Services Hub. It provides a portal for IBM Cognos and a component that interacts with the Cognos Content Store. The user interface is used to publish, find, manage, organize, and view organization's reports. Tivoli Common Reporting is based on Cognos Business Intelligence Reporting version The following Cognos components are available with Tivoli Common Reporting: v Framework Manager - a modeling tool for creating data models. v Query Studio -areporting tool for creating simple queries and reports. v v v Report Studio - a web-based tool for creating sophisticated reports against multiple databases. Connection - an application where you can view and manage all your reports. Workspace - a web-based tool for authoring simple reports and exploring your data v Workspace advanced - a tool for performing advanced data analysis and creating reports with various data sources. For information about professional services, education or technical assistance with Cognos, visit the IBM Cognos Customer Center. For information about using the product, visit Cognos information center. Jazz for Service Management architecture When you install all integration services, Jazz for Service Management should be distributed across three servers, database, enterprise, and UI and reporting servers. If you choose to install only one or a subset of integration services, Jazz for Service Management can also be deployed to one or two servers. Figure 2 on page 11 shows the physical architecture for Jazz for Service Management in a three-server topology, with the following Jazz for Service Management servers: Application server 1: Jazz for Service Management enterprise server The Jazz for Service Management enterprise server is a descriptive term for a back end application server on which WebSphere Application Server is installed. The Jazz for Service Management extension for IBM WebSphere is then installed into the WebSphere Application Server installation directory, which provides a set of WebSphere add-on files that the integration services require. This server can contain the Registry Services, Administration Services, and Security Services applications that are deployed to the same WebSphere application serving environment. Application server 2: Jazz for Service Management UI and reporting server The Jazz for Service Management UI and reporting server is a descriptive term for a front end application server, on which WebSphere Application Server and the Jazz for Service Management extension for IBM WebSphere are installed. This server can contain Dashboard Application Services Hub, Administration Services, and Tivoli Common Reporting that are deployed to the same WebSphere application serving environment. Database server: Jazz for Service Management database server The Jazz for Service Management database server is a descriptive term for 10 Jazz for Service Management: Offering Guide

21 a server on which IBM DB2 is installed. The DB2 database instance manages the Registry Services database. It can also manage the database for the IBM Cognos Content Store in the same DB2 instance. Note: The database server might also maintain the high availability database for Dashboard Application Services Hub. Figure 2. Jazz for Service Management physical architecture Figure 3 on page 12 shows the dependencies between the integration services and the middleware. Chapter 1. Jazz for Service Management overview 11

22 Figure 3. Jazz for Service Management software dependency diagram Getting started with Jazz for Service Management Different user types can use Jazz for Service Management and its integration services to help them meet their user goals. Consult the summaries of tasks, including installation, configuration, administration, integration, and user tasks. Stage one: Planning and installing Jazz for Service Management Table 1 summarizes the steps to plan and install Jazz for Service Management. Table 1. Summary of tasks to plan and install Jazz for Service Management Task Description Plan your installation You can choose to perform a simple or custom installation of Jazz for Service Management. Different factors determine which installation scenario you should choose, for example, the integration services to install, business and security policies, your target environments, and user types. You can choose to perform a simple or custom installation of Jazz for Service Management. These installation scenarios support installing Jazz for Service Management on a single server or on multiple servers in a distributed environment. Prepare your environment For more information, see Planning your installation in the Jazz for Service Management Installation Guide. You must prepare your environment whether you perform a simple or custom installation. Some tasks are common to both installation scenarios, while some tasks are exclusive to a single installation scenario or integration service. For more information, see the Preparing your environment topic in the Jazz for Service Management Installation Guide. 12 Jazz for Service Management: Offering Guide

23 Table 1. Summary of tasks to plan and install Jazz for Service Management (continued) Task Description Perform a simple installation Use this installation scenario to install and configure IBM DB2, IBM WebSphere Application Server, and Jazz for Service Management on a single server. After you provide basic information, the simple installation scenario silently installs DB2, WebSphere Application Server, Installation Manager, and the following integration services: Administration Services, Dashboard Application Services Hub, Registry Services, Security Services, and optionally Tivoli Common Reporting. The launchpad can run Prerequisite Scanner to scan for simple installation prerequisites. When you install Administration Services with Registry Services, Dashboard Application Services Hub, or Tivoli Common Reporting, Administration Services registers these service management systems as managed resources and deploys the respective task bundles. Perform a custom installation For more information, see Simple installations in the Jazz for Service Management Installation Guide. Use this installation scenario to install and configure one or more integration services on different servers. You can choose to install WebSphere Application Server and Installation Manager, if you do have existing installations of these products. You can use Installation Manager to interactively install and configure the following integration services: Administration Services, Dashboard Application Services Hub, Registry Services, and Security Services on one, two, or three servers. After your perform a custom installation, you can install Tivoli Common Reporting. When you install Administration Services with Registry Services, Dashboard Application Services Hub, or Tivoli Common Reporting, Administration Services registers these service management systems as managed resources and deploys the respective task bundles. Depending on your business and security policies, you can also review installation and configuration scripts before your install, or you can enable your environment for Federal Information Processing Standards (FIPS). Install Tivoli Common Reporting Perform post-installation tasks For more information, see Custom installations by using Installation Manager GUI, Custom installations by using silent mode, Custom installations for FIPS enablement, and Custom installations to support business policies in the Jazz for Service Management Installation Guide. You can install Tivoli Common Reporting, its content store, and its optional components after you install Dashboard Application Services Hub. Tivoli Common Reporting has a runtime dependency on Dashboard Application Services Hub. Note: You can choose to install Tivoli Common Reporting during the simple installation flow. For more information, see Installing Tivoli Common Reporting in the Jazz for Service Management Installation Guide. Verify the installation and perform optional Tivoli Common Reporting tasks. For more information, see Post-installation tasks in the Jazz for Service Management Installation Guide. Chapter 1. Jazz for Service Management overview 13

24 Stage two: Configuring Jazz for Service Management During installation by Installation Manager, an integration service is also configured. By default, an integration service is configured to use basic authentication over HTTPS. Table 2 summarizes configuration information and typical configuration tasks for all integration services and for only an individual integration service. Table 2. Summary of tasks to configure Jazz for Service Management Service Task Cross-service 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. 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. 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 For more information about common configuration tasks, see the Jazz for Service Management Configuration Guide. 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. Dashboard Application Services Hub For more information about configuring Administration Services, see Configuring Administration Services in the Jazz for Service Management Configuration Guide. 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 about configuring Dashboard Application Services Hub, see Configuring Dashboard Application Services Hub in the Jazz for Service Management Configuration Guide. 14 Jazz for Service Management: Offering Guide

25 Table 2. Summary of tasks to configure Jazz for Service Management (continued) Service Task Registry Services 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. Security Services Tivoli Common Reporting For more information about configuring Registry Services, see Configuring Registry Services in the Jazz for Service Management Configuration Guide. 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 about configuring Security Services, see Configuring Security Services in the Jazz for Service Management Configuration Guide. 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 about configuring Tivoli Common Reporting, see Configuring Tivoli Common Reporting in the Jazz for Service Management Configuration Guide. What is next for administrators: Administering integration services Table 3 summarizes the typical administration tasks common to all integration services or specific to an individual integration service. Table 3. Summary of tasks to administer Jazz for Service Management Service Task Cross-services You might need to restart Jazz for Service Management application servers as a step to complete an administration task, allowing the changes to take effect. Restarting a server impacts all integration services applications that are installed in the same WebSphere application serving environment. You might need to assign roles to users and groups depending on the access level that they require for an integration service, its features, and resources. For more information, see Administering Jazz for Service Management in the Jazz for Service Management Administration Guide. Chapter 1. Jazz for Service Management overview 15

26 Table 3. Summary of tasks to administer Jazz for Service Management (continued) Service Task Administration Services Administrators might need to assign the default PlatformMonitor, PlatformOperator, PlatformConfigurator, and PlatformAdministrator roles to users and groups. Administrators can use Administration Services to administer the service management systems running in the enterprise environment, including other integration services. They can check the status and health of the managed systems. Administrators can run tasks to check the health of your managed systems. They can run tasks to fix any issues that are flagged by a warning or error status in the Administration Services or in the command window after you run the configuration client. During the installation of the integration services in the same Installation Manager software package group during installation, that is, the JazzSM_HOME directory, the Administration Services task bundles for the following integration might be installed: Dashboard Application Services Hub, Registry Services, and Tivoli Common Reporting. You can work with these tasks in the Administration Services UI or from the command line. Dashboard Application Services Hub For more information about administering Dashboard Application Services Hub, see Administering your integrated service management environment in the Jazz for Service Management Administration Guide. Console administrators can set up the console for use by users at your site, including presentation and authorization. Administrators can assign the default User, Privileged User, Editor, and Managers roles to users and groups. They might need to create custom roles or map users and user groups to roles. Console administrators can change users passwords or log out one or more active users. Console administrators can also export and import console data for backup or migration. They can specify which mobile agents are allowed to render the Dashboard Application Services Hub mobile console. Registry Services For more information about administering Dashboard Application Services Hub, see Administering Dashboard Application Services Hub in the Jazz for Service Management Administration Guide. Administrators might need to assign the default RegistryClientRole, RegistryProviderAdminRole, and RegistryAdminRole roles to users and groups. Administrators might need to modify the Registry Services settings to troubleshoot or enhance performance. They can change the log and trace settings, data source settings, maximum number of HTTP sessions and connection pool size. Administrators can also use the Registry Services CLI to manage Resource Shape definitions, configure and remap URLs, manage cleansing rules, and other health and performance tasks. Administrators might also need to back up and restore the Registry Services as part of the organization s backup and recovery strategy. For more information about administering Registry Services, see Administering Registry Services in the Jazz for Service Management Administration Guide. 16 Jazz for Service Management: Offering Guide

27 Table 3. Summary of tasks to administer Jazz for Service Management (continued) Service Task Security Services Administrators might need to assign the default TrustClientRole security role to users and groups. Administrators might also need to back up and restore the Authentication Service as part of the organization s backup and recovery strategy. Tivoli Common Reporting For more information about administering Security Services, see Administering Security Services in the Jazz for Service Management Administration Guide. Administrators might need to assign the default tcrportaloperator security role to users and groups. For more information, see Managing Jazz for Service Management users and groups in the Jazz for Service Management Administration Guide. What is next for developers: Integrating with integration services Table 4 summarizes the typical integration tasks for each integration service. Table 4. Summary of tasks to integrate with Jazz for Service Management Service Task Administration Services Work with the Task Bundle Builder to create tasks and build task bundles that can be deployed to the Administration Services application. After deployment, operators can run these tasks for a managed system. Set up Eclipse to install the Task Bundle Builder update site feature. Create the task bundle shell. Add the task to the project. Package the task bundle. Test and debug. Dashboard Application Services Hub For more information about integrating with Administration Services, see Integrating with Administration Services in the Jazz for Service Management Integration Guide. Work with Dashboard Application Services Hub to customize the console for your visualization and dashboarding needs. Become familiar with the layout of the console, its key elements, and features. Determine how many dashboards that you require, the predefined or custom widgets to use, and the data sets and the data providers for those widgets. Determine how to organize the dashboards to ensure that navigation is intuitive for your users. Build your dashboards and custom widgets, debug, test, and deploy to your production environment. For more information about integrating with Dashboard Application Services Hub, see Integrating with Dashboard Application Services Hub in the Jazz for Service Management Integration Guide. Chapter 1. Jazz for Service Management overview 17

28 Table 4. Summary of tasks to integrate with Jazz for Service Management (continued) Service Task Registry Services Work with the Registry Services Provider Registry and the Resource Registry to share data and information with other products in an integrated service management environment. The Provider Registry is a directory of services that are provided by products and categorized by the service management domain in which the products operate. Resource Registry is a directory of resources that are managed or tracked by multiple providers across different domains. If an OSLC provider, advertise your product s services through the Provider Registry by creating Service Provider Records. Other products can then locate these services and consume them. Register the IT resources that you manage or discover, and which are of interest to other products involved in integration scenarios, by creating Registration Records in the Resource Registry. By creating these Records, it also indicates that you have domain-specific information about the resources. If an OSLC consumer, locate the required services in the Provider Registry by locating the relevant Service Provider records. Use the Resource Registry to have a unified and detailed view of the resources and links to Resource Records from multiple OSLC providers. You can then locate the required resources in the Resource Registry by locating the Registration Records. Security Services For more information about integrating with Registry Services, see Integrating with Registry Services in the Jazz for Service Management Integration Guide. Work with the Authentication Service to integrate with the user registry and single sign-on that are provided through the Jazz for Service Management WebSphere profile. Applications, including OSLC applications, that are not run in a WebSphere application serving environment, can invokeauthentication Service clients to connect and authenticate with the Authentication Service. You can develop Authentication Service clients in Java and other programming languages. For more information about integrating with Security Services, see Integrating with Security Services in the Jazz for Service Management Integration Guide. What is next for operators and managers: Using integration services Integration service Dashboard Application Services Hub Task You can log in to the console by using one of the supported browsers. The console has different accessibility features for vision-impaired, mobility impairments, and deaf and hard of hearing users. Understand the different elements of the user interface, including features accessible from the Welcome, About, and Show Tab List pages. You can also change your password. You can use different features of the console to personalize your experience. You can configure your default views and add commonly used navigation items to your favorites list. You can edit dashboards and layout, including widgets that depend on your access level. For more information about using Dashboard Application Services Hub, see Using Dashboard Application Services Hub in the Jazz for Service Management User s Guide. 18 Jazz for Service Management: Offering Guide

29 Integration service Tivoli Common Reporting Task Use Tivoli Common Reporting to run, view, or reports. Create report schedules to run reports at specified intervals. Perform ad hoc reporting. Import or export report packages as required. Create custom reports in a web-based tool. For more information about using Tivoli Common Reporting, see Using Tivoli Common Reporting in the Jazz for Service Management User s Guide. Chapter 1. Jazz for Service Management overview 19

30 20 Jazz for Service Management: Offering Guide

31 Chapter 2. Jazz for Service Management references Common directory locations The references contain information and examples for command-line interfaces, scripts, and properties files that are provided by the integration services. It also contains a reference for different directories and paths that the integration services use. Jazz for Service Management topics use path name variables for paths to common directories, for example, home directories. Jazz for Service Management home directory The JazzSM_HOME variable describes the location where Jazz for Service Management is installed. This location can be specified during installation. If not specified, the following default locations are used: v On UNIX systems: /opt/ibm/jazzsm v On Windows systems: C:\Program Files\IBM\JazzSM Jazz for Service Management profile directory The JazzSM_WAS_Profile variable describes the location of the application server profile that is used for Jazz for Service Management. This location is in the /profile/ subdirectory of the Jazz for Service Management home directory. v On UNIX systems: /opt/ibm/jazzsm/profile v On Windows systems: C:\Program Files\IBM\JazzSM\profile Jazz for Service Management profile name The JazzSM_Profile_Name variable refers to the name assigned to the WebSphere Application Server profile for Jazz for Service Management. The default name is JazzSMProfile. Installation images home directory The Install_Imgs_Home variable describes the common root directory that contains the extracted contents of the installation images depending on the installation scenario. v Simple installation IBM DB2, IBM WebSphere Application Server, and IBM Tivoli Common Reporting if you want to install Tivoli Common Reporting during the simple installation flow. Attention: You must extract the contents of the installation media for this software to the same common root directory, otherwise the simple installation displays error messages for missing software. v Custom installation IBM WebSphere Application Server, if you do not want to use an existing installation; Tivoli Common Reporting if you want to install it after a custom installation of the other integration services. Copyright IBM Corp. 2012,

32 Note: It is not necessary to extract the contents of the installation media for this software to the same common root directory, but it is preferable to maintain all extracted installation media in a central location. Jazz for Service Management installation images home directory The JazzSM_Image_Home variable describes the common root directory in which the Jazz for Service Management is extracted. It contains the launchpad, IBM Installation Manager, IBM Prerequisite Scanner, the Installation Manager repository with the software packages for the integration services except Tivoli Common Reporting, and IBM Tivoli Directory Integrator. Tip: Ensure that the path to the JazzSM_Image_Home directory does not contain any spaces or special characters, otherwise the launchpad does not start. IBM DB2 home directory The DB2_HOME variable describes the location where IBM DB2 is installed. This location was specified during installation. If not specified, the following default locations are used: v v On UNIX systems: /opt/ibm/db2/vversion_number for root user installations and $HOME/sqllib for non-root user installations, where $HOME represents the non-root user's home directory. On Windows systems: C:\IBM\SQLLIB WebSphere Application Server home directory The WAS_HOME variable describes the location where WebSphere Application Server is installed. This location was specified during installation. If not specified, the following default locations are used: v On UNIX systems: /opt/ibm/websphere/appserver v On Windows systems: C:\Program Files\IBM\WebSphere\AppServer Administration Services home directory The ADMIN_HOME variable describes the location where Administration Services is installed. This location can be specified during installation. If not specified, the following default locations are used: v On UNIX systems: /opt/ibm/jazzsm/admin v On Windows systems: C:\Program Files\IBM\JazzSM\admin Administration Services UI home directory The ADMINUI_HOME variable describes the location where Administration Services UI is installed. This location can be specified during installation. If not specified, the following default locations are used: v On UNIX systems: /opt/ibm/jazzsm/admin_ui v On Windows systems: C:\Program Files\IBM\JazzSM\admin_ui Registry Services home directory The REGISTRY_HOME variable describes the location where Registry Services is installed. This location can be specified during installation. If not specified, the following default locations are used: 22 Jazz for Service Management: Offering Guide