WebSphere MQ for AIX. Quick Beginnings GC

(1)

WebSphere

MQ

for

AIX

Quick

Beginnings

Version

5.3

GC34-6076-02

(2)

(3)

WebSphere

MQ

for

AIX

Quick

Beginnings

Version

5.3

GC34-6076-02

(4)

Note!

Beforeusingthisinformationandtheproductitsupports,besuretoreadthegeneralinformationunder“Notices”onpage 53.

Thirdedition(May2004)

ThiseditionappliestoWebSphereMQforAIX,V5.3,andtoallsubsequentreleasesandmodificationsuntil otherwiseindicatedinneweditions.

(5)

Tables

.

. v

Welcome

to

WebSphere

MQ

for

AIX

.

. vii

Roadmap. . . vii

Conventions . . . vii

What’s

new

in

WebSphere

MQ

for

AIX,

Version

5 Release

3 .

.

. ix

Chapter

1. Planning

to

install

WebSphere

MQ

for

AIX

.

. 1

Hardwarerequirements. . . 1

Diskstorage . . . 1

Prerequisitesoftware . . . 2

Operatingsystem. . . 2

Connectivity . . . 2

SSL(SecureSocketsLayer). . . 2

Optionalsoftware. . . 2 Compilers . . . 2 Transactionmonitors . . . 3 Databases . . . 3 DCE . . . 3 Java . . . 3 Delivery. . . 4 WebSphereMQcomponents . . . 4 Server . . . 4 Client. . . 5 Documentation . . . 5 Filesets . . . 6 readmefile. . . 7

Chapter

2. Preparing

to

install

WebSphere

MQ

for

AIX

.

. 9

Preparingforinstallation . . . 9

CreatingWebSphereMQfilesystems . . . 9

SettinguptheuserIDandgroup . . . 10

Migratingfromanearlierversion . . . 11

Changestotheinstallationpath . . . 11

POSIXstandardthreadinglibrary . . . 12

Creatingthesystemdefaultobjects . . . 12

Clientapplications . . . 12

EXTSHM-ExtendedSharedMemorymodel . . . 13

Nationallanguageconsiderations . . . 13

Displayingmessagesinyournationallanguage 13 Nationallanguagesupportformanuals . . . . 14

Chapter

3. Installing

the

WebSphere

MQ

for

AIX

server

.

. 15

Installationprocedure. . . 15

Easyinstallation. . . 15

Custominstallation. . . 16

Nationallanguageinstallation . . . 17

Remoteinstallation. . . 18

ReinstallingWebSphereMQforAIX . . . 18

Migratingauthorizationdata . . . 19

SettingthequeuemanagerCCSID. . . 20

Userexits . . . 21

Chapter

4. Verifying

the

server

installation

.

. 23

Verifyingalocalinstallation. . . 23

Settinguptheinstallation . . . 23

Testingtheinstallation. . . 24

Verifyingaserver-to-serverinstallation . . . 24

Settingupthesenderworkstation. . . 25

Settingupthereceiverworkstation . . . 26

Testingcommunicationbetweentheworkstations 26 VerifyingtheinstallationusingtheJMSPostcard application . . . 28

SettingupyoursystemtoruntheJMSPostcard 28 UsingtheJMSPostcardapplicationtoverifya localinstallation. . . 29

UsingthePostcardapplicationtoverifya server-to-serverinstallation . . . 31

Chapter

5. Installing

the

WebSphere

MQ

for

AIX

client

.

. 33

Installationprocedure. . . 33

Easyinstallation. . . 34

Custominstallation. . . 34

Nationallanguageinstallation . . . 35

MigratingtoandfromtheWebSphereMQSSL support. . . 35

Installingtheclientonthesamemachineasaserver 36

Chapter

6. Verifying

the

client

installation

.

. 37

Verifyingtheinstallation . . . 37

Settinguptheserverworkstation . . . 37

Settinguptheclientworkstation . . . 38

Testingcommunicationbetweentheworkstations 39

Chapter

7. WebSphere

MQ

documentation

.

. 41

Hardcopybooks. . . 41

Onlineinformation. . . 42

Publicationssuppliedwiththeproduct . . . . 42

HTMLandPDFbooksontheWorldWideWeb 43 Onlinehelp . . . 43

SupportPacs . . . 43

WebSphereMQnewsgroups. . . 43

Whitepapersandmigrationdocuments . . . . 43

Servicesupportsummary(PTFreadmes) . . . 43

(6)

Chapter

8. Applying

maintenance

to

WebSphere

MQ

for

AIX

.

. 45

InstallingaPTF . . . 45

Restoringthepreviousservicelevel . . . 46

Chapter

9. Uninstalling

WebSphere

MQ

for

AIX

.

. 47

Uninstallationprocedure . . . 47

RemovingtheWebSphereMQInternetGateway . . 47

Chapter

10. Code

sets

supported

by

WebSphere

MQ

for

AIX

.

. 49

Migratingtoeurosupport . . . 50

Notices

.

. 53

Trademarks . . . 54

Index

.

. 57

(7)

Tables

1. Gettingstartedroadmap. . . vii

2. Filesetsandcomponents . . . 6

3. ExamplesofsettingtheCCSID . . . 20

4. WebSphereMQfamilybooks . . . 41

5. LocalesandCCSIDsforAIX. . . 49

(8)

(9)

Welcome

to

WebSphere

MQ

for

AIX

ThisbookdescribesWebSphereMQforAIXVersion5.3and explainshowtoplan fortheproduct,install it,andverifythattheinstallationhasworked.

See the:

v _WebSphere_MQ_Bibliography_and_Glossary _for_an_explanation_of_terms_used_in_this book

v _WebSphere_MQ_System_{Administration}_Guide_for_further_information_on_using_the controlcommandscrtmqm,strmqm,andendmqm

Road

map

Use Table1 tofindtheinformationthatyouneedtoget startedwithWebSphere MQforAIX.

Table1.Gettingstartedroadmap

Ifyouwantto... Referto...

Learnaboutsystemrequirementsfor WebSphereMQforAIX

Chapter1,“PlanningtoinstallWebSphere MQforAIX,”onpage1andChapter2, “PreparingtoinstallWebSphereMQfor AIX,”onpage9

InstallWebSphereMQforAIX Chapter3,“InstallingtheWebSphereMQfor AIXserver,”onpage15andChapter4, “Verifyingtheserverinstallation,”onpage 23

InstalltheWebSphereMQforAIXclient Chapter5,“InstallingtheWebSphereMQfor AIXclient,”onpage33andChapter6, “Verifyingtheclientinstallation,”onpage37 ReadmoreaboutWebSphere®

MQ Chapter7,“WebSphereMQdocumentation,” onpage41

ApplymaintenancetoWebSphereMQfor AIX

Chapter8,“Applyingmaintenanceto WebSphereMQforAIX,”onpage45 UninstallaWebSphereMQforAIXserveror

client

Chapter9,“UninstallingWebSphereMQfor AIX,”onpage47

Conventions

Knowingtheconventionsusedinthisbookwillhelpyoutouseitmoreefficiently. v _Boldface_type_indicates_the_name_of_an_item_that_you_need_to_select_or_the_name

ofacommand.

v _Italics_type_indicates_new _terms,_book_titles,_or_variable_information_that_must_be replacedbyanactualvalue.

v _Monospace_type_indicates _an_example_(such_as_a _fictitious_path_or_file_name)_or textthatisdisplayedonthescreen.

(10)

(11)

What’s

new

in

WebSphere

MQ

for

AIX,

Version

5 Release

3

WebSphereMQforAIX, Version5Release3providesthefollowingnewand changed functions:

v _WebSphere_MQ_for_AIX_now _supports_WebSphere_MQ_channels_protected_using theindustrystandardSecureSockets Layer(SSL).SeeWebSphere MQSecurityfor details.ThissupportisbasedonIBM® _Global_Security_Kit;_a_copy_of_this

productisincludedwith WebSphereMQ.

v _Support_for_Java™_is_integrated_within_the_product._This_replaces_the_support previouslyprovided byMQSeries®_SupportPac™_MA88.

v _Product_{documentation}_is_now _supplied_on_separate_CD-ROMs.

v _Support_for_Web_{Administration}_and_the_Internet _Gateway_has_been _removed._If youhavethesefeaturesinstalledfromapreviousrelease oftheproduct, you willlosethemwhenyouupgrade.

v _A_new _form_of_license_management_is_implemented_for_this _release_of_the product.

v _WebSphere_MQ_for_AIX_now _supports_the_AIX_Extended_Shared_memory_model EXTSHM.

v _It_is_now _mandatory_to_export_the_entry_point _{’MQStart’}_in_any_exits _that WebSphereMQforAIXuses.

v _WebSphere_MQ_now_supports_generic_authority_{administration.}

(12)

(13)

Chapter

1. Planning

to

install

WebSphere

MQ

for

AIX

ThischapterdescribestheprerequisitesforrunningWebSphereMQforAIX,V5.3, including:

v _“Hardware_{requirements”}

v _{“Prerequisite}_software”_on_page₂ v _“Optional_software”_on_page₂

Thesoftware thatissupplied withtheWebSphereMQforAIXproductpackageis described in:

v _{“Delivery”}_on_page₄

v _“WebSphere_MQ_{components”}_on_page₄

Thelatest informationabouttheproductcanbe foundintheREADMEfile(see “readme file”onpage7).

Hardware

requirements

WebSphereMQforAIX, V5.3runsonanymachinethatsupportstheAIXV4.3.3 PowerPC®32–bit,orAIX®V5.1Power32bitonlyoperatingsystem,whetherfrom IBM orothervendors.For example:

v _IBM_RS/6000®_POWERserver® v _IBM_RS/6000_POWERstation

v _IBM_Scalable_{POWERparallel}®_systems v _Bull_DPX/20_(RISC)

v _Bull_ESCALA_(SMP)

Disk

storage

Thestorage requirementsforWebSphereMQforAIX, V5.3depend onwhich componentsyouinstall(see“WebSphereMQcomponents” onpage4), andhow muchworkingspaceyouneed.This, inturn,dependsonthenumber ofqueues thatyouuse,thenumberandsize ofthemessagesonthequeues,andwhetherthe messages arepersistent.Youalsorequire archivingcapacityondisk,tape,orother media.

Typicalstorage requirementsare asfollows: v _Server_{installation:}₅₀_MB

v _Client_{installation:}₁₅_MB v _Data_storage_(server):₅₀_MB v _Data_storage_(client):₅ _MB

Use thedfcommandtodeterminetheamount offreespaceonyour system. Diskstorageisalsorequiredfor:

v _Prerequisite_software v _Optional_software

v _Your_application _programs

See “Preparingforinstallation”onpage9 forinformationaboutcreating thefile systemsyouneedtoinstalland runWebSphereMQforAIX.

(14)

Prerequisite

software

Thissectiongivestheminimumsupportedsoftware levels.Laterlevels,if any,are supportedunlessotherwisestated.Theseprerequisites applytobothclientand serverinstallations ofWebSphereMQ.

Note: WebSphereMQdoesnotsupporthostnamesthatcontainspaces.Ifyou installWebSphereMQonacomputerwith ahostnamethatcontainsspaces, youwillbeunabletocreateanyqueuemanagers.

Operating

system

The operatingsystemssupportedbyWebSphereMQforAIX, V5.3are:

v _AIX_V4.3.3, _with_PTF_U472177,_running_in_a₃₂_bit_environment,_on₃₂_or₆₄_bit hardware.

v _AIX_V5.1, _with_PTFs_U476879,_U477366,_U477367_and_U477368, _and_APAR_fix IY29345running32bitkernelrunningon32or64bithardware.

v _AIX_V5.1, _with_PTF_U476879, _U477366,_U477367_and_U477368,_and_APAR_fix IY29345running64bitkernelrunningon64bithardware.

The CandC++runtimemust beat level5.0.2.0orhigher.

Use theoslevel commandtodeterminetheleveloftheoperatingsystemyouare running.

Connectivity

The networkprotocols supportedbyWebSphereMQforAIX,V5.3are: v _TCP/IP

v _SNA_LU_6.2

TCP/IPispartofthebaseoperatingsystem.For SNAconnectivityyouneedIBM eNetwork™_{Communications}_Server_for_AIX_V6.0.

IfyouwanttousetheSNALU6.2support onWebSphereMQforLinuxforIntel, youneedtheIBMCommunicationsServer forLinux5799-RQAVersion6.0.The CommunicationsServer isavailable asaPRPQproductfromIBM. Formore details, see:

http://www.ibm.com/software/network/commserver/about/cslinux.html

SSL

(Secure

Sockets

Layer)

IfyouwanttousetheSSLsupport,youneedIBMGlobalSecurityKitV6.Thisis supplied withWebSphereMQ.

Optional

software

The followingproductscanbeusedwith WebSphereMQforAIX,V5.3,butare not required. Unlessotherwisestated,theseproductsapplyonlytoserverinstallations of WebSphereMQ.

Compilers

The followingcompilers aresupportedfor WebSphereMQforAIX, V5.3 applications:

v _IBM_VisualAge®_C++_Professional_for_AIX_Version_5.0 v _Micro_Focus_Server _express_V2.0.10

v _IBM_Developer_Kit_for_AIX,_Java_Technology _Edition,_Version_1.3.1

(15)

Transaction

monitors

Thefollowingtransactionprocessingmonitors(coordination throughX/OpenXA interface) aresupported:

v _BEA_TUXEDO_V6.4_and _V6.5 v _WebSphere_Application_Server _V4.0 v _TXSeries™_for_AIX_V4.3

WebSphereMQforAIX, V5.3supportsWebSphereApplicationServerasanXA coordinator.For moreinformationabouttheWebSphereMQapplicationadaptor, and howtowriteComponentBrokerapplications,seetheWebSphereApplication Server EnterpriseEditionComponentBrokerWebSphereMQApplicationAdaptor DevelopmentGuide, SC09–4444.

Databases

Thefollowingdatabasesaresupported: v _DB2®_Universal _Database_V7.1_or_V7.2 v _Oracle_8iR3_(8.1.7)_and_Oracle _9i v _Sybase_V12_or_V12.5:

– AdaptiveServer Enterprise(A.S.E.),V11.5 – OpenClient(ctliband dblib),V11.1 – Embedded SQL/C,V11.0

– XAServer,V11.1

– AdaptiveServer Enterprise(A.S.E.),V12with - TheDTMoption

- Thelatestpatchesinstalled(testedwith EBF9091)

- EnvironmentvariablesSYBASEandSYBASE_OCS settoappropriatevalues intheshellfromwhichyoustarta queuemanager orapplicationprogram For informationonhowtosetupXAcoordination,seetheWebSphereMQSystem AdministrationGuide.

DCE

ThefollowingDCE productsaresupportedforclient andserverinstallationsof WebSphereMQ.IfyouwanttoruntheDCEsend,receive, ormessageexits supplied byWebSphereMQ,youmust usea DCEproductthatsupportsDESdata encryption.

v _IBM_DCE_V3.1 v _IBM_DCE_V3.2

DCE namesandsecuritymodulesareprovidedwith WebSphereMQforAIX,V5.3.

Note: Ifyouinstall theWebSphereMQDCEextensions, youwillnotbeableto useSSLchannels.

Java

Ifyouwantto usetheJavaMessagingSupport,youneed theJava Runtime Environment Version1.3orlater.

Software

requirements

(16)

Delivery

WebSphereMQforAIX, V5.3issuppliedona numberofCD-ROMs,asfollows: v _WebSphere_MQ_for_AIX_Server

v _WebSphere_MQ_Clients ₍₂_CDs) v _WebSphere_MQ_{Documentation}

WebSphereMQforAIXcanbeinstalledasaserverora client.SeetheWebSphere MQSystemAdministrationGuideforanexplanationofclientand serverinstallations of WebSphereMQ.

The ClientsCD-ROMscontaintheWebSphereMQclientsforAIX, HP-UX,Linux, Solaris, andWindows.RefertotherelevantQuickBeginningsbookforinformation onhow toinstalltheclientonotherplatforms.

The documentationCD-ROMscontaintheproductdocumentationinHTMLand PDFformats.

WebSphere

MQ

components

WhenyouinstallWebSphereMQforAIX,V5.3, youcanchoosewhichcomponents toinstall.

Server

The componentsavailableontheServerCD-ROMareasfollows:

Runtime

Mandatory component.Providessupport forexternalapplications.

BaseKit

Needed forapplicationdevelopment.

Server Provides messagingandqueuingservices toapplications,andsupport for WebSphereMQclientconnections.

Client forAIX

Provides remoteaccesstoWebSphereMQ.Mustbe connectedtoaserver. Toinstall aclientonthesamemachineasa server,usetheServer

CD-ROM;otherwiseusetheClientsCD-ROM.

Sampleprograms

Sampleapplication programs.Neededifyouwanttocheck your

WebSphereMQinstallationusingtheverification proceduresdescribedin this book.

DCE support

Provides supportforDCEnamesand securityontheserver.Install this componentonlyifyouare usingDCE.

DCE samples

Sampleprogramsfor DCEsupport.

Java messaging

Thefiles neededformessagingusingJava (includesJava Messaging Service).

Messagecatalogs

Messagecatalogsareavailable forthefollowingnational languages.The messagecatalog forthelocaleselectedonyour machineisinstalledby default.

(17)

v _Brazilian _Portuguese v _French v _German v _Italian v _Japanese v _Korean v _Spanish v _Simplified_Chinese v _Traditional_Chinese v _U.S._English Manpages

UNIX® _man_pages,_in_U.S._English,_for_the_following:

v _Control_commands

v _Message_Queue _Interface_(MQI)_commands v _MQSC _commands

WebSphereMQ supportfortheGlobal SecurityKit(GSKit)andtheKey Managementtool(iKeyman)

Needed forSSL.

IBMGlobal SecurityKitV6

Needed forSSL.

Client

Thefollowingcomponentsof WebSphereMQforAIXareavailable ontheClients CD-ROM.For adescriptionofeachcomponent,see“Server”onpage4.

Runtime BaseKit ClientforAIX Sampleprograms DCEsamples Messagecatalogs

Documentation

HTMLandPDFversionsof theWebSphereMQforAIXbooksare availableonthe DocumentationCD-ROM package,ontwoCD-ROMs,insomeorallof the

followingnationallanguages: v _Brazilian_Portuguese v _French v _German v _Italian v _Japanese v _Korean v _Spanish v _Simplified_Chinese v _Traditional_Chinese v _U.S._English

See “Onlineinformation” onpage42fordetailsofthedocumentationCD-ROM package.

Note: HTMLand PDFversionsoftheWebSphereMQbooks canbe viewed directlyfromtheCD-ROMs.

WebSphere

MQ

components

(18)

Filesets

The filesetsthatcorrespondtoeachofthecomponentsarelistedinTable2. Table2.Filesetsandcomponents

Fileset Component

mqm.base.runtime Runtime

mqm.base.samples Sampleprograms mqm.base.sdk BaseKit

mqm.Client.Bnd ClientBundle(forEasyInstallation) mqm.client.rte ClientforAIX

mqm.dce.samples DCEsamples mqm.dce.server DCEsupport

mqm.java.rte JavaandJMSsupport

mqm.keyman.rte _Support_for_SSL_key_management mqm.man.en_US.data _Man_pages_(U.S._English)

mqm.msg.de_DE _Message_catalog_(German) mqm.msg.De_DE _Message_catalog_(German) mqm.msg.en_US _Message_catalog_(U.S._English) mqm.msg.es_ES Messagecatalog(Spanish) mqm.msg.Es_ES Messagecatalog(Spanish) mqm.msg.fr_FR Messagecatalog(French) mqm.msg.Fr_FR Messagecatalog(French) mqm.msg.it_IT Messagecatalog(Italian) mqm.msg.It_IT Messagecatalog(Italian) mqm.msg.ja_JP Messagecatalog(Japanese) mqm.msg.Ja_JP Messagecatalog(Japanese) mqm.msg.ko_KR Messagecatalog(Korean)

mqm.msg.pt_BR Messagecatalog(BrazilianPortuguese) mqm.msg.zh_CN Messagecatalog(SimplifiedChinese) mqm.msg.Zh_CN Messagecatalog(SimplifiedChinese) mqm.msg.zh_TW Messagecatalog(TraditionalChinese) mqm.msg.Zh_TW Messagecatalog(TraditionalChinese) mqm.server.rte _Server

mqm.Server.Bnd _Server_Bundle_(for_Easy_{Installation)} gskak.rte _IBM_Global_Security_Kit_V6

Note: Forsomelanguages,twomessagecatalogsare availableindifferentcode sets(forexamplemqm.msg.de_DEiscodesetISO8859-1and mqm.msg.De_DEis codesetIBM-850).Formore information,seeChapter10,“Codesets supportedbyWebSphereMQforAIX,”onpage49.

(19)

readme

file

Before startingtoinstallWebSphereMQforAIX,review thereadmefileforthe latest informationontheproduct.Thereadmefilesforall supportednational languages arefoundintheREADMESdirectoryoneachCD-ROM.

readme

file

(20)

(21)

Chapter

2. Preparing

to

install

WebSphere

MQ

for

AIX

Thischapterdescribeswhattodotoprepareyour systemforinstallingWebSphere MQforAIX(see“Preparingforinstallation”).

Ifyouaremigratingfromanearlierversionof MQSeries,read“Migratingfroman earlier version”onpage11.

“National languageconsiderations”onpage13describes howtoselectthenational languageforyour WebSphereMQinstallation.

Preparing

for

installation

Before youinstall WebSphereMQforAIX,youneedto:

1. CreatethefilesystemsusedtoholdWebSphereMQanditsdata. 2. SetuptheuserIDandgroupforWebSphereMQ.

Creating

WebSphere

MQ

file

systems

Theinstallation directoryfortheWebSphereMQproductcodeis/usr/mqm. Working dataisstored in/var/mqm.Youcannotchangethese.

Creating

a

file

system

for

the

product

code

Install WebSphereMQforAIXin/usr/mqm.Thespacerequireddependsonhow manycomponentsyouinstall.Typicallyyouneed50 MBforaserverinstallation, or15 MBfora clientinstallationwithoutSSL.

Ifyoucannotinstalltheproductcodeinthis filesystem(forexample,ifitistoo smalltocontaintheproduct),youcando oneofthefollowing:

1. Createa newfilesystemandmountit as/usr/mqm.

2. Createa newdirectoryanywhereonyourmachine,andcreatea symboliclink from/usr/mqmtothisnew directory.Forexample:

mkdir /bigdisk/mqm

ln -s /bigdisk/mqm /usr/mqm

3. Allowtheinstallprogramtoexpandthefilesystem.

Whichever oftheseoptionsyouchoose,youmust doitbefore installingthe productcode.Thefilesystemintowhichthecodeisinstalledcanbea remote networkdevice,forexample,NFS.However,youmustdefinethemountoptions definedonthatdevicetoallowsetuidprograms,includingrootaccess, torun.

Creating

a

file

system

for

the

working

data

Before youinstall WebSphereMQforAIX,createandmounta journalizedfile system called/var/mqm.Use apartitionstrategywitha separatevolume forthe WebSphereMQdata.Thismeansthatothersystemactivityisnotaffectedifa large amount ofWebSphereMQworkbuildsup.

Todeterminethesizeofthe/var/mqmfilesystemfora serverinstallation,consider: v _The_maximum_number_of_messages _in_the_system _at_one_time

v _Contingency_for_message_buildups, _if_there_is_a _system_problem

(22)

v _The_average_size_of_the_message_data,_plus₅₀₀ _bytes_for_the_message_header v _The_number_of_queues

v _The_size_of_log_files_and _error_messages

v _The_amount_of_SSL_trace_that_is_written _to_the_{/var/mqm/trace}_directory_(this _is_a newdirectoryforthis release)

Allow50 MBasaminimum foraWebSphereMQserver.Youneedlessspacein /var/mqmfora WebSphereMQclient,typically15 MB.

Creating

separate

file

systems

for

working

data

Youcanalsocreateseparate filesystemsforyour logdata(/var/mqm/log)and errorfiles(/var/mqm/errors).Ifpossible,storelogfilesona differentphysical volume fromtheWebSphereMQqueues(/var/mqm).Thisensures dataintegrityin thecaseofahardwarefailure.

Ifyoucreateseparatefilesystems:

v _The_/var/mqm_and_/var/mqm/log_directories_must _be_on_a_local_file_system. v _The_{/var/mqm/errors}_directory_can_be_NFS_mounted.

Attention

IfyouchoosetoNFS-mount/var/mqm/errors,theerrorlogsmight belostif thenetworkfails.

Ifyouarecreatingseparate filesystems,allowaminimumof 30MBofstoragefor /var/mqm,20MBofstorage for/var/mqm/log,and 4MBof storagefor

/var/mqm/errors.

Ifyouwanttouseindividualqueues thatwillholdmore than2 GBofdata,you must enable/var/mqmtouselargefiles.

The sizeofthelogfiledependsonthelogsettingsthatyouuse.Thesize we recommend isforcircularloggingusingthedefaultsettings.For further informationonlogsizesseetheWebSphereMQSystemAdministrationGuide.

Setting

up

the

user

ID

and

group

Auser IDofthenamemqm,witha primarygroupofmqm,iscreatedautomatically during installation.Afterinstallation,themqm userIDownsthedirectoriesandfiles thatcontaintheresourcesassociatedwith theproduct.

YoucancreatetheuserIDandgroupIDsyourself,asdescribedinthenext section. For example,youmight wanttodo thisifyouaresettingupallsecuritygroups before installingWebSphereMQ.

Creating

the

user

ID

and

group

IfyouwanttocreatetherequireduserIDandgroupIDyourself,youmust doit

before youinstall WebSphereMQ.BothuserIDandgroupIDmustbe settomqm. For stand-alonemachines, youcancreatethenewuserIDandgroup IDslocally; for machinesadministeredinanetworkinformationservices(NIS) domain,an administratormust createtheIDsontheNISmasterservermachine.

YoucanusetheSystemManagementInterfaceTool(smit),for whichyourequire rootauthority.

(23)

1. Tocreatethemqmgroup,displaytherequiredwindow usingthis sequence:

Security & Users Groups

Add a Group

Setthenamefieldtomqm.

2. Tocreatethenewuser,mqm,displaytherequiredwindowusingthissequence:

Security & Users Users

Add a User

Setthenamefieldtomqm.

3. ToaddapasswordtothenewuserID, displaytherequiredwindowusingthis sequence:

Security & Users

Change a Users Password Passwords

Setthepasswordasrequired.

Adding

existing

user

IDs

to

the

group

Ifyouwantto runadministrationcommands,forexamplecrtmqm(createqueue manager) orstrmqm(startqueuemanager),your userIDmustbe amemberofthe mqm group.

Users donotneedmqmgroup authoritytorunapplicationsthatusethequeue manager;it isneededonlyfortheadministrationcommands.

Youcanusesmitto addanexistinguser IDtothemqm group.Display therequired window usingthissequence:

Security & Users Users

Change / Show Characteristics of a User

Enterthenameoftheuser intheUserNamefield.Addmqmto theGroupSET

field,whichisacomma-separatedlistof thegroupstowhichtheuser belongs. Users neednothavetheirprimarygroupsettomqm.Provided thatmqmisintheir set ofgroups,theycanusetheadministrationcommands.

Migrating

from

an

earlier

version

Thissectiondescribes differencesbetweenWebSphereMQforAIX, V5.3and earlier versions oftheproduct,knownpreviouslyasMQSeries.

Changes

to

the

installation

path

Changes inAIXpackagingmeanthatMQSeriesV5.1and laterversions installinto directory /usr/mqm,whereasMQSeriesV5.0installsintodirectory /usr/lpp/mqm. InstallingWebSphereMQforAIX,V5.3failsif afilesystemmounted as

/usr/lpp/mqmisdetected.Ifyouare migratingfromanearlier version,andafile system existsfor thisdirectory,youneedtodooneofthefollowingthingsbefore installingWebSphereMQforAIX, V5.3.Either:

v _Uninstall_your _existing_MQSeries_product, _and_delete_the_file_system _or_move_it tothenew installpathof/usr/mqm

or

Preparation

(24)

v _Move_the_old_file_system_of_/usr/lpp/mqm_to_the_new_installation_path_of

/usr/mqmandcreateasymboliclinkfromtheoldpathtothenewbyissuingthe followingcommand:

ln -s /usr/mqm /usr/lpp/mqm

Ifyouuninstallyour existingMQSeriesproduct,and deleteormoveyourexisting filesystem,youcantheninstall WebSphereMQforAIX,V5.3asdescribedin “Installation procedure”onpage15.

However, ifyoumovetheoldfilesystemtothenewinstallationpath,perform the migration installationdescribedin“Migratingfromanearlier version”onpage18. Ifyouhavealreadysymbolically linkedafilesystemto/usr/lpp/mqm,installing WebSphereMQforAIX, V5.3destroysthefilesystemcontentand thelink, and youareleft withanemptyfilesystem.Inthis case,uninstallyour existing

MQSeriesproductanddeletethefilesystem,or relinkittothenewinstall pathof /usr/mqm,beforeinstallingWebSphereMQforAIX, V5.3.

The installationprocessforWebSphereMQforAIX,V5.3createsa symboliclink fromtheold/usr/lpp/mqmpathtothenew /usr/mqmpath.Thereforeanyexisting scripts ormakefilesthatreference theoldpatharestill valid.

POSIX

standard

threading

library

MQSeriesforAIX,V5.2onwards,usesthePOSIXstandardthreading library (whichwas notavailable onAIXV4.2)tomatchtheimplementationonother UNIX platforms.ExistingMQSeriesapplicationsbuiltonAIX4.2usingthedraft7 levelofPOSIXthreadsarenotaffectedbythisnew implementationand will continuetorununchanged.However, youneedtorecompileWebSphereMQexits and installableservicesandrelinkthemusingthexlc_r compileronAIX4.3touse thefinallevelofthepthreadstandarddefinition(alsoknown asthedraft 10level). Write anynewthreaded applicationsonAIX4.3tousethislevelofthepthreads standard.

Creating

the

system

default

objects

WhenyouusethecrtmqmcommandtocreateaqueuemanagerwithWebSphere MQforAIX,V5.3, thesystem defaultobjectsareautomaticallycreated.Weno longerprovidethesampleMQSC definitionfile,amqscoma.tst.

Ifyouusedamqscoma.tsttocustomize yoursettingsforMQSeriesforAIX, V5.0, and youwanttousethesamesettingswith V5.3oftheproduct:

1. Saveyour copyofamqscoma.tst. 2. InstallWebSphereMQforAIX, V5.3.

3. Loadyour copyofamqscoma.tstand usethefiletore-createyourdefault objects.

Client

applications

An MQSeriesVersion5 clientcanconnecttoallqueuemanagersthatsupport client attach.Note, however,thatyoucannotusefeaturesandstructuresspecificto WebSphereMQforAIX, V5.3inyour clientapplicationif youconnecttoa

non-Version 5.3queuemanager.

(25)

EXTSHM

-

Extended

Shared

Memory

model

By default,AIXhasa differentSystemVSharedMemorymodelfromtheother UNIX platforms.Nomorethan10shared memorysegmentscanbeattached simultaneouslybyanindividualprocess.

With WebSphereMQforAIX, V5.3,queuemanagersusetheAIXextension EXTSHM,whichallowsmorethan10segmentstobe attachedbya singleprocess. ThisisenabledbyexportingtheenvironmentvariableEXTSHM=ONinthe environment beforeaprocess isstarted(thevariablemust beinuppercase). Totakefulladvantageofthisfacility, settheenvironmentvariable EXTSHM=ON intheenvironmentof allWebSphereMQapplicationsbeforetheyare started.All WebSphereMQqueuemanagerprocesseswillset thisvariableforthelifetime of theirprocess,if itisnotalreadysetwhenthequeuemanagerisstarted.

Ifa user’sWebSphereMQapplication choosesnottosetthis variable,itcanstill connectand communicatewith WebSphereMQcorrectly.However,if the application triesto usemoreshared memorythanisavailable inthe10slots providedfor attachingsharedmemorysegments,thatrequestmightfail.

ThetypesofsituationsthatcanincreasethenumberofsegmentsthatWebSphere MQtriestoattachare:

v _Many_threads _all_attach_to_WebSphere_MQ

v _Large_messages _transfer_between_the_application_and_WebSphere_MQ

v _An_application_uses_other_application_libraries,_such_as_database_connections, andtheseotherlibrariesallocatesharedmemoryfromthe10slotsavailable.

Note: Notall applicationssupport theuseoftheEXTSHM=ONenvironment variable.Donotsetthisvalue globally(forexample,in/etc/environment). Itisbetter tosetthisvalue locallyintheprofileofanyuserwhowantsto runWebSphereMQapplications.

National

language

considerations

Thissectionincludesinformationondisplayingmessages inyournational languageand nationallanguagesupportformanuals.

Displaying

messages

in

your

national

language

Messages inthelanguagespecified bythelocaleselectedonyourmachineare installedbydefault.Ifyourequiremessages inadifferentlanguage,ensurethat: 1. Youinstalltheappropriatemessagecatalog (see“WebSphereMQcomponents”

onpage4and “Nationallanguageinstallation”onpage17).

2. YourNLSPATHenvironmentvariable includestheappropriatedirectory. For example,toselectmessagesinGermanusethefollowing:

export LANG=de_DE

export NLSPATH=/usr/lib/nls/msg/%L/%N

Tofind outwhichlanguageiscurrentlyinstalled,usethelocalecommand. Ifa messagecatalog isnotavailable forthislanguage,installamessage catalogfora differentlanguage,oryouwillnotseeanymessages.

Migration

(26)

National

language

support

for

manuals

The documentationforWebSphereMQissupplied inHTMLandPDFformatson a separateCD-ROM.Thedocumentationisavailable inanyof thelanguagesthat are supportedbyWebSphereMQforAIX.

See “Onlineinformation” onpage42formore informationabouthypertextlinking betweenbooks indifferentnational languages.

(27)

Chapter

3. Installing

the

WebSphere

MQ

for

AIX

server

Thischaptertellsyouhow toinstalltheWebSphereMQforAIXserver.

Italso tellsyouhow tomigratefromaversion ofMQSeries(see“Migratingfrom an earlierversion”onpage18),anddescribes someotherproceduresthatmight be neededafteryouhaveinstalledWebSphereMQ.

Chapter4,“Verifyingtheserverinstallation,”onpage23describeshowtoverify thatyour installationoftheWebSphereMQserverisworking.

Ifyouwantto installtheWebSphereMQclient,seeChapter5,“Installingthe WebSphereMQforAIXclient,”onpage33.

Installation

procedure

Thereare differentwaysofinstallingWebSphereMQforAIX.Youcanuse: v _Easy_installation

v _Custom_installation

v _National_language_installation v _Remote_installation

The“Easyinstallation”proceduregivesaminimalconfigurationonyourmachine, consistingofthefollowingcomponents:

v _Runtime v _Base_Kit v _Server

v _Sample_programs

Ifyouwantanyoftheothercomponents,suchasonlinedocumentation, use “Custominstallation”onpage16.

Ifyouwantmessages inadifferentnationallanguagefromthelocaleselectedon your machine,use“National languageinstallation”onpage17.

Toinstall WebSphereMQforAIXona remotemachine,see“Remoteinstallation” onpage18.

Before youstart theinstallationprocedure, makesurethatyouhaveprepared your system asdescribedin“Preparingforinstallation”onpage9.

Note: WerecommendthatyouinstallAIXPTFU472177beforeinstalling

WebSphereMQforAIX,V5.3. ThisPTFupdatesthebos.rte.install fileset onAIXtoVersion4.3.3.17.

WithoutthisPTF,theWebSphereMQproductmightappeartoinstall correctly,eventhoughsomeoftheproductfilesare missing.

Easy

installation

Thisinstallationprocedureusesthexinstallmprogram, whichisavailable inthe X11.vsm.rte optionalfileset.

(28)

By default,theprocedureinstallstheclientcomponentsforWebSphereMQSSL support. IfyoudonotwanttoinstalltheclientcomponentsforWebSphereMQ SSLsupport,seethereadmefilesuppliedwith WebSphereMQforAIX.

1. Loginasroot.

2. InserttheWebSphereMQforAIXServerCD-ROMintotheCD-ROMdrive. 3. EnterthefollowingcommandtomounttheCD-ROM:

mount /cdrom

4. Type: xinstallm -ez

TheWebSphereMQWelcomewindowisdisplayed,followedbya second windowwhere youcanmakesomeselections.

5. ChoosetheCD-ROM softwaresource.

6. For Whichbundleof softwarewouldyouliketoinstall?choose

Media-defined.

7. ClickInstall/Update tocreatethemqm.Serverandmqm.Client. 8. Choosethemqm.Serverbundleand clickInstall/Updateagain.

Thisinstallsthefilesetsinthisbundle, andaworkinprogresswindowgives informationastheinstallationproceeds.

Attheendoftheinstallation,click theViewlogbuttonandscrolltothebottomof thelogtoseethefilesetsthathavebeeninstalledsuccessfully.

Once youhaveinstalledWebSphereMQforAIX,youneedtorunthesetmqcap

command, inputtingthenumberofprocessorsyouhavepaidfor.Therelationship betweenprocessorsandlicenseunitsforUNIX serversisshowninthelicense agreement.

The firsttimeyoustart aqueuemanageronthismachine,if youhavenotalready runthe setmqcapcommand, yougeta warning sayingPurchased licenseunits not set (usesetmqcap). Ifyou havealreadyrunsetmqcap but enteredan

incorrect value, yougetthewarning Insufficientlicense units.Youneed torun

setmqcaptocorrectthis beforeyoucanstart aqueuemanager.

Tochangeyour installation,orbackout afailedinstallation,usetheSystem Management InterfaceTool(smit)inthefollowingtext.

Custom

installation

ThisinstallationprocedureusestheSystemManagementInterfaceTool(smit), enabling youtoselectwhichcomponentsyouwanttoinstall.Thecomponentsand filesetsarelisted in“WebSphereMQcomponents”onpage4;youmustinstall at least theRuntime, BaseKit,and Servercomponents.

1. Loginasroot.

mount /cdrom

4. Selecttherequiredsmitwindow usingthefollowingsequence:

Software Installation and Maintenance Install and Update Software

Install and Update from LATEST Available Software

Installing

the

server

| |

(29)

Alternativelyyoucanusea fastpathcommand(smittyinstall_latest). 5. ClickListtodisplaytheinputdeviceordirectoryforthesoftware. 6. Select/dev/cd0(CD-ROM Drive)andclickOK.

7. UsetheSOFTWAREtoinstall fieldtoobtainalistofavailablefilesets, and selectthefilesetsyouwanttoinstall.

Note: Ifyouinstall theDCE extensions,youwillnotbeabletorunSSL channels.

8. MakesurethatInclude correspondingLANGUAGEfilesets?issettoYes. 9. OnAIXV4.3.3:

a. ClickOKtoinstall WebSphereMQ. OnAIXV5.1:

a. ChangePreviewnewLICENSEagreements?toyes andclickOKtoview thelicenseagreements.

Note: Payparticularattentiontothesectionthatoutlinesthenumberof licenseunitsyouneed,becauseyouwillbeasked latertoconfirm thatyouhavepurchasedsufficientlicenseunitsforthenumberof processorsyouhaveinyour computer.

b. ChangeACCEPTnewlicense agreements?toyesandclick OKtoaccept thelicenseagreementsand installWebSphereMQ.

OnceyouhaveinstalledWebSphereMQforAIX, youneed torunthe

setmqcapcommand,inputtingthenumber ofprocessorsyouhavepaidfor. TherelationshipbetweenprocessorsandlicenseunitsforUNIXservers is shown inthelicenseagreement.

National

language

installation

TheEasy andCustominstallationproceduresinstall messagesinthelanguage, specified bythelocaleselectedonyourmachine,bydefault.Ifyourequire messages inadifferentlanguage,usethefollowingprocedure.

Theprocess issimilarto“Custominstallation”onpage16.Youmustinstall atleast theRuntime,BaseKit,and Servercomponents,inadditiontotheMessageCatalog foryour chosenlanguage.

1. Loginasroot.

mount /cdrom

Install and Update from ALL Available Software

5. Check Listtodisplaytheinputdeviceordirectoryforthesoftware. 6. Select/dev/cd0(CD-ROM Drive)andclickOK.

7. UsetheSOFTWAREtoinstall fieldtoobtainalistofavailablefilesets, and selectthefilesetsyouwanttoinstall (includingthemessagecatalog). 8. OnAIXV4.3.3:

a. ClickOKtoinstall WebSphereMQ. OnAIXV5.1:

Installing

the

server

Chapter3.InstallingtheWebSphereMQforAIXserver

17

| |

(30)

a. ChangePreviewnewLICENSEagreements?toyes andclickOKtoview thelicenseagreements.

Note: Payparticularattentiontothesectionthatoutlinesthenumberof licenseunitsyouneed,becauseyouwillbeasked latertoconfirm thatyouhavepurchasedsufficientlicenseunitsforthenumberof processorsyouhaveinyour computer.

b. ChangeACCEPTnewlicense agreements?toyesandclick OKtoaccept thelicenseagreementsand installWebSphereMQ.

OnceyouhaveinstalledWebSphereMQforAIX,youneed torunthe

setmqcapcommand,inputting thenumber ofprocessorsyouhavepaidfor. TherelationshipbetweenprocessorsandlicenseunitsforUNIXservers is shown inthelicenseagreement.

Remote

installation

Toinstall WebSphereMQforAIXona remotemachine,youcanusestandardAIX techniques.

Todo this,logontobothsystemsasroot.PuttheWebSphereMQforAIXServer CD-ROM intheCD-ROMdriveof themachine fromwhichyouaregoingtotake thecopy.Followthis procedureforeachtarget machineonwhichyouwantto install theproduct:

1. Createa CD-ROMfilesystemonthelocalmachine,and mounttheCD-ROM filesystem onthelocal machine(mount /cdrom).

2. Using smit,exportthisfilesystemusingNFStothetargetmachine.

3. Logontotheremote machineanduseNFStomounttheCD-ROMfilesystem that youcreated (mount local_machine:/cdrom).

4. Usesmittoinstall WebSphereMQforAIXfromthetargetdirectory thatyou specified.

Once youhaveinstalledWebSphereMQforAIX,youneedtorunthesetmqcap

command, inputtingthenumberofprocessorsyouhavepaidfor.Therelationship betweenprocessorsandlicenseunitsforUNIX serversisshowninthelicense agreement.

Reinstalling

WebSphere

MQ

for

AIX

IfyoureinstallWebSphereMQforAIX, acheck ismadetoseeiftheWebSphere MQconfigurationfile(mqs.ini)exists.Ifthefileexists,itiskeptand usedwith the newlyinstalledsystem.Ifthefiledoesnotexist, anemptymqs.ini fileisplacedin thedirectory/var/mqm.

Migrating

from

an

earlier

version

Alwaysbackupthe/var/mqmdirectory beforestartingtomigratefromanearlier version ofMQSeriesforAIX.

Ifyouhaveinstalledanyofthefollowingfilesets,uninstallthembefore you perform themigration.

mqm.java.bindings

(31)

mqm.java.client mqm.java.share mqm.gateway.* mqmjava.base mqmjava.jms mqm.html.*

Tomigrate toWebSphereMQforAIX,V5.3,first endallqueuemanageractivityon thetarget machineandthen usetheSystemManagementInterfaceTool(smit)to updateyour currentlyinstalledcomponents.

1. Loginasroot.

2. InserttheWebSphereMQforAIX,V5.3ServerCD-ROMintotheCD-ROM drive.

Update Installed Software to Latest Level (Update All)

Alternativelyyoucanusea fastpathcommand(smittyupdate_latest). 4. Check ListtodisplaytheSingleSelectListwindow,and select/dev/cd0

(CD-ROM Drive).

5. Check OKtodisplaytheparametersforUpdateAll.

6. For correctmigration,updateall previouslyinstalledWebSphereMQ

(MQSeries)software.Selectthe_update_alloption intheSoftwaretoUpdate

fieldandpressEnter.

7. ClickOK ontheconfirmationwindowtoupdatethesoftware.

Whenallpreviouslyinstalledcomponentshavebeenupdatedtothelatest level, youcaninstallanyadditionalcomponents(includingsupport forJavaifyou uninstalleditbefore theupdate)asdescribedin“Custominstallation”onpage16. Differences betweenWebSphereMQforAIX,V5.3andversionsof MQSeriesare described in“Migratingfromanearlierversion”onpage11.

Migrating

authorization

data

IfyouaremigratingfromMQSeriesV5.1orV5.2,and youareusingthe

compatibility OAM,allauthorizationdataismigrated fromtheauthorizationfiles totheauthorizationqueuethefirst timethatyourestartthequeuemanagerafter installingWebSphereMQforAIX, V5.3.IftheOAMdetectsa missingfileand: v _The_{authorization}_applies_to_a_single _object,_the_OAM_gives_the_mqm_group

accesstotheobjectandcontinueswiththemigration.MessageAMQ5528is writtentothequeuemanager’serrorlog.RefertotheWebSphereMQMessages

bookformoreinformationaboutmessageAMQ5528.

v _The_{authorization}_applies_to_a_class _of_objects,_the_OAM_stops_the_migration._The queuemanager doesnotstart untilthefilehasbeenreplaced.

Youcancontinuetostoreauthorizationdatainfiles.However, ifyoudoso,you cannotexploitanyoftheV5.3improvements(suchasgeneric profiles),and the performance oftheOAMwillbeaffected.ThedefaultOAMservicemoduleis amqzfu. WebSphereMQforAIX,V5.3alsoprovidesthepreviousservicemodule asamqzfu0.Therearetwowaysinwhichyoucanusethepreviousmoduleto continuetostoreauthorizationdatainfiles:

Migration

(32)

v _Modify_the_Module_attribute_in_the_{ServiceComponent}_stanza _of_the_qm.ini_file touseamqzfu0.Notethatthisoptionispossibleonlyforqueuemanagers createdbeforeyoumigratedtoV5.3.

v _Replace_the_amqzfu_module_found_in_/opt/mqm/lib_by_the_previous_version._For example,youcandothisby:

1. Removing theexistingamqzfumodule 2. Renamingamqzfu0asamqzfu

Notes:

1. Youcanrestorethenewamqzfumodulefromthecopy providedasamqzfu1. 2. Once youhavecreatedorrestartedaqueuemanagerwith thenew amqzfu

module,youcannolongerreplacetheamqzfumodulewiththeprevious version.Themigration process,describedabove,isnotreversible.

Youcanview authorizationdatawith thedspmqautand dmpmqautcommands. Refer totheWebSphere MQSystemAdministrationGuideforacompletedescription of thesecommands.

Setting

the

queue

manager

CCSID

The codedcharactersetidentifier(CCSID)isfixed whenyoucreatea queue manager.TheCCSIDisdeterminedbythelocalethatyouusetorunthecrtmqm

command. FormoreinformationonusingcommandsetsseetheWebSphereMQ System AdministrationGuide

The followingtable givessomeexamples ofusingtheLANGparameterinyour NLSPATH environmentvariabletochangethecodeset andCCSID.

Table3.ExamplesofsettingtheCCSID

Example Codeset CCSID

exportLANG=C (thisisthedefaultlocale) ISO8859-1 819 export LANG=en_US ISO8859-1 819 export LANG=En_US IBM-850 850

Tomodify anexistingqueuemanager CCSID,followthisprocedure: 1. StartMQSC commandsbytyping: runmqsc

2. Display theexistingqueuemanagerCCSID, usingtheMQSC command:

display qmgr ccsid

3. ChangetheCCSIDtothenew CCSIDwith theMQSCcommand:

alter qmgr ccsid (new.ccsid)

wherenew.ccsid isthenumberof thenew CCSID. 4. StopMQSCcommandsbytyping: end

5. Stopthequeuemanager,and thenrestart itandanychannelsthatituses. See Chapter10,“CodesetssupportedbyWebSphereMQforAIX,”onpage49for furtherinformationaboutsupportedcode sets.See“Migratingtoeurosupport”on page50forinformationonmigratingtoaCCSIDthatsupportstheeurocharacter.

(33)

User

exits

Check thatyouruser exitsarelinkedwith threadedlibrariesbefore usingthemon this versionoftheproduct.

v _For_further_details_on_threaded _libraries,_and _information_about_{data-conversion} exits,seetheWebSphereMQApplicationProgrammingGuide.

v _For_information_about_channel_exits,_see_the_WebSphere_MQ_{Intercommunication} book.

v _For_information_about_{cluster-workload}_exits,_see_the_WebSphere _MQ_Queue

ManagerClustersbook.

User

exits

(34)

(35)

Chapter

4. Verifying

the

server

installation

Thischapterdescribeshowto verifythattheWebSphereMQforAIXserverhas been correctlyinstalledand configured.YoucanverifyaWebSphereMQserver installationat differentlevels:

v _A_local_{(stand-alone)} _installation_that_has_no_{communication}_links_with_other WebSphereMQinstallations.Thisisdescribedin“Verifyinga localinstallation.” v _A_{server-to-server}_installation_that_includes_{communication}_links_to _other

WebSphereMQinstallations.Thisisdescribedin“Verifyinga server-to-server installation”onpage24.

See Chapter6,“Verifyingtheclientinstallation,”onpage37ifyouhavea client/server installationthatincludescommunicationlinksbetweenaserver machine andaWebSphereMQclient.

Verifying

a

local

installation

Toverify alocalinstallationwith asimpleconfigurationofonequeuemanager and onequeue,usesampleprogramstoputa messageontothequeueand toread themessagefromthequeue.

Note: WebSphereMQobjectdefinitionsarecase-sensitive.Anytextenteredasan MQSCcommandinlowercaseisconvertedautomaticallytouppercase unlessyouencloseitinsinglequotationmarks.Make surethatyoutype the examplesexactlyasshown.

Theproceduresoutlinedinthis sectiondescribehowtoconfigureyour default queuemanagerfromthecommandline.

Setting

up

the

installation

From ashellwindow,usethese stepstoinstall aqueuemanagerand aqueue: 1. Createa defaultqueuemanager calledvenus.queue.managerbyentering the

followingcommand:

crtmqm -q venus.queue.manager

Youwillseemessagestelling youthatthequeuemanagerhasbeen created, andthatthedefaultWebSphereMQobjectshavebeen created.

2. Tostart thequeuemanager,type:strmqm

Amessagetellsyouwhenthequeuemanagerhasstarted.

Thefirst timethatyoustarta queuemanager onamachine,youmightgetone of the following warnings: Purchased license units not set (use setmqcap) or Insufficientlicense units.See “Installation procedure”on page15 for howto correctthis.

3. EnableMQSC commandsbytyping:runmqsc

Amessagetellsyouthatan MQSCsessionhasstarted.MQSChasnocommand prompt.

4. Definea localqueuecalledORANGE.QUEUEbyenteringthefollowingcommand: define qlocal (orange.queue)

(36)

Amessagetellsyouwhenthequeuehasbeencreated. 5. StopMQSCbytyping: end

Youwillseesomemessages,followedbythecommandprompt. Youhavenowdefined:

v _A_default_queue_manager _called_{venus.queue.manager} v _A_queue_called_ORANGE.QUEUE

Testing

the

installation

Totest thequeuemanagerand queue,usetheamqsputsampleprogramtoputa message onthequeue,andtheamqsgetsampleprogramtoget themessageback fromthequeue:

1. Changeintothe/usr/mqm/samp/bindirectory, whichcontains thesample programs.

2. Puta messageonthequeueusingthefollowingcommand: ./amqsput ORANGE.QUEUE

Thefollowingmessagesare displayed: Sample amqsput0 start

target queue is ORANGE.QUEUE

3. Typesomemessagetext, ononeormorelines,followedbyablank line.The followingmessageisdisplayed:

Sample amqsput0 end

Yourmessageisnowonthequeueand thecommandpromptisdisplayed again.

4. Togetthemessagefromthequeue,usethefollowingcommand: ./amqsget ORANGE.QUEUE

Thesampleprogramstarts,andyour messageisdisplayed.Afterapause,the sampleendsandthecommandpromptisdisplayed again.

Youhavenowsuccessfullyverifiedthelocalinstallation.

Verifying

a

server-to-server

installation

Thereare morestepsinvolvedinverifyingaserver-to-serverinstallation,because youneedtocheck thecommunicationslinkbetweenthetwomachines. Beforeyou cando this,youmust ensurethatthecommunicationsprotocolhasbeeninstalled and configuredonbothsystems.WebSphereMQforAIXsupportsbothTCPand SNA.Thisexampleexplainshowtoverifyyour installationifyouareusingTCP; if youare usingSNA,refertotheWebSphereMQIntercommunication manual. Totest theinstallation,set uptwoworkstations,oneasasender andoneasa receiver.Youtestcommunicationsbetweensender andreceiverusingsample programs,whichyoumustinstall onbothworkstations.Theverification procedure assumesthatbothworkstationsare UNIXmachines;ifthis isnotthecase,someof thecommandsaredifferent(fordetails, refertothedocumentationforthe

workstation).

(37)

Note: WebSphereMQobjectdefinitionsarecase-sensitive.Anytextenteredasan MQSCcommandinlowercaseisconvertedautomaticallytouppercase unlessyouencloseitinsinglequotationmarks.Make surethatyoutype the examplesexactlyasshown.

Setting

up

the

sender

workstation

From ashellwindow,usethese stepstoset upthesendermachine: 1. Createa defaultqueuemanager calledsaturn.queue.managerwith the

followingcommand:

crtmqm -q saturn.queue.manager

Messagestellyouthatthequeuemanagerhasbeencreated,andthatthe defaultWebSphereMQobjectshavebeen created.

2. Tostart thequeuemanager,type: strmqm

Thefirst timethatyoustarta queuemanager onamachine,youmightgetone of the following warnings: Purchased license units not set (use setmqcap) or Insufficientlicense units.See “Installation procedure”on page15 for howto correctthis.

3. StartMQSC commandsbytyping: runmqsc

Amessagetellsyouthatan MQSCsessionhasstarted.MQSChasnocommand prompt.

4. Definea localqueuecalledTRANSMIT1.QUEUE (tobeusedasatransmission queue)byentering thefollowingcommand:

define qlocal (transmit1.queue) usage (xmitq) Amessagetellsyouwhenthequeuehasbeencreated.

5. Definea localdefinitionof theremotequeuewith thefollowingcommand: define qremote (local.def.of.remote.queue) rname (orange.queue) + rqmname (’venus.queue.manager’) xmitq (transmit1.queue)

ThenamespecifiedbytheRNAME parametermustbe thesame asthenameof thequeuetowhichyouaresendingthemessage(ORANGE.QUEUEonthereceiver workstation).

6. Definea senderchannelwiththefollowingcommand: define channel (first.channel) chltype (sdr) +

conname (’con-name(port)’) xmitq (transmit1.queue) trptype (tcp)

Thevalue con-nameistheTCPaddress ofthereceiverworkstation, andportis theportname,with 1414asdefault.

7. StopMQSCbytyping: end

Some messagesaredisplayed,followedbythecommandprompt. Youhavenowdefinedthefollowingobjects:

v _A_default_queue_manager_called _{saturn.queue.manager} v _A_transmission_queue_called_{TRANSMIT1.QUEUE}

v _A_local_definition_of_a _remote_queue_called_{LOCAL.DEF.OF.REMOTE.QUEUE} v _A_sender _channel_called_{FIRST.CHANNEL}

Verifying

a

server-to-server

installation

(38)

Setting

up

the

receiver

workstation

Now followthesestepstosetupthereceiver:

1. Createa defaultqueuemanager calledvenus.queue.managerbyenteringthe followingcommand:

crtmqm -q venus.queue.manager

Messagestellyouthatthequeuemanagerhasbeencreated,andthatthe defaultWebSphereMQobjectshavebeen created.

2. Tostart thequeuemanager,type: strmqm

Thefirst timethatyoustarta queuemanager onamachine,youmightgetone of the following warnings: Purchased license units not set (use setmqcap) or Insufficientlicense units. See“Installation procedure” onpage15 for how tocorrectthis.

3. Starta WebSphereMQlistenerasabackgroundtaskbyenteringthefollowing command:

runmqlsr -t tcp &

Youcanusethe-pparametertospecifythenumberofa portthatthelistener shouldlistenon.Ifyoudonotspecifyit,thedefaultof 1414isused. Theport numbermust bethesameastheonethatyouspecifywhensettingupthe sender.

4. EnableMQSC commandsbytyping:runmqsc

AmessagetellsyouthatanMQSCsession hasstarted.MQSChasnocommand prompt.

5. Definea localqueuecalledORANGE.QUEUEbyenteringthefollowingcommand: define qlocal (orange.queue)

Amessagetellsyouwhenthequeuehasbeencreated. 6. Definea receiverchannelwiththefollowingcommand:

define channel (first.channel) chltype (rcvr) trptype (tcp) Amessagetellsyouwhenthechannelhasbeencreated.

7. StopMQSCbytyping:end

Some messagesaredisplayed,followedbythecommandprompt. Youhavenowdefinedthefollowingobjects:

v _A_default_queue_manager _called_{venus.queue.manager} v _A_queue_called_ORANGE.QUEUE

v _A_receiver_channel_called_{FIRST.CHANNEL}

Testing

communication

between

the

workstations

Finally,usetheamqsputsampleprogramtoputamessagefromthesender workstationtoa queueat thereceiver,andtheamqsgetsampleprogramonthe receiverworkstationtogetthemessagefromthequeue:

1. Ifthequeuemanagersonthetwoworkstationshavestopped, restartthemnow bytyping: strmqm

(39)

2. On thesenderworkstation,start thesenderchannelasabackgroundtaskby enteringthefollowingcommand:

runmqchl -c FIRST.CHANNEL -m saturn.queue.manager &

Thereceiverchannelonthereceiverworkstationstartsautomaticallywhenthe sender channelstarts.

3. On thesenderworkstation,change intothe/usr/mqm/samp/bin directory,which containsthesampleprograms.

4. Toputamessageonthelocaldefinitionoftheremotequeue(whichinturn specifiesthenameoftheremotequeue),usethefollowingcommand:

./amqsput LOCAL.DEF.OF.REMOTE.QUEUE

Youwillseethefollowingmessages: Sample amqsput0 start

target queue is LOCAL.DEF.OF.REMOTE.QUEUE

5. Typesomemessagetextononeormorelines,followedbya blankline.You willseethefollowingmessage:

Sample amqsput0 end

Yourmessageisnowonthequeueand thecommandpromptisdisplayed again.

6. On thereceiverworkstation, changeintothe/usr/mqm/samp/bindirectory, whichcontainsthesampleprograms.

7. Togetthemessagefromthequeueatthereceiver,enterthefollowing command:

./amqsget ORANGE.QUEUE

Thesampleprogramstarts,andyour messageisdisplayed.Afterapause,the sampleendsandthecommandpromptisdisplayed again.

Youhavenowsuccessfullyverifiedtheserver-to-serverinstallation.

Verifying

a

server-to-server

installation

(40)

Verifying

the

installation

using

the

JMS

Postcard

application

TousetheJMSPostcard,youmustinstall theoptionalJavaMessagingand sample programs featuresofWebSphereMQ,andyoumust haveaworkingJRE (Java Runtime Environment).

Note: IfyouwanttheJMSPostcardapplicationtousefontandcolorsettings differentfromtheJava VirtualMachinedefaults,changethePostcard.inifile. Formore informationseeWebSphereMQUsingJava.

Use theJMSPostcardapplication toverifythatWebSphereMQissuccessfully installed,theassociatedcommunicationlinksare workingproperly,andthat WebSphereMQJavaMessaging supportissuccessfullyinstalled.

YoucanusetheJMSPostcardapplication toverifya localinstallation(whichdoes nothaveanycommunicationlinkswith otherWebSphereMQinstallations).For furtherinformation,see“UsingtheJMSPostcardapplication toverifyalocal installation”onpage29.

YoucanalsousetheJMSPostcardapplicationtoverifycommunicationbetween your machineandthemachineof anothernameduser,where thatmachineis runningWebSphereMQandusingTCP/IP.Therefore,youcanusetheJMS Postcard applicationtoverifythatyoucancommunicatewithanotherserver.To usetheJMSPostcardapplicationforthis typeofverification,eitherbothmachines must beinthesamecluster (thesimplestmethod),oryoumustconfigurechannels tocommunicatebetweenthetwomachines(see“Verifyinga server-to-server installation”onpage24)

Toensurethatbothmachinesarepart ofthesame cluster,youcandoeitherof the following:

v _Run_the_JMS_Postcard_application _for_the_first _time_on_each_machine._The_JMS

Postcardapplicationdetectsthattherearenolocalqueuemanagersdefinedfor thatmachine,anddisplaystheDefaultConfigurationwizardsothatyoucan createthedefaultqueuemanagersandlinkthemtothedefaultcluster.

v _Create_your_own_queue_managers_on_both_machines,_create_a_cluster,_and _ensure thatthequeuemanagersthatyoucreateoneachmachinebelongtothesame cluster.

YoucanusetheJMSPostcardapplication withexistingqueuemanagers,aslong asbothqueuemanagersbelongtothesame cluster,orcommunicationchannels havebeen configuredbetweenthequeuemanagers.Alternatively,youcan

exchangepostcardsbetweentwoqueuesthatare usingthesamequeuemanageras theirmailbox.

For furtherinformation,see“UsingthePostcard applicationtoverifya server-to-serverinstallation”onpage31.

Setting

up

your

system

to

run

the

JMS

Postcard

Before youcanruntheJMSPostcardapplication, youmust ensurethat:

v _You_are _a_member_of_the_WebSphere_MQ_{administrators}_group_(mqm)._If_you_are nota memberofmqm,ask someonewhoisamembertoruntheDefault

Configurationtoolonyourbehalf,eitherdirectly,orbyrunningtheJMS Postcardapplication,whichrunstheDefault Configurationtoolindirectly.

WebSphere MQ for AIX. Quick Beginnings GC

WebSphere

MQ

for

AIX

Quick

Beginnings

Version

5.3

WebSphere

MQ

for

AIX

Quick

Beginnings

Version

5.3

Contents

Tables

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. v

Welcome

to

WebSphere

MQ

for

AIX

.

. vii

What’s

new

in

WebSphere

MQ

for

AIX,

Version

5

Release

3

.

.

.

.

.

.

.

.

. ix

Chapter

1.

Planning

to

install

WebSphere

MQ

for

AIX

.

.

.

.

.

.

.

. 1

Chapter