IBM 4.6.x User Manual

 

The

 

jms.MessageBrokerName

 

specifies

 

the

 

broker

 

name

 

to

 

use

 

for

 

the

 

JMS

 

provider.

 

You

 

must

 

set

 

this

 

connector

 

property

 

if

 

you

 

specify

 

JMS

 

as

 

the

 

delivery

 

transport

 

mechanism

 

(in

 

the

 

DeliveryTransport

 

property).

 

When

 

you

 

connect

 

to

 

a

 

remote

 

message

 

broker,

 

this

 

property

 

requires

 

the

 

following

 

values:
QueueMgrName:Channel:HostName:PortNumber

 

where:

 

 

is

 

the

 

name

 

of

 

the

 

queue

 

manager.

 

 

is

 

the

 

channel

 

used

 

by

 

the

 

client.

 

 

is

 

the

 

name

 

of

 

the

 

machine

 

where

 

the

 

queue

 

manager

 

is

 

to

 

reside.

 

is

 

the

 

port

 

number

 

used

 

by

 

the

 

queue

 

manager

 

for

 

listening

 

For

 

example:

 

jms.MessageBrokerName

 

=

 

WBIMB.Queue.Manager:CHANNEL1:RemoteMachine:1456

 

The

 

default

 

value

 

is

 

crossworlds.queue.manager

.

 

Use

 

the

 

default

 

when

 

connecting

 

to

 

a

 

local

 

message

 

broker.

 

 

The

 

jms.NumConcurrentRequests

 

property

 

specifies

 

the

 

maximum

 

number

 

of

 

concurrent

 

service

 

call

 

requests

 

that

 

can

 

be

 

sent

 

to

 

a

 

connector

 

at

 

the

 

same

 

time.

 

Once

 

that

 

maximum

 

is

 

reached,

 

new

 

service

 

calls

 

are

 

blocked

 

and

 

must

 

wait

 

for

 

another

 

request

 

to

 

complete

 

before

 

proceeding.

 

The

 

default

 

value

 

is

 

10

.

 

 

The

 

jms.Password

 

property

 

specifies

 

the

 

password

 

for

 

the

 

JMS

 

provider.

 

A

 

value

 

for

 

this

 

property

 

is

 

optional.

 

There

 

is

 

no

 

default

 

value.

 

 

The

 

jms.TransportOptimized

 

property

 

determines

 

if

 

the

 

WIP

 

(work

 

in

 

progress)

 

is

 

optimized.

 

You

 

must

 

have

 

a

 

WebSphere

 

MQ

 

provider

 

to

 

optimize

 

the

 

WIP.

 

For

 

optimized

 

WIP

 

to

 

operate,

 

the

 

messaging

 

provider

 

must

 

be

 

able

 

to:

 

1.

   

Read

 

a

 

message

 

without

 

taking

 

it

 

off

 

the

 

queue

 

2.

   

Delete

 

a

 

message

 

with

 

a

 

specific

 

ID

 

without

 

transferring

 

the

 

entire

 

message

 

to

 

the

 

receiver’s

 

memory

 

space

 

3.

   

Read

 

a

 

message

 

by

 

using

 

a

 

specific

 

ID

 

(needed

 

for

 

recovery

 

purposes)

 

4.

   

Track

 

the

 

point

 

at

 

which

 

events

 

that

 

have

 

not

 

been

 

read

 

appear.

The

 

JMS

 

APIs

 

cannot

 

be

 

used

 

for

 

optimized

 

WIP

 

because

 

they

 

do

 

not

 

meet

 

conditions

 

2

 

and

 

4

 

above,

 

but

 

the

 

MQ

 

Java

 

APIs

 

meet

 

all

 

four

 

conditions,

 

and

 

hence

 

are

 

required

 

for

 

optimized

 

WIP.

 

This

 

property

 

is

 

valid

 

only

 

if

 

the

 

value

 

of

 

DeliveryTransport

 

is

 

JMS

 

and

 

the

 

value

 

of

 

BrokerType

 

is

 

ICS

.

 

The

 

default

 

value

 

is

 

false

.

   

 

Adapter

 

for

 

Siebel

 

eBusiness

 

Applications

 

User

 

Guide