Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Does ALE work on RAM running on WAS Express?

Can an ALE synch connection be setup to synchronize WSRR 8.x and RAM 7.5.1 if RAM is running on the bundled WAS Express edition (as opposed to a full WAS 7.x version). or does RAM ALE WSRR sychroniization require a full WAS instance?

A folow up question is, if ALE can be set up using RAM on WAS Express, can the connecion be made secure simply by the exchange of certs into eachothers trust stores, or is Single Sign On using LTPA keys required for a secure connnection?  (LTPA Single Sign On would seem to be incompatible with RAM on WAS Express because WAS Express is not cell-aware?)

In summary, the most essential question here is: can RAM on WAS Express synchronize with WSRR via secure connection?

0 votes


Accepted answer

Permanent link
WSRR and RAM do not have to run on the same WAS instance ... so you can use RAM on express and WSRR on another WAS instance.  They communicate using their configured urls with http ... if it is https, it will be secure.

ALE is a WebSphere bundle of RAM and WSRR ... They do not have ALE v8.... but WSRR v8 should be compatible with RAM 7.5.1 as they note in their pubs.
Gordon Flood selected this answer as the correct answer

1 vote

Comments

Excellent, thank you!

We were wondering if our ALE synch problems were being cause by running RAM on WAS Express (and WSRR on WAS ND), but will now look elsewhere for the source of the problem.

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 7,506
× 6,130
× 1
× 1

Question asked: Jan 02 '13, 2:49 p.m.

Question was seen: 4,045 times

Last updated: Jan 03 '13, 1:50 p.m.

Confirmation Cancel Confirm