WebSphere MQ for Solaris. Quick Beginnings GC

WebSphere

MQ

for

Solaris

Quick

Beginnings

Version

5.3

GC34-6075-02

WebSphere

MQ

for

Solaris

Quick

Beginnings

Version

5.3

GC34-6075-02

Note!

Beforeusingthisinformationandtheproductitsupports,besuretoreadthegeneralinformationunder“Notices”onpage 47.

Thirdedition(May2004)

ThiseditionappliestoWebSphereMQforSolaris,V5.3,andtoallsubsequentreleasesandmodificationsuntil otherwiseindicatedinneweditions.

Contents

Tables

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. v

Welcome

to

WebSphere

MQ

for

Solaris

vii

Roadmap. . . vii

Conventions . . . vii

What’s

new

in

WebSphere

MQ

for

Solaris,

Version

5

Release

3

.

.

.

.

.

. ix

Chapter

1.

Planning

to

install

WebSphere

MQ

for

Solaris

.

.

.

.

.

.

. 1

Hardwarerequirements. . . 1

Diskstorage . . . 1

Prerequisitesoftware . . . 2

Operatingsystem. . . 2

Connectivity . . . 2

SSL(SecureSocketsLayer). . . 3

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

Chapter

2.

Preparing

to

install

WebSphere

MQ

for

Solaris

.

.

.

.

.

.

. 7

Preparingforinstallation . . . 7

CreatingWebSphereMQfilesystems . . . 7

SettinguptheuserIDandgroup . . . 8

Migratingfromanearlierversion . . . 9

Changestoqm.iniforLU62channelsusing Sunlink9.1 . . . 9

Creatingthesystemdefaultobjects. . . 9

Clientapplications . . . 9

Nationallanguageconsiderations . . . 9

Displayingmessagesinyournationallanguage. . 9

Nationallanguagesupportformanuals . . . . 9

Chapter

3.

Installing

the

WebSphere

MQ

for

Solaris

server

.

.

.

.

.

.

.

. 11

Kernelconfiguration . . . 11

Semaphores . . . 11

Filedescriptors . . . 12

Installationprocedure. . . 12

Silentinstallation . . . 13

Migratingfromanearlierversion . . . 14

Migratingauthorizationdata . . . 14

SettingthequeuemanagerCCSID. . . 15

Userexits . . . 15

Chapter

4.

Verifying

the

server

installation

.

.

.

.

.

.

.

.

.

.

.

.

. 17

Verifyingalocalinstallation. . . 17

Settinguptheinstallation . . . 17

Testingtheinstallation. . . 18

Verifyingaserver-to-serverinstallation . . . 18

Settingupthesenderworkstation. . . 19

Settingupthereceiverworkstation . . . 20

Testingcommunicationbetweentheworkstations 20 VerifyingtheinstallationusingtheJMSPostcard application . . . 22

SettingupyoursystemtoruntheJMSPostcard 22 UsingtheJMSPostcardapplicationtoverifya localinstallation. . . 23

UsingthePostcardapplicationtoverifya server-to-serverinstallation . . . 25

Chapter

5.

Installing

the

WebSphere

MQ

for

Solaris

client

.

.

.

.

.

.

.

.

. 27

Installationprocedure. . . 27

MigratingtoandfromtheWebSphereMQSSL support. . . 28

Installingtheclientonthesamemachineasaserver 28

Chapter

6.

Verifying

the

client

installation

.

.

.

.

.

.

.

.

.

.

.

.

. 29

Verifyingtheinstallation . . . 29

Settinguptheserverworkstation . . . 29

Settinguptheclientworkstation . . . 30

Testingcommunicationbetweentheworkstations 31

Chapter

7.

WebSphere

MQ

documentation

.

.

.

.

.

.

.

.

.

.

. 33

Hardcopybooks. . . 33

Onlineinformation. . . 34

Publicationssuppliedwiththeproduct . . . . 34

HTMLandPDFbooksontheWorldWideWeb 35 Onlinehelp . . . 35

SupportPacs . . . 35

WebSphereMQnewsgroups. . . 35

Whitepapersandmigrationdocuments . . . . 35

Servicesupportsummary(PTFreadmes) . . . 35

Chapter

8.

Applying

maintenance

to

WebSphere

MQ

for

Solaris

.

.

.

.

.

. 37

InstallingaPTF . . . 37

Restoringthepreviousservicelevel . . . 38

Chapter

9.

Uninstalling

WebSphere

MQ

for

Solaris

.

.

.

.

.

.

.

.

.

.

.

.

. 39

Uninstallationprocedure . . . 39

Chapter

10.

Code

sets

supported

on

WebSphere

MQ

for

Solaris

.

.

.

.

.

. 41

Migrationtoeurosupport . . . 46

Notices

.

.

.

.

.

.

.

.

.

.

.

.

.

. 47

Trademarks . . . 48

Index

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 51

Tables

1. Gettingstartedroadmap. . . vii

2. ExamplesofsettingtheCCSID . . . 15

3. WebSphereMQfamilybooks . . . 33

4. LocalesandCCSIDsforSolaris . . . 41

Welcome

to

WebSphere

MQ

for

Solaris

ThisbookdescribesWebSphereMQforSolarisVersion5.3andexplainshow to planfortheproduct,installit,and verifythattheinstallationhasworked. See the:

v _{WebSphereMQBibliographyandGlossary foranexplanationoftermsusedinthis} book

v _{WebSphereMQSystemAdministrationGuideforfurtherinformationonusingthe} controlcommandscrtmqm,strmqm,andendmqm

Road

map

Use Table1 tofindtheinformationthatyouneedtoget startedwithWebSphere MQforSolaris.

Table1.Gettingstartedroadmap

Ifyouwantto... Referto...

Learnaboutsystemrequirementsfor WebSphereMQforSolaris

Chapter1,“PlanningtoinstallWebSphere MQforSolaris,”onpage1andChapter2, “PreparingtoinstallWebSphereMQfor Solaris,”onpage7

InstallWebSphereMQforSolaris Chapter3,“InstallingtheWebSphereMQfor Solarisserver,”onpage11andChapter4, “Verifyingtheserverinstallation,”onpage 17

InstalltheWebSphereMQforSolarisclient Chapter5,“InstallingtheWebSphereMQfor Solarisclient,”onpage27andChapter6, “Verifyingtheclientinstallation,”onpage29 ReadmoreaboutWebSphere®

MQ Chapter7,“WebSphereMQdocumentation,” onpage33

ApplymaintenancetoWebSphereMQfor Solaris

Chapter8,“Applyingmaintenanceto WebSphereMQforSolaris,”onpage37 UninstallaWebSphereMQforSolarisserver

orclient

Chapter9,“UninstallingWebSphereMQfor Solaris,”onpage39

Conventions

Knowingtheconventionsusedinthisbookwillhelpyoutouseitmoreefficiently. v _{Boldfacetypeindicatesthenameofanitemthatyouneedtoselectorthename}

ofacommand.

v _{Italicstypeindicatesnew terms,booktitles,orvariableinformationthatmustbe} replacedbyanactualvalue.

v _{Monospacetypeindicates anexample(suchasa fictitiouspathorfilename)or} textthatisdisplayedonthescreen.

What’s

new

in

WebSphere

MQ

for

Solaris,

Version

5

Release

3

WebSphereMQforSolaris,Version5Release3 providesthefollowingnew and changed functions:

v _{WebSphereMQforSolaris nowsupportsWebSphereMQchannelsprotected} usingtheindustrystandardSecureSocketsLayer(SSL).SeeWebSphereMQ Securityfordetails.ThissupportisbasedonIBM® _{GlobalSecurityKit;acopyof} thisproductisincludedwithWebSphereMQ.

v _{SupportforJava}™_{isintegratedwithintheproduct.Thisreplacesthesupport} previouslyprovided byMQSeries®_SupportPac™_MA88.

v _{Productdocumentationisnow suppliedonseparateCD-ROMs.}

v _{SupportforWebAdministrationandtheInternet Gatewayhasbeen removed.If} youhavethesefeaturesinstalledfromapreviousrelease oftheproduct, you willlosethemwhenyouupgrade.

v _{Anew formoflicensemanagementisimplementedforthis releaseofthe} product.

v _{WebSphereMQnowsupportsgenericauthorityadministration.}

Chapter

1.

Planning

to

install

WebSphere

MQ

for

Solaris

ThischapterdescribestheprerequisitesforrunningWebSphereMQfor Solaris, V5.3, including:

v _{“Hardwarerequirements”}

v _{“Prerequisitesoftware”onpage2} v _{“Optionalsoftware”onpage3}

Thesoftware thatissupplied withtheWebSphereMQforSolaris productpackage isdescribedin:

v _{“Delivery”onpage4}

v _{“WebSphereMQcomponents”onpage4}

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

Hardware

requirements

WebSphereMQforSolaris,V5.3runsonall SunSPARCandSunUltraSPARC desktopand serversystems,supportedbytheappropriatereleaseof theSolaris operatingenvironment,asshown in“Prerequisitesoftware”onpage2.

Disk

storage

Thestorage requirementsforWebSphereMQforSolaris,V5.3dependonwhich 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 _{Serverinstallation:50MB}

v _{Clientinstallation:15MB} v _{Datastorage(server):50MB} v _{Datastorage(client):5 MB}

Use thedf-kcommandtodeterminetheamount offreespaceonyour system. Diskstorageisalsorequiredfor:

v _{Prerequisitesoftware} v _{Optionalsoftware}

v _{Yourapplication programs}

See “Preparingforinstallation”onpage7 forinformationaboutcreating thefile systemsyouneedtoinstalland runWebSphereMQforSolaris.

Prerequisite

software

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

Note: WebSphereMQdoesnotsupporthostnamesthatcontainspaces.Ifyou installWebSphereMQonacomputerwith ahostnamethatcontainsspaces, youwillbeunabletocreateanyqueuemanagers.

Operating

system

The operatingsystem supportedbyWebSphereMQforSolaris, V5.3is: v _{SunSolaris 7(32bit) withpatches:}

– 107171–02 –patchadd,patchrmpatch. Installthispatchfirst – 107544–03 –fsckpatch. (mustbe installedbefore 106541–17) – 106950–16 –linkerpatch

– 106327–11–32bitsharedlibrarypatchforC++ – 106300–10 –64bitsharedlibrarypatchforC++ – 106541–18 –kernelupdatepatch

– 106980–17 –libthreadpatch

Note: Laterversionsofthesame,orequivalent,patchesalsowork. v _{SunSolaris 8(32bit)}

Youmust installthepatcheslisted forSunSolaris 7,plusthefollowingpatches orequivalentsupersedinglevelsbeforeyouinstallWebSphereMQ:

– 108827–12 – 111177–06

IfyouaregoingtousetheSSLsupportprovidedbyWebSphereMQ,youmust alsoapplythefollowingpatchesorequivalentsuperseding levels:

– 108434–02 – 111327–02 – 108991 – 108528

Connectivity

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

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

The networkprotocols supportedbyWebSphereMQforSolaris,V5.3are:

v _TCP/IP

v _SNALU6.2

TCP/IPispartofthebaseoperatingsystem.For SNAconnectivityyoucanuse anyofthefollowing:

v _{Peer-to-PeerVersion9.1}

v _{DataConnectionSNAP-IXV6.2orlater} v _{BrixtonSNAserver}

Iftoken ringisused,youneedSunTRI Driver4.0orlater.

SSL

(Secure

Sockets

Layer)

Ifyouwantto usetheSSLsupport,youneedIBMGlobalSecurityKitV6.Thisis supplied withWebSphereMQ.

Optional

software

Thefollowingproductscanbeusedwith WebSphereMQforSolaris,V5.3, butare notrequired.Unlessotherwisestated,theseproductsapplyonlytoserver

installations ofWebSphereMQ.

Compilers

Thefollowingcompilers aresupportedforWebSphereMQforSolaris,V5.3 applications:

v _{SunWorkshopcompilerCV5.0} v _{SunWorkshopcompilerC++V5.0} v _{ForteC6(SunWorkshop6C)}

v _{ForteC++6(SunWorkshop6C++)includingupdate2} v _{MicroFocusServer expressV2.0.10}

v _{Java2Standard Edition,fortheSolaris OperatingEnvironment,SDK1.3.1}

Transaction

monitors

Thefollowingtransactionprocessingmonitors(coordination throughX/OpenXA interface) aresupported:

v _{BEATUXEDOV6.4and V6.5}

v _{WebSphereApplicationServer V4.0} v _TXSeries™_{forSolarisV4.3}

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

Databases

Thefollowingdatabasesaresupported: v _DB2®_{Universal DatabaseV7.1orV7.2} v _{Oracle8iR3(8.1.7)andOracle 9i} v _{SybaseV12orV12.5:}

– AdaptiveServer Enterprise(A.S.E.),V11.5 – OpenClient(ctliband dblib),V11.1

– Embedded SQL/C,V11.0

– XAServer,V11.1

– SybaseAdaptiveServer Enterprise,V12: - WithDTMoption

- Withthelatestpatches installed(testedwithEBF9090)

- WithenvironmentvariablesSYBASEand SYBASE_OCSsettoappropriate valuesintheshellfromwhichyoustart aqueuemanageror application program

For informationonhowtosetupXAcoordination,seetheWebSphereMQSystem AdministrationGuide.

Software

requirements

DCE

The followingDCE productsaresupportedfor clientandserverinstallationsof WebSphereMQ.IfyouwanttoruntheDCEsend,receive, ormessageexits supplied byWebSphereMQ,youmust usea DCEproductthatsupportsDESdata encryption.

v _{IBMDCEV3.1forSunSolaris 7} v _{IBMDCEV3.2forSunSolaris 8}

DCE namesandsecuritymodulesareprovidedwith WebSphereMQforSolaris, V5.3.

Note: Ifyouinstall theWebSphereMQDCEextensions, youwillnotbeableto useSSLchannels.

Java

IfyouwanttousetheJavaMessagingSupport,youneed theJava Runtime Environment Version1.3orlater.

Delivery

WebSphereMQforSolaris,V5.3issupplied onanumberof CD-ROMs,asfollows: v _{WebSphereMQforSolaris Server}

v _{WebSphereMQClients (2CDs)}

v _{WebSphereMQDocumentation}

WebSphereMQforSolariscanbe installedasa serveroraclient.Seethe

WebSphere MQSystemAdministrationGuideforanexplanationofclientand server installations ofWebSphereMQ.

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

The documentationCD-ROMscontaintheproductdocumentationinHTMLand PDFformats.

WebSphere

MQ

components

WhenyouinstallWebSphereMQfor Solaris,V5.3,youcanchoosewhich componentsto install.

Server

The componentsavailableontheServerCD-ROMareasfollows:

Server Provides messagingandqueuingservices toapplications,andsupport for WebSphereMQclientconnections.

Client 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

SampleprogramsforDCE support.

Java messaging

Thefiles neededformessagingusingJava(includesJava Messaging Service).

Messagecatalogs

Amessagecatalogin U.S.Englishisinstalledautomatically.Message catalogsarealso availableforthefollowingnationallanguages: v _{Brazilian Portuguese} v _French v _German v _Italian v _Japanese v _Korean v _Spanish v _{SimplifiedChinese} v _{TraditionalChinese} Manpages

UNIX® manpages,inU.S.English,forthefollowing:

v _{Controlcommands}

v _{MessageQueue Interface(MQI)commands}

v _{MQSC commands}

WebSphereMQ supportfortheGlobal SecurityKit(GSKit)andtheKey Managementtool(iKeyman)

Needed forSSL.

IBMGlobal SecurityKitV6

Needed forSSL.

Client

Thefollowingcomponentsof WebSphereMQforSolarisare availableonthe Clients CD-ROM.Fora descriptionofeachcomponent, see“Server” onpage4.

Client

Sampleprograms Messagecatalogs Manpages

Documentation

HTMLandPDFversionsof theWebSphereMQforSolarisbooks areavailableon theDocumentationCD-ROMpackage,ontwoCD-ROMs,insomeorallofthe followingnationallanguages:

v _{BrazilianPortuguese} v _French v _German v _Italian v _Japanese v _Korean v _Spanish v _{SimplifiedChinese}

WebSphere

MQ

components

v _{TraditionalChinese} v _U.S.English

See “Onlineinformation” onpage34fordetailsofthedocumentationCD-ROM package.

Note: HTMLand PDFversionsoftheWebSphereMQbooks canbe viewed directlyfromtheCD-ROMs.

readme

file

Before startingtoinstallWebSphereMQforSolaris,reviewthereadmefileforthe latest informationontheproduct.Thereadmefilesfor allsupportednational languages arefoundintheREADMESdirectoryoneachCD-ROM.

Chapter

2.

Preparing

to

install

WebSphere

MQ

for

Solaris

Thischapterdescribeswhattodotoprepareyour systemforinstallingWebSphere MQforSolaris (see“Preparingforinstallation”).

Ifyouaremigratingfromanearlierversionof MQSeries,read“Migratingfroman earlier version”onpage9.

“National languageconsiderations”onpage9 describeshowto selectthenational languageforyour WebSphereMQinstallation.

Preparing

for

installation

Before youinstall WebSphereMQforSolaris,youneedto:

1. CreatethefilesystemsusedtoholdWebSphereMQanditsdata. 2. SetuptheuserIDandgroupforWebSphereMQ.

Creating

WebSphere

MQ

file

systems

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

Creating

a

file

system

for

the

product

code

Install WebSphereMQforSolaris in/opt/mqm.Thespacerequireddependsonhow manycomponentsyouinstall.Typicallyyouneed50 MBforaserverinstallation, or15 MBfora clientinstallationwithoutSSL.

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

1. Createa newfilesystemandmountit as/opt/mqm.

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

mkdir /bigdisk/mqm

ln -s /bigdisk/mqm /opt/mqm

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 WebSphereMQforSolaris,createand mountafilesystem called/var/mqm.Usea partitionstrategywitha separatevolumefor theWebSphere MQdata.Thismeansthatothersystem activityisnotaffected ifalargeamount of WebSphereMQworkbuildsup.

Todeterminethesizeofthe/var/mqmfilesystemfora serverinstallation,consider: v _{Themaximumnumberofmessages inthesystem atonetime}

v _{Contingencyformessagebuildups, ifthereisa systemproblem}

v _{Theaveragesizeofthemessagedata,plus500 bytesforthemessageheader}

v _{Thenumberofqueues}

v _{Thesizeoflogfilesand errormessages}

v _{TheamountofSSLtracethatiswritten tothe/var/mqm/tracedirectory}

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/mqmand/var/mqm/logdirectoriesmust beonalocalfilesystem.} v _{The/var/mqm/errorsdirectorycanbeNFSmounted.}

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 thathold morethan2GBofdata,youmust mountthefilesystemwith thelargefiles option.

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

Setting

up

the

user

ID

and

group

Auser IDofthenamemqm,witha primarygroupofmqm,isrequired.Themqm user IDownsthedirectoriesand filesthatcontaintheresources associatedwiththe product.Youmustcreatetheuser IDand groupIDsyourself,asdescribed inthe next section.

Creating

the

user

ID

and

group

Youmust createtherequireduserIDandgroupIDbeforeyouinstallWebSphere MQ.BothuserIDandgroup IDmust besettomqm.Forstand-alonemachines, you cancreatethenewuser IDand groupIDslocally;formachinesadministeredina networkinformationservices(NIS) domain,anadministratormustcreatetheIDs ontheNISmasterservermachine.

Adding

existing

user

IDs

to

the

group

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

Users donotneedmqm groupauthoritytorunapplicationsthatusethequeue manager;it isneededonlyfortheadministrationcommands.

Migrating

from

an

earlier

version

Thissectiondescribes differencesbetweenWebSphereMQforSolaris,V5.3and earlier versionsoftheproduct,known previouslyasMQSeries.

Changes

to

qm.ini

for

LU62

channels

using

Sunlink

9.1

InWebSphereMQforSolaris,V5.3,itispossibletochoosewhichLU6.2 softwareis used. ForSunlink 9.1a newentryisrequiredundertheLU6.2stanza. Fordetails seetheWebSphereMQSystemAdministrationGuide.

Creating

the

system

default

objects

WhenyouusethecrtmqmcommandtocreateaqueuemanagerwithWebSphere MQforSolaris, V5.3,thesystemdefaultobjectsareautomaticallycreated.Weno longerprovidethesampleMQSC definitionfile,amqscoma.tst.

Ifyouusedamqscoma.tsttocustomize yoursettingsforMQSeriesforSolaris, V5.0, andyouwanttousethesame settingswithV5.3of theproduct:

1. Saveyourcopy ofamqscoma.tst. 2. InstallWebSphereMQforSolaris,V5.3.

3. Loadyourcopy ofamqscoma.tstand usethefiletore-createyourdefault objects.

Client

applications

An MQSeriesVersion5 clientcanconnecttoallqueuemanagersthatsupport client attach.Note, however,thatyoucannotusefeaturesandstructuresspecificto WebSphereMQforSolaris,V5.3inyourclientapplication ifyouconnecttoa non-Version 5.3queuemanager.

National

language

considerations

Thissectionincludesinformationondisplayingmessages inyournational languageand nationallanguagesupportformanuals.

Displaying

messages

in

your

national

language

Messages inU.S.Englisharealwaysavailable. Ifyourequiremessages ina differentlanguage,ensurethat:

1. Youinstalltheappropriatemessagecatalog (see“WebSphereMQcomponents” onpage4).

2. YourNLSPATHenvironmentvariable includestheappropriatedirectory. For example,toselectmessagesinGermanusethefollowing:

export LANG=de

export NLSPATH=/usr/lib/locale/%L/LC_MESSAGES/%N

Tofind outwhichlanguageiscurrentlyinstalled,usethelocalecommand.

National

language

support

for

manuals

ThedocumentationforWebSphereMQissupplied inHTMLandPDFformatson a separateCD-ROM.Thedocumentationisavailable inanyof thelanguagesthat are supportedbyWebSphereMQforSolaris.

Migration

See “Onlineinformation” onpage34formore informationabouthypertextlinking betweenbooks indifferentnational languages.

Chapter

3.

Installing

the

WebSphere

MQ

for

Solaris

server

Thischaptertellsyouhow toinstalltheWebSphereMQforSolaris server. Italso tellsyouhow tomigratefromaversion ofMQSeries(see“Migratingfrom an earlierversion”onpage14),anddescribes someotherproceduresthatmight be neededafteryouhaveinstalledWebSphereMQ.

Chapter4,“Verifyingtheserverinstallation,”onpage17describeshowtoverify thatyour installationoftheWebSphereMQserverisworking.

Ifyouwantto installtheWebSphereMQclient,seeChapter5,“Installingthe WebSphereMQforSolarisclient,” onpage27.

Kernel

configuration

WebSphereMQusessemaphores,sharedmemory,and filedescriptors,andit is probable thatthedefaultkernelconfigurationisnotadequate.

Semaphores

Before installation,reviewthemachine’sconfiguration. Todothistype the followingcommand:

sysdef -i

To changethe values,adda set parameter = value lineto the/etc/system file. For furtherinformationonsettingupthesystem,seetheSolarisSystem

Administration documentation.

Notes:

1. Donotchangethevalue ofshmminfromthesystemdefaultvalue.

2. Semaphore andswapusagedoesnotvarysignificantlywithmessagerate or persistence. set shmsys:shminfo_shmmax = 4294967295 set shmsys:shminfo_shmseg = 1024 set shmmin:shminfo_shmmin = 1 set shmsys:shminfo_shmmni = 1024 set semsys:seminfo_semmni = 1024 set semsys:seminfo_semaem = 16384 set semsys:seminfo_semvmx = 32767 set semsys:seminfo_semmap = 1026 set semsys:seminfo_semmns = 16384 set semsys:seminfo_semmsl = 100 set semsys:seminfo_semopm = 100 set semsys:seminfo_semmnu = 2048 set semsys:seminfo_semume = 256 set msgsys:msginfo_msgmni = 50 set msgsys:msginfo_msgmap = 1026 set msgsys:msginfo_msgmax = 4096 set msgsys:msginfo_msgmnb = 4096

Figure1.SettingkernelparametervaluesonaSolarissystem

3. WebSphereMQqueuemanagersaregenerallyindependentofeachother. Thereforesystemkernelparameters,forexampleshmmni,semmni,semmns,and semmnuneedtoallowforthenumberofqueuemanagersinthesystem. 4. Youneed toset thekernelparametersset msgsys:msginfo_msgmap and

msgsys:msginfo_msgmaxonlyifyouareusingcircularlogging.

File

descriptors

Solaris hasa lowdefaultsystemsoft limitforthenumberoffiledescriptors.When runninga multi-threadedprocess,youmight reachthesoftlimit forfile

descriptors.ThisgivesyoutheWebSphereMQreasoncode

MQRC_UNEXPECTED_ERROR (2195)and,ifthereareenoughfiledescriptors,a WebSphereMQFFST™file.

Toavoidthisproblemyoucanincreasethesystemsoftlimitfor thenumber offile descriptors.Todothis,editthe/etc/systemfileandchangethevalueofthe system softlimittomatchthesystemhardlimit(1024)byaddingset rlim_fd_cur=1024.

Additionally,if youare runningWebSphereMQundertheLotus®Domino™ server,youcanreducethenumberofactiveserverthreads intheDomino HTTP serverprocess byopening theserverNameandaddressbook,andreducingthe

Number activethreadsvalue ontheserverdocumenttobetween50and 60.

Installation

procedure

Thissectiondescribes theinstallationof theWebSphereMQforSolarisserver, usingthepkgaddprogram, enablingyoutochoosewhichcomponentsyouwant toinstall. Thecomponentsarelistedin“WebSphereMQcomponents” onpage4; youmustinstall atleasttheServer component.

Note: Ifyouare usinga screenreader,youare recommendedtousethe

non-interactiveinstallationoption“Silentinstallation”onpage13,sothat youcanacceptthelicensewithoutviewingit.

Before youstart theinstallation procedure,makesurethatyouhaveprepared your system asdescribedin“Preparingforinstallation”onpage7.

1. Loginasroot.

2. MounttheWebSphereMQforSolarisServer CD-ROM.

v _{IfyouuseSolarisvolume managertomounttheCD-ROM,mqlicense.sh} willbe installedinto /cdrom/mq_solarisdirectory.

v _{IfyouarenotusingSolarisvolume managertomounttheCR-ROM,} mqlicense.shwillbeinstalledintoa directoryofyour choice,forexample /cdromdirectory.

3. Changeinto thedirectory containingmqlicense.sh,forexample:

cd /cdrom

4. Runthemqlicense.shscripttoacceptthelicense:

./mqlicense.sh

Ifyouwanttoviewatext-only versionofthelicense,whichcanberead bya screen-reader,type:

./mqlicense.sh -text_only

The licenseisdisplayed.

Kernel

configuration

| | | | | | | |

Note: Payparticularattentiontothesectionthatoutlinesthenumberof licenseunitsyouneed,becauseyouwillbeaskedlatertoconfirmthat youhavepurchasedsufficient licenseunits forthenumber of

processorsthatyouhaveinyourcomputer.

Ifyouacceptthelicense,theinstallationcontinues.Ifyoudonotacceptthe license, youcannotcontinuetheinstallationprocess.

5. Enterthefollowingcommandtostart theinstallationprocess:

pkgadd -d /cdrom

IfyouusetheSolaris volumemanagertomounttheCD,thecommandto start theinstallationis:

pkgadd -d /cdrom/mq_solaris

6. Youare presentedwitha listofthepackagesthatareavailable. Enterthe number ofthemqmpackage.

7. Enterthenumbersofthecomponentsthatyourequire,separatedbyspacesor commas,after thelistofcomponentsisdisplayed.

8. Answer yornwhenyouareaskedwhether youwanttoinstalltheDCE option.

Note: Ifyouanswer y,youwillnotbe abletorunSSLchannels. 9. Answer ytotheotherquestions.

10. Amessageisissuedwhentheinstallationiscomplete.Enterqtoexitthe

pkgadd program.

Note: Duringtheinstallationprocessyoumust selectyes ifyouarepromptedto choosewhethertoinstall certainWebSphereMQfilesassetuid/setgid files. Once youhaveinstalledWebSphereMQforSolaris, youneedtorunthesetmqcap

command, inputtingthenumberofprocessorsyouhavepaidfor.Therelationship betweenprocessorsandlicenseunitsforUNIX serversisshown inthelicense agreement.

Thefirst timethatyoustarta queuemanageronthismachine,ifyouhavenot alreadyrunthesetmqcapcommand, youget a warningsayingPurchased license units not set (use setmqcap). Ifyou havealreadyrun setmqcapbut entered an incorrect value, yougetthewarning Insufficientlicense units.Youneed torun

setmqcaptocorrectthis beforeyoucanstart aqueuemanager.

Silent

installation

Youcanperforma silentinstallationofWebSphereMQforSolaris.Ascriptfile called silent.shissuppliedinthesilentdirectoryontheCD-ROM.Thisscript allows youtoperforma non-interactiveinstallationthatrequiresnoinputand displays nooutputonthescreen.

Theinstallation scriptsilent.shusesanadminfileand aresponsefile,bothof whichare suppliedinthesilentdirectory.Youcanusethesefilesassuppliedto perform asilentinstallationforallthecommonfeatures, includingallthenational languagefeatures, withouttheDCEcomponent.

By default,thesilent.sh scriptassumesthattheWebSphereMQServerCD-ROM hasbeenmounted on/cdromand itwritesalloutputandlogs tothefile

/tmp/mq.install.Ifyouwanttoalterthese values,copysilent.sh andtheadmin and responsefilestoawritabledirectory, makethenecessary changes,andrunthe script fromthemodifiedlocation.

Installing

the

server

Youalso needtoedittheresponsefileifyouwanttochangethecomponentsto install, forexample,becauseyoudonotwantallthenationallanguagefeatures. Whenyouhavecheckedthescriptfilesandmadeanychangesrequired, run silent.sh tostarttheinstall.WhentheinstallationofWebSphereMQforSolaris is complete, checkthelogfileforanyerrors.

Once youhaveinstalledWebSphereMQforSolaris, youneedtorunthesetmqcap

command, inputtingthenumberofprocessorsyouhavepaidfor.Therelationship betweenprocessorsandlicenseunitsforUNIX serversisshowninthelicense agreement.

Migrating

from

an

earlier

version

Alwaysbackupthe/var/mqmdirectory beforestartingtomigratefromanearlier version ofMQSeriesforSunSolaris.

Tomigrate toWebSphereMQforSolaris, V5.3:

1. Endallqueuemanageractivity onthetarget machine.

2. UninstalltheoldMQSeriesproductasdescribed inChapter9,“Uninstalling WebSphereMQforSolaris,”onpage39.Donotdeletethe/var/mqmdirectory treeifyouwanttoretain existingMQSeriesinformation,forexampleyour queuemanagerdata.

3. InstallWebSphereMQforSolaris,V5.3asdescribed in“Installationprocedure” onpage12.

Differences betweenWebSphereMQforSolaris, V5.3andversions ofMQSeriesare described in“Migratingfromanearlierversion”onpage9.

Migrating

authorization

data

IfyouaremigratingfromMQSeriesV5.1orV5.2,and youareusingthe

compatibility OAM,allauthorizationdataismigrated fromtheauthorizationfiles totheauthorizationqueuethefirst timethatyourestartthequeuemanagerafter installingWebSphereMQforSolaris,V5.3.IftheOAMdetectsamissingfileand: v _{Theauthorizationappliestoasingle object,theOAMgivesthemqmgroup}

accesstotheobjectandcontinueswiththemigration.MessageAMQ5528is writtentothequeuemanager’serrorlog.RefertotheWebSphereMQ MessagesbookformoreinformationaboutmessageAMQ5528.

v _{Theauthorizationappliestoaclass ofobjects,theOAMstopsthemigration.The} queuemanager doesnotstart untilthefilehasbeenreplaced.

Youcancontinuetostoreauthorizationdatainfiles.However,ifyoudoso,you cannotexploitanyoftheV5.3improvements(suchasgeneric profiles),and the performance oftheOAMwillbeaffected.ThedefaultOAMservicemoduleis amqzfu. WebSphereMQforSolaris, V5.3alsoprovides theprevious service module asamqzfu0.Therearetwowaysinwhichyoucanusetheprevious module tocontinuetostoreauthorizationdatainfiles:

v _{ModifytheModuleattributeintheServiceComponentstanza oftheqm.inifile} touseamqzfu0.Thisoptionispossibleonlyforqueuemanagerscreatedbefore youmigrated toV5.3.

v _{Replacetheamqzfumodulefoundin/opt/mqm/libbythepreviousversion.For} example,youcandothisby:

1. Removing theexistingamqzfumodule

Notes:

1. Youcanrestorethenewamqzfumodulefromthecopy providedasamqzfu1. 2. Once youhavecreatedorrestartedaqueuemanagerwith thenew amqzfu

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

Youcanviewauthorizationdatawiththedspmqautand dmpmqautcommands. Refer totheWebSphereMQSystemAdministrationGuideforacompletedescription of thesecommands.

Setting

the

queue

manager

CCSID

Thecoded charactersetidentifier(CCSID)isfixed whenyoucreatea queue manager.TheCCSIDisdeterminedbythelocalethatyouusetorunthecrtmqm

command. FormoreinformationonusingcommandsetsseetheWebSphereMQ SystemAdministrationGuide

Thefollowingtable givessomeexamplesof usingtheLANGparametertochange thecodeset andCCSIDonSolaris8.

Table2.ExamplesofsettingtheCCSID

Example Codeset CCSID

export LANG=en_US.ISO8859-1 ISO8859-1 819 export LANG=pl_PL.ISO8859-2 ISO8859-2 912

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

2. Display theexistingqueuemanagerCCSID, usingtheMQSCcommand:

display qmgr ccsid

3. ChangetheCCSIDtothenew CCSIDwith theMQSCcommand:

alter qmgr ccsid (new.ccsid)

wherenew.ccsid isthenumberofthenew CCSID.

4. StopMQSCcommandsbytyping: end

5. Stopthequeuemanager,and thenrestart itandanychannelsthatituses. See Chapter10,“CodesetssupportedonWebSphereMQforSolaris,”onpage41 forfurtherinformationaboutsupportedcode sets.See“Migrationtoeurosupport” onpage46forinformationonmigratingtoaCCSIDthatsupportstheeuro

character.

User

exits

Check thatyouruser exitsarelinkedwith threadedlibrariesbefore usingthemon this versionoftheproduct.

v _{Forfurtherdetailsonthreaded libraries,and informationaboutdata-conversion} exits,seetheWebSphereMQApplicationProgrammingGuide.

v _{Forinformationaboutchannelexits,seetheWebSphereMQIntercommunication} book.

v _{Forinformationaboutcluster-workloadexits,seetheWebSphere MQQueue}

ManagerClustersbook.

Migration

Chapter

4.

Verifying

the

server

installation

Thischapterdescribeshowto verifythattheWebSphereMQforSolarisserverhas been correctlyinstalledand configured.YoucanverifyaWebSphereMQserver installationat differentlevels:

v _{Alocal(stand-alone) installationthathasnocommunicationlinkswithother} WebSphereMQinstallations.Thisisdescribedin“Verifyinga localinstallation.” v _{Aserver-to-serverinstallationthatincludescommunicationlinksto other}

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

See Chapter6,“Verifyingtheclientinstallation,”onpage29ifyouhavea 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 page12 for howto correctthis.

3. EnableMQSC commandsbytyping:runmqsc

Amessagetellsyouthatan MQSCsessionhasstarted.MQSChasnocommand prompt.

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

Amessagetellsyouwhenthequeuehasbeencreated. 5. StopMQSCbytyping: end

Youwillseesomemessages,followedbythecommandprompt. Youhavenowdefined:

v _{Adefaultqueuemanager calledvenus.queue.manager} v _{AqueuecalledORANGE.QUEUE}

Testing

the

installation

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

1. Changeintothe/opt/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.WebSphereMQforSolarissupportsbothTCP and SNA.Thisexampleexplainshow toverifyyourinstallationif youareusing TCP;ifyouareusingSNA,refertotheWebSphereMQIntercommunicationmanual. Totest theinstallation,set uptwoworkstations,oneasasender andoneasa receiver.Youtestcommunicationsbetweensender andreceiverusingsample programs,whichyoumustinstall onbothworkstations.Theverification procedure assumesthatbothworkstationsare UNIXmachines;ifthis isnotthecase,someof thecommandsaredifferent(fordetails, refertothedocumentationforthe

workstation).

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

Amessagetellsyouwhenthequeuemanagerhasstarted.

Thefirst timethatyoustarta queuemanager onamachine,youmightgetone of the following warnings: Purchased license units not set (use setmqcap) or Insufficientlicense units.See “Installation procedure”on page12 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 _{Adefaultqueuemanagercalled saturn.queue.manager} v _{AtransmissionqueuecalledTRANSMIT1.QUEUE}

v _{Alocaldefinitionofa remotequeuecalledLOCAL.DEF.OF.REMOTE.QUEUE} v _{Asender channelcalledFIRST.CHANNEL}

Verifying

a

server-to-server

installation

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

Amessagetellsyouwhenthequeuemanagerhasstarted.

Thefirst timethatyoustarta queuemanager onamachine,youmightgetone of the following warnings: Purchased license units not set (use setmqcap) or Insufficientlicense units. See“Installation procedure” onpage12 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 _{Adefaultqueuemanager calledvenus.queue.manager} v _{AqueuecalledORANGE.QUEUE}

v _{AreceiverchannelcalledFIRST.CHANNEL}

Testing

communication

between

the

workstations

Finally,usetheamqsputsampleprogramtoputamessagefromthesender workstationtoa queueat thereceiver,andtheamqsgetsampleprogramonthe receiverworkstationtogetthemessagefromthequeue:

1. Ifthequeuemanagersonthetwoworkstationshavestopped, restartthemnow bytyping: strmqm

2. On thesenderworkstation,start thesenderchannelasabackgroundtaskby enteringthefollowingcommand:

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

Thereceiverchannelonthereceiverworkstationstartsautomaticallywhenthe sender channelstarts.

3. On thesenderworkstation,change intothe/opt/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/opt/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

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”onpage23.

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”onpage18)

Toensurethatbothmachinesarepart ofthesame cluster,youcandoeitherof the following:

v _{RuntheJMSPostcardapplication forthefirst timeoneachmachine.TheJMS}

Postcardapplicationdetectsthattherearenolocalqueuemanagersdefinedfor thatmachine,anddisplaystheDefaultConfigurationwizardsothatyoucan createthedefaultqueuemanagersandlinkthemtothedefaultcluster.

v _{Createyourownqueuemanagersonbothmachines,createacluster,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”onpage25.

Setting

up

your

system

to

run

the

JMS

Postcard

Before youcanruntheJMSPostcardapplication, youmust ensurethat:

v _{Youare amemberoftheWebSphereMQadministratorsgroup(mqm).Ifyouare} nota memberofmqm,ask someonewhoisamembertoruntheDefault

Configurationtoolonyourbehalf,eitherdirectly,orbyrunningtheJMS Postcardapplication,whichrunstheDefault Configurationtoolindirectly.

v _{AsupportedJavaVirtualMachine isinstalledonyoursystem andsuitably} configuredinthesystempathsothatthejavacommandcanbe executed. v _{Therequiredenvironmentvariablesaredefined.}

Definetheenvironmentvariablesasfollows: 1. Logonasuser mqm.

2. Addtherequiredenvironmentvariablestothe.profilefileusinga texteditor. Theseareshowninthefollowingtable:

CLASSPATH /opt/mqm/java/lib/com.ibm.mq.jar: /opt/mqm/java/lib/com.ibm.mqjms.jar: /opt/mqm/java/lib/connector.jar: /opt/mqm/java/lib/jms.jar: /opt/mqm/java/lib/jndi.jar: /opt/mqm/java/lib/jta.jar: /opt/mqm/java MQ_JAVA_INSTALL_PATH /opt/mqm/java MQ_JAVA_DATA_PATH /var/mqm LD_LIBRARY_PATH /opt/mqm/java/lib PATH(forJREsettings) $PATH:/opt/java1.3/bin

Using

the

JMS

Postcard

application

to

verify

a

local

installation

Note: Aqueuemanager thatcanbeusedasa mailboxmust bealreadysetup. Thisqueuemanager canbe eitherthedefaultqueuemanager,whichisset upautomaticallywhenyouruntheDefault Configurationwizard,or anotherqueuemanagerthatyouhaveset upyourself.

Toverify thatthelocalinstallationisworking,youcanusetheJMSPostcard

application. Thisapplication allowsyoutocreatetwopostcardsonthesame machine andsendmessages betweenthem,verifyingthatWebSphereMQ messaging isworking correctlyonthemachine,andthatWebSphereMQJava Messaging supportissuccessfullyinstalled.

Note: IfyouwanttheJMSPostcardapplicationtousefontandcolorsettings differentfromtheJava VirtualMachinedefaults,changethePostcard.inifile. FormoreinformationseeWebSphereMQUsingJava.

1. Changedirectory to/opt/mqm/java/bin 2. RunthePostcardshellscript.

Iftherearenoqueuemanagersonyour machine,theIncompleteDefault Configuration windowisdisplayed.FromhereyoucaneitherruntheDefault ConfigurationwizardtocreateaqueuemanagertousewiththeJMSPostcard

application, oryoucanclosetheapplication. 3. TheJMSPostcard -SignOnwindowisdisplayed.

Type inanicknametousetosend messageswithin thepostcard application (forexample,user1).

Iftheonlyqueuemanager onyourmachineisthedefaultqueuemanagerthat youcreatedbyrunningtheDefaultConfigurationwizard,this queuemanager isusedasyourmailboxforpostcards.ClickOKtodisplayyour firstpostcard, then gotostep 5.

4. Select thequeuemanagertouseasthemailbox:

Verifying

a

server-to-server

installation

v _{Ifyouhavecreatedoneormoreof yourownqueuemanagers,but you} havenotruntheDefault Configurationwizard,selecttheappropriatequeue managerfromthelistdisplayed.

v _{IfyouhaveruntheDefault Configurationwizardandyouwanttousethe} defaultqueuemanager,but thereismorethanonequeuemanageronyour machine,selecttheAdvancedcheckbox,then selectUseDefault

Configurationasmailbox.

v _{IfyouhaveruntheDefault Configurationwizardandalso createdoneor} moreofyourown queuemanagers,andyoudonotwanttousethedefault queuemanager,selecttheAdvancedcheckbox,selectChoosequeue

managerasmailbox,then selecttheappropriatequeuemanagerfromthe listdisplayed.

Whenyourselectioniscomplete,click OKtodisplayyourfirst postcard window.

5. RunthePostcardshellscriptagain.Thisopensa secondpostcardwindow. 6. The JMSPostcard -SignOnpanelisdisplayedagain. Typeinasecond

nicknametousetosendmessageswithin thePostcardapplication(for example,user2).

7. Repeattheselectionofthequeuemanager thatyouwanttouseasthe mailbox(asdescribedearlier).Thequeuemanageryouselectforthis second postcard musteitherbe inthesameclusterasthequeuemanager forthefirst postcard, orcommunicationlinksmust havebeen setupbetweenthem. 8. Younow havetwopostcards,onewith thenicknameuser1 andonewiththe

nicknameuser2.

9. Inoneofthepostcards(forexample,user1),typesomemessagetextinthe

Message:fieldand thenicknameoftheotherpostcard(forexample,user2)in theTo: field.

Note: Becausethesenderandreceiverareonthesamemachine,youdonot needtotype anythingintheOn:field.

Ifthereceiverisonadifferentmachine,andisusingthedefaultqueue managerasthemailbox,youneedtotypetherecipient’smachine in theOn:field.

Ifthereceiverisonadifferentmachine,andisnotusingthedefault queuemanagerasthemailbox,youneed totypetherecipient’squeue managerintheOn:field.

10. Click Send.

11. ThePostcardssentandreceived areaof thepostcard showsdetailsofthe message.Inthesendingpostcard,themessageisdisplayedassent.Inthe receivingpostcard,themessageisdisplayedasreceived.

12. From thereceivingpostcard,double-click themessageinthePostcardssent andreceived areatoview it.

Ifyoucompletethisproceduresuccessfully,itverifiesthatWebSphereMQis working correctly,andthattheWebSphereMQJavamessaging supportis successfullyinstalled.

Whatnext?

Depending onyour situation,youmight wanttodo thefollowing: v _{InstallWebSphereMQonothermachines.Followthesameinstallation}

procedurethatyouusedforthefirst machine.EnsurethatyouusetheJoin DefaultClusterwindow intheDefault Configurationwizardtoaddthe othermachinestoyourfirst machine’scluster.

v _{InstalltheWebSphereMQclientonothermachines.SeetheChapter5,} “InstallingtheWebSphereMQforSolarisclient,” onpage27.

v _{Continuewith furtheradministrationtasks.SeetheWebSphereMQSystem}

AdministrationGuide.

Using

the

Postcard

application

to

verify

a

server-to-server

installation

YoucanusetheJMSPostcardapplication toverifycommunicationbetweenyour machine andthemachineofanothernameduser,wherethatmachineusesTCP/IP. Therefore,youcanusethePostcardapplicationstoverifythatyoucan

communicatewithanotherserver.Beforeyoustart:

v _{MakesurethatTCP/IPandWebSphereMQare installedonbothmachines.} v _{Checkthateitherofthefollowingapply:}

– Bothmachinesareinthesamecluster(this isthesimplestmethod)

– Youhaveconfiguredchannelstocommunicatebetweenthetwomachines(see “Verifyinga server-to-serverinstallation”onpage18).

Toverify thatthecommunicationbetweentwomachines, thesenderof themessage and thereceiver, areworkingcorrectly,andthattheWebSphereMQJavamessaging support issuccessfullyinstalled,youcanusetheJMSPostcardapplication.

Onthesendermachine:

1. Changedirectoryto/opt/mqm/java/bin 2. RunthePostcardshellscript.

Iftherearenoqueuemanagersonyour machine,theIncomplete Default Configurationwindow isdisplayed.From hereyoucaneitherruntheDefault Configurationwizardtocreatea queuemanagertousewith theJMSPostcard

application,oryoucanclosetheapplication. 3. TheJMSPostcard-SignOnwindow isdisplayed.

Typeina nicknametousetosendmessages withinthePostcardapplication (forexample,user1).

Iftheonlyqueuemanageronyour machineisthedefaultqueuemanager that youcreatedbyrunningtheDefaultConfigurationwizard,thisqueuemanager isusedasyour mailboxforpostcards. ClickOKtodisplayyour postcard,then go tostep5.

4. Selectthequeuemanagertouseasthemailbox:

v _{Ifyouhavecreatedoneormoreofyour ownqueuemanagers,butyouhave} notruntheDefault Configurationwizard, selecttheappropriatequeue manager fromthelistdisplayed.

Verification

—

local

installation

v _{IfyouhaveruntheDefaultConfigurationwizardandyouwanttousethe} defaultqueuemanager,butthereismore thanonequeuemanageronyour machine,selecttheAdvancedcheckbox,then selectUseDefault

Configuration asmailbox.

v _{IfyouhaveruntheDefaultConfigurationwizardandalsocreatedoneor} more ofyourownqueuemanagers, andyoudo notwanttousethedefault queuemanager,selecttheAdvancedcheckbox, selectChoosequeue

managerasmailbox,thenselecttheappropriatequeuemanagerfromthelist displayed.

Whenyourselectioniscomplete,clickOKtodisplayyour postcard. 5. Typein thefollowing:

v _{Some messagetextintheMessage:field.} v _{ThenicknameoftherecipientintheTo:field.}

v _{Ifthereceiverisusingthedefaultqueuemanagerasthemailbox, the}

machine nameoftherecipientintheOn:field.Ifthereceiverisnotusingthe defaultqueuemanager,typethequeuemanagernameintheOn:field. 6. ClickSend.

Onthereceivermachine:

1. Toreceivethemessage,runthePostcardshellscript.

Iftherearenoqueuemanagersonyour machine,theIncomplete Default Configurationwindow isdisplayed.From hereyoucaneitherruntheDefault Configurationwizardtocreatea queuemanagertousewith theJMSPostcard

application,oryoucanclosetheapplication.

2. Typein thenicknameoftherecipient,selectthequeuemanager touseasthe mailbox,then clickOKtodisplaytheJMSPostcardwindow.

3. InthePostcardssent andreceived areaofthepostcard, detailsofthenew messagearedisplayed. Themessageisdisplayed asreceived.

Whenthismessagearrives,this verifiesthatWebSphereMQandtheJava messagingsupport arecorrectlyinstalledandthatyourcommunicationlink betweenthetwomachinesisworkingcorrectly.

Whenallinstallationand verificationiscomplete,youarereadytostartusing WebSphereMQ(seetheWebSphereMQSystemAdministrationGuide).