Donnerstag, 31. Januar 2008

Application deployment using Tivoli Provisioning Manager and Rational ClearQuest

This demo begins with the role of a project manager approving a request for deployment of version 2 that resolved a defect in the Web banking application. The initiation to deploy the application is done using Rational ClearQuest. The deployment to distribute the application is done by Tivoli Provisioning Manager. After observing the deployment, the demo transitions to the role of the tester and confirms that the deployed application is functioning correctly. You'll observe how Rational ClearQuest is used to track deployments of applications that support governance/compliance processes that require approval. You'll also see how deployment work flows in Tivoli Provisioning Manager can be initiated remotely through a ClearQuest action.

Application deployment using Tivoli Provisioning Manager and Rational ClearQuest

This demo begins with the role of a project manager approving a request for deployment of version 2 that resolved a defect in the Web banking application. The initiation to deploy the application is done using Rational ClearQuest. The deployment to distribute the application is done by Tivoli Provisioning Manager. After observing the deployment, the demo transitions to the role of the tester and confirms that the deployed application is functioning correctly. You'll observe how Rational ClearQuest is used to track deployments of applications that support governance/compliance processes that require approval. You'll also see how deployment work flows in Tivoli Provisioning Manager can be initiated remotely through a ClearQuest action.

Application deployment using Tivoli Provisioning Manager and Rational ClearQuest

This demo begins with the role of a project manager approving a request for deployment of version 2 that resolved a defect in the Web banking application. The initiation to deploy the application is done using Rational ClearQuest. The deployment to distribute the application is done by Tivoli Provisioning Manager. After observing the deployment, the demo transitions to the role of the tester and confirms that the deployed application is functioning correctly. You'll observe how Rational ClearQuest is used to track deployments of applications that support governance/compliance processes that require approval. You'll also see how deployment work flows in Tivoli Provisioning Manager can be initiated remotely through a ClearQuest action.

Application deployment using Tivoli Provisioning Manager and Rational ClearQuest

This demo begins with the role of a project manager approving a request for deployment of version 2 that resolved a defect in the Web banking application. The initiation to deploy the application is done using Rational ClearQuest. The deployment to distribute the application is done by Tivoli Provisioning Manager. After observing the deployment, the demo transitions to the role of the tester and confirms that the deployed application is functioning correctly. You'll observe how Rational ClearQuest is used to track deployments of applications that support governance/compliance processes that require approval. You'll also see how deployment work flows in Tivoli Provisioning Manager can be initiated remotely through a ClearQuest action.

Dienstag, 8. Januar 2008

SOA authorization using Tivoli Federated Identity Manager and WebSphere Service Registry and Repository

This article describes a service-based approach to authorization in Service Oriented Architecture (SOA) environments using IBM Tivoli Federated Identity Manager (TFIM). This approach extends existing IBM solutions for identity propagation in SOA by leveraging Tivoli Access Manager (TAM) as the authorization policy decision point. A software utility to discover services from the IBM WebSphere Service Registry and Repository (WSRR) to enable the authorization solution will be provided to simplify and accelerate deployment of this authorization solution.

SOA authorization using Tivoli Federated Identity Manager and WebSphere Service Registry and Repository

This article describes a service-based approach to authorization in Service Oriented Architecture (SOA) environments using IBM Tivoli Federated Identity Manager (TFIM). This approach extends existing IBM solutions for identity propagation in SOA by leveraging Tivoli Access Manager (TAM) as the authorization policy decision point. A software utility to discover services from the IBM WebSphere Service Registry and Repository (WSRR) to enable the authorization solution will be provided to simplify and accelerate deployment of this authorization solution.

SOA authorization using Tivoli Federated Identity Manager and WebSphere Service Registry and Repository

This article describes a service-based approach to authorization in Service Oriented Architecture (SOA) environments using IBM Tivoli Federated Identity Manager (TFIM). This approach extends existing IBM solutions for identity propagation in SOA by leveraging Tivoli Access Manager (TAM) as the authorization policy decision point. A software utility to discover services from the IBM WebSphere Service Registry and Repository (WSRR) to enable the authorization solution will be provided to simplify and accelerate deployment of this authorization solution.

SOA authorization using Tivoli Federated Identity Manager and WebSphere Service Registry and Repository

This article describes a service-based approach to authorization in Service Oriented Architecture (SOA) environments using IBM Tivoli Federated Identity Manager (TFIM). This approach extends existing IBM solutions for identity propagation in SOA by leveraging Tivoli Access Manager (TAM) as the authorization policy decision point. A software utility to discover services from the IBM WebSphere Service Registry and Repository (WSRR) to enable the authorization solution will be provided to simplify and accelerate deployment of this authorization solution.

Montag, 7. Januar 2008

SOA: Managing identity contexts across service requests

Businesses embrace Service Oriented Architecture (SOA) to help their IT meet the needs of their business. The loose coupling of services and their distributed nature across organizations and trust boundaries presents a number of challenges. When it comes to the reuse of existing applications or service connectivity across organizational or technological boundaries, the identity systems can vary and so can the credential systems. Managing, mapping, and propagating identity across these environments is necessary. This article discusses the business challenges when managing identity contexts in Web services and SOA. It outlines the importance of creating solutions based on standards. The security token service (STS) capability in IBM Tivoli Federated Identity Manager (TFIM) is a key building block that can be used in solutions to address these identity propagation requirements. This article explains the capabilities of the STS and outlines architectural approaches using TFIM to solve these needs.

SOA: Managing identity contexts across service requests

Businesses embrace Service Oriented Architecture (SOA) to help their IT meet the needs of their business. The loose coupling of services and their distributed nature across organizations and trust boundaries presents a number of challenges. When it comes to the reuse of existing applications or service connectivity across organizational or technological boundaries, the identity systems can vary and so can the credential systems. Managing, mapping, and propagating identity across these environments is necessary. This article discusses the business challenges when managing identity contexts in Web services and SOA. It outlines the importance of creating solutions based on standards. The security token service (STS) capability in IBM Tivoli Federated Identity Manager (TFIM) is a key building block that can be used in solutions to address these identity propagation requirements. This article explains the capabilities of the STS and outlines architectural approaches using TFIM to solve these needs.

SOA: Managing identity contexts across service requests

Businesses embrace Service Oriented Architecture (SOA) to help their IT meet the needs of their business. The loose coupling of services and their distributed nature across organizations and trust boundaries presents a number of challenges. When it comes to the reuse of existing applications or service connectivity across organizational or technological boundaries, the identity systems can vary and so can the credential systems. Managing, mapping, and propagating identity across these environments is necessary. This article discusses the business challenges when managing identity contexts in Web services and SOA. It outlines the importance of creating solutions based on standards. The security token service (STS) capability in IBM Tivoli Federated Identity Manager (TFIM) is a key building block that can be used in solutions to address these identity propagation requirements. This article explains the capabilities of the STS and outlines architectural approaches using TFIM to solve these needs.

SOA: Managing identity contexts across service requests

Businesses embrace Service Oriented Architecture (SOA) to help their IT meet the needs of their business. The loose coupling of services and their distributed nature across organizations and trust boundaries presents a number of challenges. When it comes to the reuse of existing applications or service connectivity across organizational or technological boundaries, the identity systems can vary and so can the credential systems. Managing, mapping, and propagating identity across these environments is necessary. This article discusses the business challenges when managing identity contexts in Web services and SOA. It outlines the importance of creating solutions based on standards. The security token service (STS) capability in IBM Tivoli Federated Identity Manager (TFIM) is a key building block that can be used in solutions to address these identity propagation requirements. This article explains the capabilities of the STS and outlines architectural approaches using TFIM to solve these needs.