High Availability Options for WebSphere MQ for IBM i

Size: px

Start display at page:

Download "High Availability Options for WebSphere MQ for IBM i"

Arabella Lawrence
6 years ago
Views:

1 IBM Software Group High Availability Options for WebSphere MQ for IBM i Karen Stanley (kstanly@us.ibm.com) Advisory Software Engineer 22 March 2012 WebSphere Support Technical Exchange

2 Acknowledgment IBM Software Group Jonathan Rumsey IBM i Lead Developer WebSphere MQ IBM Systems & Technology Group David Peraza WebSphere Support Technical Exchange 2 of 45

3 Agenda Save and Restore options QSaveQmgr: SupportPac MS03 New command implemented into the WebSphere MQ V7.1 product Replication options Duplicate AMQAJRN and Checkpoint (QMQMCHKPT) Backup Queue Manager Multi-Instance Queue Manager (WMQ V and higher) When Target Queue Manager will not start WebSphere MQ Clustering Advance System i Helpful Links Suggested Reading WebSphere Support Technical Exchange 3 of 45

4 Save and Restore Options WebSphere Support Technical Exchange 4 of 45

5 Save/Restore Option for WebSphere MQ Backup of one or more queue managers requires them to be quiesced. For WebSphere MQ on iseries V6.0 and higher use the following to quiesce all queue managers: End ALL applications and monitoring packages ENDMQM MQMNAME(*ALL) OPTION(*IMMED) ENDCCTJOB(*YES) RCDMQMIMG(*YES) TIMEOUT(15) ENDSBS QMQM WebSphere Support Technical Exchange 5 of 45

6 Save/Restore Option for WebSphere MQ Cont. CRTSAVF FILE(QGPL/QMxxxxx) TEXT( QMGR: QMGRname- QMGR LIBRARY') CRTSAVF FILE(QGPL/IFSxxxxx) TEXT('QMGR: QMGRname- IFS DIR') SAVLIB LIB([QMxxxxx]) DEV(*SAVF) SAVF(QGPL/QMxxxxx) TGTRLS(V5R4M0) SAV DEV('/qsys.lib/qgpl.lib/ifsxxxxx.file/') OBJ(('/qibm/userdata/mqm/qmgrs/[QMxxxxx]/*')) TGTRLS(V5R4M0) NOTE: Where xxxxx is the name of the Queue Manager NOTE: Use the RSTLIB and RST commands to restore queue manager environment onto Target system. NOTE: Must update the /qibm/userdata/mqm/mqs.ini file to include the restored queue manager. NOTE: Must be performed for each queue manager configured NOTE: Must associate journal receivers using the WRKJRN for journal AMQAJRN in queue manager library on the target server WebSphere Support Technical Exchange 6 of 45

7 QSaveQmgr: SupportPac MS03 WebSphere MQ Product Support Homepage Technote: MS03: WebSphere MQ - Save Queue Manager object definitions using PCFs (saveqmgr) Requires active queue manager (STRMQM) Requires active Command Server (STRMQMCSVR) Creates a script file of WebSphere MQ definitions NOTE: No message data is saved The script files generated by QSaveQmgr can be ftpped to the target system to rebuild a Queue Manager. New command built into the WebSphere MQ V7.1 product (DMPMQMCFG) For example, from the QSH (QSHELL) environment type /qsys.lib/qmqm.lib/dmpmqcfg.pgm -m QMGRNAME > /qsys.lib/libname.lib/qtxtsrc.file/qmgrname.mbr /qsys.lib/qmqm.lib/dmpmqcfg.pgm -m QMGRNAME -o grtmqmaut > /qsys.lib/libname.lib/qmqmaut.file/qmgrname.mbr WebSphere Support Technical Exchange 7 of 45

8 Replication Options WebSphere Support Technical Exchange 8 of 45

9 Duplicate AMQAJRN and Checkpoint (QMQMCHKPT) Source Target Qmgr: Common Library: QMCOMMON AMQAJRN Remote Journal Association Remote Journal Library: COMMONQM AMQAJRN Journal Scrape Program Qmgr: Common Library: QMCOMMON AMQAJRN AMQA AMQA AMQA Note: Periodically restore the QMQMCHKPT file, execute the journal scrape program and start the target queue manager. WebSphere Support Technical Exchange 9 of 45

10 Duplicate AMQAJRN and Checkpoint (QMQMCHKPT) Cont. Source Add RDB (relational database name) Entry ADDRDBDIRE RDB(MQAS03) RMTLOCNAME('hostname or ip address' *IP) Add Server Authority Entry ADDSVRAUTE(*CURRENT) Server(MQAS03) Usrid(User profile) Pwd(password) Create Source queue manager CRTMQM MQMNAME(COMMON) Go to the Target server (*next slide*) Create remote journal entry ADDRMTJRN RDB(MQAS03) SRCJRN(QMCOMMON/AMQAJRN) TGTJRN(COMMONQM/AMQAJRN) RMTRCVLIB(COMMONQM) MSGQ(COMMONQM/RMTJRNMSG) TEXT('Remote journal for QMGR: COMMON ) Activate remote journaling CHGRMTJRN RDB(MQAS03) SRCJRN(QMCOMMON/AMQAJRN) TGTJRN(COMMONQM/AMQAJRN) JRNSTATE(*ACTIVE) DELIVERY(*SYNC) Start queue manager and begin processing STRMQM MQMNAME(COMMON) NOTE: Periodically quiesce queue manager and save the QMQMCHKPT file from the queue manager directory /qibm/userdata/mqm/common/qmqmchkpt and ftp to the target server. Also perform a RCDMQMIMG OBJ(*ALL) OBJTYPE(*ALL) MQMNAME(COMMON) DSPJRNDTA(*YES) to force a checkpoint. WebSphere Support Technical Exchange 10 of 45

11 Duplicate AMQAJRN and Checkpoint (QMQMCHKPT) Cont. Target Create Remote database profile CRTUSRPRF USRPRF(RDBUSER) PASSWORD() USRCLS(*SECOFR) Create Remote journaling library CRTLIB LIB(COMMONQM) Create Remote journal message queue CRTMSGQ MSGQ(COMMONQM/RMTJRNMSG) Create Backup queue manager CRTMQM MQMNAME(COMMON) Go Back to the Source server (*previous slide*) NOTE: To move the journal entries from the Remote Journal to the Backup queue manager will require an application to read the entries from COMMONQM/AMQAJRN and write them to QMCOMMON/AMQAJRN. WebSphere Support Technical Exchange 11 of 45

12 NOTE: What is a Checkpoint? A checkpoint is a point in time when the record described in the journal is the same as the record in the queue. The checkpoint itself consists of the series of journal records needed to restart the queue manager. For example the state of all transactions (that is, units of work) active at the time of the checkpoint. Reference: WebSphere MQ for iseries System Administration Guide WebSphere MQ never expects the IFS files to contain more recent data than the journal. The copy of the checkpoint file must be older than the copies of the IFS object files. This rule guards against skipping log records that need to be replayed at start-up time. The checkpoint data determines how much log data is replayed on start-up and so how much message/transaction data is recovered. WebSphere Support Technical Exchange 12 of 45

13 NOTE: When is a Checkpoint Taken? A checkpoint will be taken after every 10,000 persistent get and/or put operations, or every 30 minutes, if at least 100 messages have been get and/or put, which ever occurs first. Additionally, a check point will also be taken during Queue Manager startup (STRMQM) Queue Manager shutdown (ENDMQM) Journal threshold size has been exceeded and a new journal receiver has been automatically created. When a full media image is taken RCDMQMIMG OBJ(*ALL) OBJTYPE(*ALL) MQMNAME(QMGRNAME) DSPJRNDTA(*YES) A checkpoint will be taken if CheckPointLogRecdMax journal entries have been written since the last checkpoint. For WMQ V5.2 and subsequent releases this defaults to 10,000 so we will take a checkpoint when 10,000 persistent GETs and/or PUTs occur. If we do not get CheckPointLogRecdMax journal entries within 30 minutes we will do a checkpoint if at least CheckPointLogRecdMin journal entries have been written. So, if we wait 30 minutes and we haven't done at least 100 persistent GETs and/or PUTs, then we don't bother doing a checkpoint. Note: It is possible to put non persistent messages to a queue with message persistence set to yes when the persistence option of no is specified on the MQPUT/MQPUT1. WebSphere Support Technical Exchange 13 of 45

14 Backup queue managers for WMQ V6.x This method involves mirroring only the journal data from the Source to the Target machine. The queue manager on the Target machine is designated as backup queue manager and is periodically started in a restricted state that allows replaying of journal data only. When a switch or failover occurs, the queue manager on the Target machine is activated. Setup is the same as the initial recommendation. However, on the startup for the Backup (Target) queue manager specify *YES for the REPLAY parameter, for example, STRMQM MQMNAME(COMMON) REPLAY(*YES) NOTE: This automatically updates the checkpoint file on the Target server so that the backup queue manager only needs to replay new journal entries each time. By periodically replaying the backup queue manager, this ensures that when a switch/failover is required only the latest journal entries need to be replayed allowing for a quick restart/recovery. To activate the backup queue manager specify *YES for the ACTIVATE parameter. Backup queue managers cannot be started with a regular STRMQM until they have been first activated. STRMQM MQMNAME(COMMON) ACTIVATE(*YES) Once the queue manager has been activated then a normal startup can be issued, STRMQM MQMNAME(COMMON) WebSphere Support Technical Exchange 14 of 45

15 STRMQM Start Message Queue Manager (STRMQM) Type choices, press Enter. Message Queue Manager name... *DFT Redefine system objects.... *NO *YES, *NO Fix directories *NO *YES, *NO Startup Status Detail..... *ALL *ALL, *MIN Service startup *YES *YES, *NO Perform replay only *NO *YES, *NO Activate backup *NO *YES, *NO Permit Standby Queue Manager.. *NO *YES, *NO WebSphere Support Technical Exchange 15 of 45

16 NOTE: STRMQM Startup Status Detail (STRSTSDTL) Specifies the detail of status messages that are issued whilst starting the queue manager. *ALL Display all startup status messages. This level of detail includes periodically displaying messages detailing transaction recovery and log replay. This level of detail can be useful in tracking queue manager startup progress following the abnormal termination of a queue manager. *MIN Displays a minimum level of status messages. Service startup (STRSVC) Specifies whether the additional following QMGR components are started when the Queue Manager is started: The Channel Initiator The Command Server Listeners with CONTROL set to QMGR or STARTONLY Services with CONTROL set to QMGR or STARTONLY Perform replay only (REPLAY) Whether the Queue Manager is being started to perform replay only. This enables a backup copy of a Queue Manager on a remote machine to replay logs created by the corresponding active machine, and to allow the backup Queue Manager to be activated in the event of a disaster on the active machine. Activate backup (ACTIVATE) Specifies whether to mark a Queue Manager as active. A Queue Manager that has been started with the REPLAY option is marked as a backup Queue Manager and cannot be started before it has been activated. WebSphere Support Technical Exchange 16 of 45

17 What s New WMQ V and higher : Multi-Instance Queue Manager Basic failover support without separate HA coordinator Can start two instances of a queue manager on different machines One is active instance; other is standby instance Active instance owns the queue manager s files Will accept connections from applications Standby instance does not own the queue manager s files Applications cannot connect to standby instance If the active instance fails, performs queue manager restart and becomes active Instances share the data, so it s the SAME queue manager WebSphere Support Technical Exchange 17 of 45

ADDMQMINF Add Queue Manager Info ADDMQMINF MQMNAME() PREFIX() MQMDIR() MQMLIB() Adds reference to a queue manager, essentially inserts appropriate

18 ADDMQMINF Add Queue Manager Info ADDMQMINF MQMNAME() PREFIX() MQMDIR() MQMLIB() Adds reference to a queue manager, essentially inserts appropriate stanzas into the mqs.ini Equivalent of CRTMQM for adding a standby instance of an existing queue manager WebSphere Support Technical Exchange 18 of 45

19 RMVMQMINF Remove Queue Manager Info RMVMQMINF MQMNAME() Removes reference to a queue manager Essentially removes the stanzas for a given queue manager from the mqs.ini file Equivalent of DLTMQM for a standby instance of a queue manager WebSphere Support Technical Exchange 19 of 45

WRKMQMJRN Work With Queue Manager Journals WRKMQMJRN QMNAME() Displays local queue manager library and journal information in top half of screen Displays a list of remote journaling artefacts in a

20 WRKMQMJRN Work With Queue Manager Journals WRKMQMJRN QMNAME() Displays local queue manager library and journal information in top half of screen Displays a list of remote journaling artefacts in a list in bottom half of screen Remote Journal direction indicators indicate direction of journal replication To remote system (->) From remote system (<-) WebSphere Support Technical Exchange 20 of 45

21 ADDMQMJRN Add A Queue Manager Journal ADDMQMJRN MQMNAME() RMTJRNRDB() Add a remote journal for a queue manager Only valid to be run on the source system (i.e. direction of replication ->) Must have configured the appropriate RDB entries for the destination Default options are the simplest way to get journaling up and running quickly!!! WebSphere Support Technical Exchange 21 of 45

22 CHGMQMJRN Change Journaling CHGMQMJRN MQMNAME() JRN() RMJRNRDB() Alters existing journaling artefacts, for example changing state from *ACTIVE to *INACTIVE, *ASYNC to *SYNC, etc Likely to be required after failover has successfully occurred to catch up with journal entries written whilst a system has been down Sync journaling automatically inactivated if target system cannot confirm writes within a configurable timeout WebSphere Support Technical Exchange 22 of 45

RMVMQMJRN Remove Journal RMVMQMJRN MQMNAME() JRN() RMTJRNRDB() Inactivates and removes remote journaling artefacts Removes journal and receivers at

23 RMVMQMJRN Remove Journal RMVMQMJRN MQMNAME() JRN() RMTJRNRDB() Inactivates and removes remote journaling artefacts Removes journal and receivers at remote location if successful Only valid to be run on the source system (i.e. direction of replication ->) WebSphere Support Technical Exchange 23 of 45

24 Example of Configuring a Multi-Instance Queue Manager Checklist: Verify that your userid and password match across all servers Verify that the QMQM userid is updated to have a password and that it matches across servers. Sample Environment: SERVER1 (i5/os V6.1/WMQ ) SERVER2 (i5/os V6.1/WMQ ) SERVER3 (i5/os V6.1/WMQ ) NOTE: i5/os remote journal enabled between SERVER1 and SERVER2. Also, SERVER3 does not need to have WebSphere MQ installed, however for this setup we did have WMQ V installed on the server. WebSphere Support Technical Exchange 24 of 45

25 Example of Configuring a Multi-Instance Queue Manager Source (SERVER1): 1. ADDRDBDIRE RDB(SERVER2) RMTLOCNAME(Hostname/ip address *IP) RMTAUTMTH(*USRIDPWD) ADDRDBDIRE RDB(SERVER3) RMTLOCNAME(Hostname/ip address *IP) RMTAUTMTH(*USRIDPWD) 2. CRTMQM MQMNAME(MIQMGR02) UDLMSGQ(SYSTEM.DEAD.LETTER.QUEUE) MQMDIRP('/QNTC/SERVER3/QIBM/UserData/mqm/qmgrs') 3. STRMQM MQMNAME(MIQMGR02) STANDBY(*YES) NOTE: View the mqs.ini file to obtain the following information Name=MIQMGR02 Prefix=/QIBM/UserData/mqm Library=QMMIQMGR02 Directory=MIQMGR02 DataPath=/qntc/SERVER3/QIBM/UserData/mqm/qmgrs/MIQMGR02 NOTE: Queue manager should be in ACTIVE status. Goto Target (SERVER2) 4. ADDMQMJRN MQMNAME(MIQMGR02) RMTJRNRDB(SERVER2) 5. WRKMQMJRN MQMNAME(MIQMGR02) NOTE: This command allows the enduser to verify that remote journaling has been enabled from SERVER1 to SERVER2. Goto Target (SERVER2) WebSphere Support Technical Exchange 25 of 45

26 Example of Configuring a Multi-Instance Queue Manager Target (SERVER2): 1. ADDRDBDIRE RDB(SERVER1) RMTLOCNAME(Hostname/ip address *IP) RMTAUTMTH(*USRIDPWD) ADDRDBDIRE RDB(SERVER3) RMTLOCNAME(Hostname/ip address *IP) RMTAUTMTH(*USRIDPWD) 2. ADDMQMINF MQMNAME(MIQMGR02) PREFIX('/QIBM/UserData/mqm') MQMDIR(MIQMGR02) MQMLIB(QMMIQMGR02) DATAPATH('/QNTC/SERVER3/QIBM/Userdata/mqm/qmgrs/MIQMGR02') NOTE: Queue manager instance should be in ELSEWHERE status. Goto Source (SERVER1) 3. ADDMQMJRN MQMNAME(MIQMGR02) RMTJRNRDB(SERVER1) 4. WRKMQMJRN MQMNAME(MIQMGR02) NOTE: This command allows the enduser to verify that remote journaling has been enabled from SERVER2 to SERVER1. 5. STRMQM MQMNAME(MIQMGR02) STANDBY(*YES) NOTE: Queue manager instance should in STANDBY status. WebSphere Support Technical Exchange 26 of 45

27 When the Target queue manager will not start Undocumented Cold Start program New Program AMQOCLS4 automates 12 step procedure Only runs in interactive job User is warned of message loss and must agree to conditions via a inquiry message Cold start is logged in QMQMMSG *MSGQ CALL AMQOCLS4 PARM(QMGRLIB QMGRNAME SIZE) QMGRLIB is the queue manager library name, QMxxxxx (where xxxxx is the first eight characters of the queue manager name and should be blank padded for 48 characters) QMGRNAME indicates the queue manager and should be blank padded (48 Characters) SIZE indicates the Threshold size of the journal receivers For WMQ V and higher only the queue manager name is required WARNING: WMQ V5.3 and later releases makes more use of memory buffers for persistent messages than previous versions If the journals are deleted, there is more chance of losing data after abnormal Qmgr shutdown NOTE: Program was added in CSD06 for WMQ for iseries and Updated in CSD08 for V5.3 to included the Size parameter. WebSphere Support Technical Exchange 27 of 45

28 Undocumented Cold Start program A new program is supplied to automate 12 step procedure - AMQOCLS4 This can be invoked as: CALL AMQOCLS4 PARM(QMGRLIB QMGRNAME SIZE) This program has checks to ensure that it is only run in interactive job (because people should not automate this procedure) Break messages are sent to the screen to warn the user of potential message loss and submission for backup of the queue manager prior to the cold start procedure. The user must reply to these messages, accepting responsibility for doing cold start This exchange of messages is logged in the QMGRLIB/QMQMMSG *MSGQ to record the fact that a cold start ran Queue manager will be started NOTE: If you wish to determine in more detail why a queue manager has failed startup then save the Queue Manager library (QMxxxxxx) and the Integrated File System for the queue manager (/qibm/userdata/mqm/qmgrs/<qmgrname>) WebSphere Support Technical Exchange 28 of 45

29 First Inquiry message from AMQOCLS4 Display Messages System: MQAS03 Queue..... : QPADEV000G Program.... : *DSPMSG Library... : QSYS Library... : Severity... : 00 Delivery... : *NOTIFY Type reply (if required), press Enter. From... : XXXXXXXX 09/11/06 10:53:39 WARNING: The AMQOCLS4 program should only be used under instruction from IBM Support. It can lead to loss of data in some circumstances. IBM will not accept responsibility for data lost due to incorrect use of this program. Do you want to proceed? Type 'yes' to accept these conditions and restart queue manager MQAS01. Reply... WebSphere Support Technical Exchange 29 of 45

30 Second Inquiry message from AMQOCLS4 Display Messages System: MQAS03 Queue..... : QPADEV000G Program.... : *DSPMSG Library... : QSYS Library... : Severity... : 00 Delivery... : *NOTIFY Type reply (if required), press Enter. From... : XXXXXXXX 09/11/06 10:56:05 Do you want to backup the queue manager library prior to running the cold start. This will create a save file in QGPL of the same name as the queue manager library, or clear and reuse it if it already exists. Type 'yes' to backup the Queue manager library. Reply... WebSphere Support Technical Exchange 30 of 45

31 Completion message from AMQOCLS4 Display Messages System: MQAS03 Queue..... : QPADEV000G Program.... : *DSPMSG Library... : QSYS Library... : Severity... : 00 Delivery... : *NOTIFY Type reply (if required), press Enter. From... : XXXXXXX 09/11/06 11:00:00 Cold Start complete. You will need to reapply any changes you had previously made to journal objects in the queue manager library. WebSphere Support Technical Exchange 31 of 45

32 WebSphere MQ Clustering WebSphere Support Technical Exchange 32 of 45

33 WebSphere MQ Queue Manager Clusters Queue manager Reduced system administration Server Application Cluster queue Queue manager Queue manager Client Application Transmission queue Workload balancing Cluster queue Server Application Queue manager Server Application Increased availability Cluster queue WebSphere Support Technical Exchange 33 of 45

34 Goals of WMQ Cluster Support Application sees a single queue Actually implements as multiple queues Reference: WebSphere MQ Queue Manager Clusters /v6r0/topic/com.ibm.mq.csqzah.doc/qc10120_. htm WebSphere Support Technical Exchange 34 of 45

35 WebSphere MQ Cluster: Components Full repositories queue manager: This is a queue manager that knows about every object in the cluster Partial repositories queue managers This is a queue manager that by default does not know about every object in the cluster. Clustered object A queue or channel that is defined to be in the cluster Auto defined Clustered object A remote queue or channel that is defined by WebSphere MQ SYSTEM.CLUSTER.TRANSMIT.QUEUE This is the queue used by the queue manager to send messages through the cluster Workload management This is the component that defines where messages are sent in the cluster WebSphere Support Technical Exchange 35 of 45

36 Advanced System i Options Author : David Peraza (dperaza@us.ibm.com) WebSphere Support Technical Exchange 36 of 45

37 i5/os Clustering WMQ Cluster is a partial HA solution Messages waiting to be processed (in flight) by Application become temporarily unavailable (marooned) when Queue Manager (or its host system) fails Messages become available again once the failing Queue Manager is brought back online Depending on the importance of the messages, time required to recover the Queue Manager (or its host system) may be unacceptable i5/os Clustering can prevent marooned messages caused by system failures i5/os Cluster with switchable Independent ASP (IASP) i5/os Cluster with mirrored IASP Combination of WMQ cluster and i5/os cluster. WebSphere Support Technical Exchange 37 of 45

38 i5/os Cluster with Switchable IASP The IASP is made switchable via the High Speed Link (HSL) loop The IASP is initially available to the Primary node MGR.A is stored in the IASP and initially active on the Primary node In the event of a Switchover or Failover the IASP is automatically switched to the Backup Node and MGR.A made available Messages that were not processed due to the failure of the Primary node are processed on the Backup node There is a limit on the distance of the HSL loop (15 meters for Copper and 250 Meters for Optical) Primary Node System i MGR.A HSL connector TCP/IP Connection HSL connector IASP MGR.A Lib MGR.A IFS Backup Node System i MGR.A HSL connector WebSphere Support Technical Exchange 38 of 45

39 i5/os Cluster with Mirrored IASP Each node owns an IASP The IASP attached to the Primary node is mirrored (i5/os Geographical Mirroring) to the Backup node via the i5/os cluster Since MGR.A is stored in IASP and mirrored to IASP, if the Primary node fails IASP can automatically be made available on the Backup node and MGR.A activated there Similar to Switchable IASP, Mirrored IASP provides protection from marooned messages Unlike Switchable IASP, Mirrored IASP has no distance limit. Data can be mirrored over the Internet. Performance degrades with slow internet connections and distance. Primary Node System i MGR.A HSL connector IASP MGR.A Lib MGR.A IFS TCP/IP Connection Geo Mirroring Backup Node System i MGR.A HSL connector IASP MGR.A Lib MGR.A IFS WebSphere Support Technical Exchange 39 of 45

40 I5/OS Cluster and WMQ Cluster Initially Node A is the Primary Node for MGR.A and Node B is the Primary Node for MGR.B. Node B is a backup of A while Node A is a backup of B. This configuration makes use of the WMQ workload balance capabilities while utilizing i5/os clustering to ensure constant availability of messages. No node stays idle, all processors are being used. Calculations are necessary so that each node can handle the complete load in the event of a system failure. HSL connector IASP_A MGR.A Lib MGR.A IFS Node A System i MGR.A MGR.B IASP_B MGR.B Lib MGR.B IFS WMQ Cluster Channel TCP/IP Connection Geo Mirroring Geo Mirroring Node B IASP_B MGR.B Lib MGR.B IFS System i MGR.B MGR.A HSL connector IASP_A MGR.A Lib MGR.A IFS WebSphere Support Technical Exchange 40 of 45

41 Helpful Links WebSphere MQ Family Support : IBM Technote : Cold Start Procedure for WebSphere MQ for iseries MQ for iseries Softcopy Library : Redbook : AS/400 Remote Journal Function for High Availability and Data Replication (SG ) WebSphere Support Technical Exchange 41 of 45

42 Suggested Reading MQSeries Primer : WebSphere MQ for iseries Best Practice Guide : ibm.com/developerworks/websphere/library/techarticles/0605_rumse y/0605_rumsey.html Automating Journal Management in WebSphere MQ for iseries ibm.com/developerworks/websphere/library/techarticles/0308_phillip s/phillips.html WebSphere message queuing features for high availability on i5/os NOTE: Article by David Peraza WebSphere Support Technical Exchange 42 of 45

43 Additional WebSphere Product Resources Learn about upcoming WebSphere Support Technical Exchange webcasts, and access previously recorded presentations at: Discover the latest trends in WebSphere Technology and implementation, participate in technically-focused briefings, webcasts and podcasts at: Join the Global WebSphere Community: Access key product show-me demos and tutorials by visiting IBM Education Assistant: View a webcast replay with step-by-step instructions for using the Service Request (SR) tool for submitting problems electronically: Sign up to receive weekly technical My Notifications s: WebSphere Support Technical Exchange 43 of 45

44 Connect with us! 1. Get notified on upcoming webcasts Send an to with subject line wste subscribe to get a list of mailing lists and to subscribe 2. Tell us what you want to learn Send us suggestions for future topics or improvements about our webcasts to wsehelp@us.ibm.com 3. Be connected! Connect with us on Facebook Connect with us on Twitter WebSphere Support Technical Exchange 44 of 45

45 Questions and Answers WebSphere Support Technical Exchange 45 of 45

Advanced Integration Services In IBM Business Process Manager

IBM Software Group Advanced Integration Services In IBM Business Process Manager Pratima Ahuja (pratima@us.ibm.com) Software Engineer 09/11/2012 WebSphere Support Technical Exchange Agenda What is an AIS