|
Ready for IBM Tivoli software: Eligible product integrations
Validate your solution integration against one or more of the following IBM Tivoli software products. You can preview a brief summary of each product integration option.
You will find further details in the product requirements document included in the validation process.
IBM Tivoli Access Manager for e-business is a versatile solution for authentication and authorization problems. It manages growth and complexity, controls management costs and addresses the difficulty of executing security policies across a wide range of Web and application resources. It defines and manages centralized authentication, access, and audit policy. It also enables flexible single sign-on integration with Web-based applications spanning multiple sites and domains, while providing a modular authorization architecture that separates security code from application code.
To complete the Ready for IBM Tivoli software validation, one or more of the following options need to be implemented:
- Single sign-on integration (SSO): Tivoli Access Manager has a number of techniques for building an SSO solution using WebSEAL components.
- External Authentication C API (CDAS): This option allows you to substitute the default built-in WebSEAL authentication mechanism with a shared library for custom handling and processing of extended attribute and client authentication information.
- External Authentication Interface (EAI): EAI provides a means for solutions to supply an authenticated identity to WebSEAL and the Web server plug-ins.
- Common Authorization Model integration: Use the Authorization API (AznAPI) a C/C++ API ratified by the Open Group, JNI Wrappers of the Authorization API, or Java 2 Security Implementation (JAAS) in the Java Authorization API.
- Virtual Directory Server Integration: Dynamically translate received requests to operations in other protocols or data models like a relational database
Back to top
Change management, configuration management. These are at the core of any Service Management strategy. The IBM Tivoli Change and Configuration Management Database (CCMDB) provides an enterprise-ready platform for storing deep, standardized data on configurations and change histories to help integrate people, processes, information and technology. The Discovery Library integration provides a mechanism for communicating and sharing information about discovered resources and their relationships within the enterprise. The Discovery Library consists of the following components:
- Discovery Library XML schema specification, called the Identity Markup Language (IdML), defines a set of operations for creating, updating, and deleting objects in the Common Data Model.
- Discovery Library Adapters (DLA) contains application code written to extract discovered resources, their data relationship, and transform it to the IdML specification.
- Discovery Library books has XML files formatted to the IdML specification containing discovery information, including the identity of resources and their relationships.
- Discovery Library File Store is a repository for Directory Library books.
To complete the Ready for IBM Tivoli software validation one or more of the following options need to be implemented:
- Author Discovery Library Adapter: Your solution can create an IdML book.
- Reader Discovery Library Adapter: Your solution can retrieve information from Change and Configuration Management Database.
Back to top
IBM Tivoli Composite Application Manager for Response Time Tracking can proactively recognize, isolate, and resolve transaction performance problems using robotic and real-time techniques. It is an end-to-end transaction management solution that monitors end user response time and helps you visualize the transaction's path through your application systems, including response time contributions of each step.
Solutions that implement the Application Response Measurement (ARM) instrumentation can be integrated to use the Tivoli Composite Application Manager for Response Time Tracking management console. This is accomplished through the implementation of an XML file containing the application name, transaction groupings, individual transactions, and monitoring settings that describe the ARM instrumented transactions for the integrated solution. This allows customers to visualize their transaction topology, define thresholds for transactions, and receive alerts when transaction thresholds are violated. This includes the following capabilities:
- Discovery component allows identification of incoming Web transactions that need to be monitored.
- Listening components are the quality of service and J2EE monitoring components that collect data for actual user transactions that are executed against the Web servers and Web applications servers.
- Playback components are synthetic transaction investigator and Rational robot/generic Windows that robotically execute, or playback, transactions that are recorded to simulate actual user activity.
To complete a Tivoli Composite Application Manager for Response Time Tracking integrated solution validation, a technical paper or user's guide, XML file, and Web session are required to describe and demonstrate the integration.
Back to top
IBM Tivoli Directory Integrator synchronizes and exchanges information between applications or directory sources. It synchronizes identity data residing in directories, databases, collaborative systems, applications used for human resources (HR), customer relationship management (CRM) and enterprise resource planning (ERP), and other corporate applications. It serves as a flexible synchronization layer between a company's identity structure and the application sources of identity data, eliminating the need for a centralized data store.
To complete the Ready for IBM Tivoli software validation one or more of the following options need to be implemented:
- Custom connector(s): A connector is used to access and update information sources.
- Custom parser(s): A parser is used in conjunction with a transport Connector to interpret or generate the content that travels over the Connector's byte stream.
- Custom function component(s): An assembly line component that facilitates the wrapping of custom logic and external methods, and may present a user friendly "connector-like" user interface in the configuration editor (CE).
- Server API: Provides a set of programming calls that can be used to develop solutions and interact with the IBM Tivoli Directory Integrator (TDI) server locally and remotely.
Back to top
IBM Tivoli Enterprise Console consolidates events from networks, hardware and software throughout the environment. It provides an infrastructure overview and sophisticated, automated problem diagnosis and resolution to help you improve system performance and reduce your support costs. It also has pre-configured rules that provide best-practices event management.
To complete the Ready for IBM Tivoli software validation one or more of the following options need to be implemented:
- Create an IBM Tivoli Enterprise Console event adapter: Software component to handle integrated solution information for sending events to Tivoli Enterprise Console; Event Integration Facility (EIF) C or Java libraries, CLI adapter using 'wpostemsg' commands.
- Configure or customize one of the standard adaptors: Modify one of the Tivoli Enterprise Console default adaptors: logfile or SNMP adaptor.
- Creation of a BAROC file: The .baroc file defines the complete set of custom events that the adapter may send to the server in BAROC format. This file is imported into the current server rulebase so that events received from the adapter can be parsed.
- Optional rules file: Defines one or more rules for acting on the events defined in the .baroc file. This file is imported into the current Tivoli Enterprise Console server rule base. The rules may perform actions such as correlation between two events, automatically matching a closure event to a prior event when a problem is resolved.
Back to top
IBM Tivoli Federated Identity Management provides a simple, loosely-coupled model for managing identity and access to resources that span companies or security domains. Rather than replicate identity and security administration at both companies, Tivoli Federated Identity Manager provides a simple model for managing identities and providing them with access to information and services in a trusted fashion.
For companies deploying service-oriented architecture and Web services, Tivoli Federated Identity Management provides policy-based integrated security management for federated Web services. The foundation of Tivoli Federated Identity Management is trust, integrity, and privacy of data.
To complete the Ready for IBM Tivoli software validation one or more of the following options need to be implemented:
- SAML artifact: Two Web browser-based profiles of SAML are designed to support single sign-on. The browser/artifact profile and browser/post profile. In the Browser/post profile, SAML assertions are uploaded to the browser within an HTML form and conveyed to the destination site as part of an HTTP POST payload when the user submits the form.
- SAML Assertion elements and attributes: The set of elements and attributes Tivoli Federated Identity Manager requires are configurable. It has flexibility in the XSL rules on the IdP for producing assertions (IdP=producer) and SP (SP=consumer) side for consuming assertions.
Back to top
IBM Tivoli Identity Manager provides a secure, automated, policy-based user management solution. It helps enterprises set up new accounts and passwords quickly; including the ability for users to reset and synchronize their own passwords. A workflow engine handles automated submissions and approvals of user security requests. The embedded provisioning engine can be used to automate administrative requests to reduce costs involved with account, credential and access right management.
To complete the Ready for IBM Tivoli software validation one or more of the following options need to be implemented:
- API integration: Designed to allow access to the application layer of the Tivoli Identity Manager Platform. It can be used to develop a custom-lightweight user interface or integration.
- IBM Directory Integrator (IDI) integration: IDI is a data synchronization tool shipped with Tivoli Identity Manager to assist in manipulating data from a variety of identity sources.
- Workflow Extensions API: Allows definition of custom workflow units or extensions that are executed as part of the life cycle operation within the workflow engine.
Back to top
IBM Maximo Asset Management software capabilities maximize the lifetime value of complex assets and closely align them with your overall business strategy, allowing you to increase return on assets, decrease costs, increase productivity, improve asset-related decision-making, improve asset service delivery, improve regulatory compliance, increase business responsiveness, lower total cost of ownership.
Maximo Asset Management consists of six key systems that enable companies to successfully manage assets, including production equipment, facilities and transportation assets, in alignment with their business objectives.
Maximo provides the Maximo External Adaptor (MEA) to provide a default base for handling inbound and outbound transactions. MEA listens for events being routed by the Integration Component. For outbound transactions (events targeted at an external solution), MEA uses its router to provide a connection to the end point. For inbound transactions (events and data received by Maximo from external solutions), MEA uses its gateway to pick-up the transactions for processing. MEA can handle a number of interchange formats for handling inbound and outbound transactions.
To complete the Ready for IBM Tivoli software validation one or more of the following options need to be implemented with one of the indicated interfaces:
- Outbound interface: HTTP post, XML, tables, JMS queue, Enterprise Java Bean, or Web service
- Inbound interface: HTTP post, XML, tables, JMS queue, Enterprise Java Bean, Web service, or Gateway Web Service
Back to top
IBM Tivoli Monitoring is an enterprise-class solution that optimizes IT infrastructure performance and availability. It manages the IT infrastructure including operating systems, databases and servers across distributed and host environments through a single customizable workspace portal interface. Agents are used throughout the enterprise to monitor data sources reporting the results to the Tivoli Enterprise Management Server. Tivoli Monitoring contains a universal agent that can be configured as a generic agent to monitor your application through one or more data providers. A data provider acts as the interface between the universal agent and your application. A universal agent may be created by configuring one of the built-in data providers or by developing an additional data provider specific to monitoring your data source.
To complete the Ready for IBM Tivoli software validation one or more of the following options need to be implemented:
- Creation of a solution custom agent: Along with applicable custom workspaces, views, policies and actions, custom agent options include:
- Use any of the out-of-the-box universal agent data providers
- Create a custom universal agent data provider
- Tivoli Monitoring Web Services SOAP: This interface to query agent data is used in your solution.
- Tivoli Data Warehouse V2.1: Query and usage of historical agent data from the database used with monitoring.
Back to top
IBM Tivoli Netcool/OMNIbus is at the core of the Tivoli Netcool suite of software, a carrier-class service and business assurance system. The Tivoli Netcool/OMNIbus application focuses primarily on fault and event management. It collects and consolidates real-time events and alarms from a wide variety of networking environments. These environments include servers, mainframes, Microsoft Windows systems, UNIX applications, circuit switches, voice switches, IP routers, SNMP devices, network management applications and frameworks, among many others. Tivoli Netcool/OMNIbus presents this consolidated information in a meaningful, intuitive, point-and-click format providing information of interest to users through individually configurable filters and views. Using the Tivoli Netcool/OMNIbus real-time monitoring, you can address problems before they cause disruptions in service supporting continuity of business operations.
To complete the Ready for IBM Tivoli software validation one or more of the following options need to be implemented:
- Tivoli Netcool/OMNIbus rules files: This is for at least one of the standard-based Netcool/OMNIbus probes (the SNMP, TL1 or Syslog probes).
- Integration tool: This tool is used for the Tivoli Netcool/Desktop or Tivoli Netcool/Webtop clients.
- Tivoli Netcool/OMNIbus automations in the ObjectServer: The automation will detect pre-defined changes in the ObjectServer and execute automated responses to these changes. This enables the ObjectServer to process many alerts without requiring an operator to take action.
Back to top
Enterprise and service providers are realizing the strategic importance of network management. Tivoli NetView extends traditional network management to ensure the availability of critical business systems, and to provide rapid resolution of problems. Tivoli NetView discovers TCP/IP networks, displays network topologies, correlates and manages events and SNMP traps, monitors network health, and gathers performance data. Tivoli NetView meets the needs of managers of large networks by providing the scalability and flexibility to manage mission-critical environments.
To complete the Ready for IBM Tivoli software validation one or more of the following options need to be implemented:
- External Application Integration: ARF integration for application launch of the NetView Console
- MIB Integration: Product-specific SNMP MIB
- Event Integration: SNMP Trap definitions, a BAROC file for TEC server
- Service Monitoring Integration: Configure NetView servmon daemon to monitor applications
Back to top
IBM Tivoli Provisioning Manager enhances usability for executing changes while keeping server and desktop software compliant. Tivoli Provisioning Manager helps organizations with provisioning, configuration and maintenance of servers and virtual servers, operating systems, middleware, applications, storage and network devices acting as routers, switches, firewalls, and load balancers. Companies can leverage Provisioning Manager tools and automation capabilities against their existing infrastructure. Pre-built automation packages provide control and configuration of major vendors' products, while customized workflows can implement your company's best practices and procedures.
To complete the Ready for IBM Tivoli software validation an automation package (tc-driver) representing your solution or system needs to be implemented containing the following:
- User's guide in UTF-8 HTML format
- End user license agreement for the use of the automation package
- Automation workflows (base minimum requirements are listed in the product requirements document)
- XML for defining the solution in the data center
- Other content required for the automated deployment of solutions
- Automated integration scripts and files
Back to top
IBM Tivoli Storage Manager-Extended Edition expands on Tivoli Storage Manager back-up, restore and archive abilities to help expedite disaster recovery by creating a detailed plan and automated scripts, and disaster-recovery functionality can track where offsite copies of data are stored.
- Client API integration: Third party products can use Tivoli Storage Manager as a policy-managed storage repository, by integrating via the Client Application Programming Interface (API). Through Client API integration:
- Database applications can write data to a storage device as back-up.
- Back-up products can function as back-up clients for Tivoli Storage Manager.
- Applications can use Tivoli Storage Manager as a policy-managed storage repository.
- Network data management protocol: Network attached storage (NAS) devices integrate with Tivoli Storage Manager via the network data management protocol (NDMP) to perform high-performance, scalable backups and restores that minimize network traffic and transfer data.
- SAN hardware validation: Third-party SAN hardware devices can be validated with Tivoli Storage Manager through a system level test that emphasizes data movement through the SAN to a tape library and tape drive devices.
Back to top
IBM System Storage Archive Manager facilitates compliance with the most stringent regulatory requirements in the most flexible and function-rich manner. It helps manage and simplify the retrieval of the ever increasing amount of data that organizations must retain for strict records retention regulations. Many of the regulations demand the archiving of records, e-mails, design documents and other data for many years, in addition to requiring that the data is not changed or deleted.
IBM System Storage Archive Manager makes the deletion of data before its scheduled expiration extremely difficult. Short of physical destruction to storage media or server, or deliberate corruption of data or deletion of the Archive Manager database, Archive Manager will not allow data on the storage managed by the IBM System Storage Archive Manager server to be deleted before its scheduled expiration date. Content management and archive applications can apply business policy management for ultimate expiration of archived data at the appropriate time. Sold as a separately licensed software product integrated into Tivoli Storage Manager-Extended Edition server software, IBM System Storage Archive Manager requires a stand-alone Tivoli Storage Manager-Extended Edition server be dedicated for its use. It is accessible solely via the Tivoli Storage Manager API by a variety of content management or archive applications software applications.
To complete the Ready for IBM Tivoli software validation specific Tivoli Storage Manager Client API features need to be used to ensure the integration leverages critical data retention capabilities.
Back to top
|
|
|