Verifying subcomponent configuration – IBM 51 User Manual

Page 30

Advertising
background image

v

Starts

the

WebSphere

Application

Server.

v

Configures

the

WebSphere

Application

Server,

including:

WebSphere

Application

Server

configuration

WebSphere

Application

Server

deployment

WebSphere

Application

Server

setup

on

UNIX,

to

run

as

user

configuration

v

Enables

security

for

the

WebSphere

Application

Server.

v

On

Windows,

it

creates

the

Windows

Service.

v

On

Windows,

it

creates

keys

in

Windows

registry.

v

Reinitializes

the

database.

v

The

Tivoli

Intelligent

Orchestrator

uninstaller

is

automatically

created

by

the

Install

Shield

MultiPlatform

(ISMP).

v

If

the

Install

Agent

Manager

check

box

is

selected,

the

agent

manager

installer

is

launched.

v

Verifying

subcomponent

configuration

The

following

procedures

are

required

to

confirm

that

Tivoli

Intelligent

Orchestrator

and

subcomponents

have

been

successfully

configured:

v

Verifying

Tivoli

Intelligent

Orchestrator’s

connection

to

DB2

Universal

Database.

See

“DB2

Universal

Databaseconfiguration

verification.”

v

Verifying

the

IBM

Tivoli

Directory

Server

configuration.

See

“IBM

Tivoli

Directory

Server

configuration

verification”

on

page

19.

v

Verifying

Tivoli

Intelligent

Orchestrator’s

connection

to

IBM

Tivoli

Directory

Server.

See

“IBM

Tivoli

Directory

Server

connection

verification”

on

page

20.

v

Verifying

the

WebSphere

Application

Server

configuration.

See

“WebSphere

Application

Server

configuration

verification”

on

page

21.

DB2

Universal

Databaseconfiguration

verification:

Tivoli

Intelligent

Orchestrator

uses

two

mechanisms

to

connect

to

the

database:

1.

Java

connection

using

the

information

in

the

dcm.xml

file,

located

at

%TIO_HOME%\config

on

Windows

($TIO_HOME/config

on

UNIX):

<config>

<database>

<type>db2</type>

<driver>COM.ibm.db2.jdbc.app.DB2Driver</driver>

<url>jdbc:db2:TC</url>

<name>TC</name>

<username>db2inst1</username>

<password>QJsdAjUEHi8=</password>

</database>

</config>

2.

Kula

user

through

the

WebSphere

Application

Server.

In

the

administrative

console,

go

to

Security

–>

JAAS

Configuration

–>

J2C

Authentication

Data

to

connect

to

the

database.

When

troubleshooting

the

DB2

Universal

Database

connection

with

Tivoli

Intelligent

Orchestrator,

follow

these

steps:

1.

Try

to

manually

connect

to

the

database,

and

run

the

following

command

to

list

all

DB2

Universal

Database

tables:

list

tables

18

Tivoli

Intelligent

Orchestrator

Problem

Determination

and

Troubleshooting

Guide

Advertising