Using The WebSphere MQ Driver - Oracle

2y ago
23 Views
2 Downloads
602.11 KB
59 Pages
Last View : 1m ago
Last Download : 3m ago
Upload by : Eli Jorgenson
Transcription

Using the WebSphere MQDriverV4.2Document ID: TMGN-16-4.2-01Date Published: 3.5.04

1997 2004 edocs Inc. All rights reserved.edocs, Inc., One Apple Hill Dr., Natick, MA 01760The information contained in this document is the confidential and proprietary information ofedocs, Inc. and is subject to change without notice.This material is protected by U.S. and international copyright laws. edocs and eaPost areregistered in the U.S. Patent and Trademark Office.No part of this publication may be reproduced or transmitted in any form or by any meanswithout the prior written permission of edocs, Inc.eaSuite, eaDirect, eaPay, eaCare, eaAssist, eaMarket, and eaXchange are trademarks of edocs,Inc.All other trademark, company, and product names used herein are trademarks of their respectivecompanies.Printed in the USA.

PrefaceIn This SectionUsing this Manual . ivFinding the Information You Need . ixIf You Need Help . xii

ivUsing the WebSphere MQ DriverUsing this ManualWelcome to Using the WebSphere MQ Driver for Telco Service & Analytics Manager.This manual covers using the WebSphere MQ Driver in Connectors.

PrefaceBefore You Get StartedYou should be familiar with the following:!Your application architecture!Programming in Java!Designing or working with databases!eXtended Markup Language (XML)!Your OSSv

viUsing the WebSphere MQ DriverWho Should Read this ManualThis manual is for developers and project managers who are responsible for configuringand developing connectors which use the IBM WebSphere MQ driver.However, there are other topics covered in this manual that may interest othermembers of the project development team.!AdministratorsYou will find information about running and managing connectors using this driver.!DevelopersYou will find everything you need to know in order to build, generate and runconnectors using this driver. This manual contains instructions on how to use theIntegration Logic Studio you use the driver in connectors. It also shows you how togenerate the runtime files then launch the connector.!Project ArchitectYou can use the information in this manual to learn about connectors and how theyuse this driver.!Project ManagerYou will find information about connectors and the different tools used to create andrun them. You will find information about how your solution uses connectors and thisdriver.

PrefaceviiHow this Manual is OrganizedThis manual contains the following chapters:!About WebSphere MQ and the SmartLink (ISF)This chapter introduces the IBM WebSphere MQ driver and its role in the SmartLink(ISF).It contains information about:!!SmartLink (ISF)!SmartLink (ISF) Connectors!This driver and the SmartLink (ISF) ConnectorsInstalling the WebSphere MQ DriverThis chapter covers the installation of the driver.It contains information about:!!Required software!Installing this driverConfiguring Your ConnectorThis chapter covers the configuration the Connector to use the driver.It contains information about:!!Installing the ILS driver plugin!Configuring the connector to use this driverGenerating Your ConnectorThis chapter covers generating the runtime files of your connector.It contains information about:!!Using the ILS to generate the runtime files!Using the command line tool to generate runtime filesRunning Your ConnectorThis chapter covers running the connector.It contains information about:!Starting and stopping connectors

viiiUsing the WebSphere MQ Driver!!Administrating connectorsTool ReferenceThis appendix is a tool reference guide. It covers the location, configuration and useof the administration tools.The administration tools covered include:!Synchronizer connector tools!OSS connector tools!Connector Generator

PrefaceWhat Typographical Changes and Symbols MeanThis manual uses the following conventions:TYPEFACEMEANINGEXAMPLEItalicsManuals, topics or otherimportant itemsRefer to DevelopingConnectors.Small CapitalsSoftware and ComponentnamesYour application uses adatabase called the CID.File names, commands,paths, and on screencommandsGo to //home/my fileFixed Widthix

xUsing the WebSphere MQ DriverObtaining edocs Software and DocumentationYou can download edocs software and documentation directly from Customer Centralat https://support.edocs.com. After you log in, click on the Downloads button on the left.When the next page appears, you will see a table displaying all of the availabledownloads. To search for specific items, select the Version and/or Category and clickthe Search Downloads button. If you download software, an email from edocs TechnicalSupport will automatically be sent to you (the registered owner) with your license keyinformation.If you received an edocs product installation CD, load it on your system and navigatefrom its root directory to the folder where the software installer resides for youroperating system. You can run the installer from that location, or you can copy it to yourfile system and run it from there. The product documentation included with your CD is inthe Documentation folder located in the root directory. The license key information forthe products on the CD is included with the package materials shipped with the CD.

PrefacexiFinding the Information You NeedThis driver is an integral part of solutions based on Telco Service & Analytics Manager.If you are new to using drivers and working with the SmartLink (ISF), you should startby reading Building Connectors. This manual helps you understand the integrationarchitecture and shows you how to build connectors to connect to today’s marketleading OSS software. You can also read Using the Loopback Connector forinformation about a connector built for development purposes.You should always read the release bulletin for late-breaking information.You should refer to the documentation set which came with your version of TelcoService & Analytics Manager for more detailed information.

xiiUsing the WebSphere MQ DriverIf You Need HelpTechnical support is available to customers who have valid maintenance and supportcontracts with edocs. Technical support engineers can help you install, configure, andmaintain your edocs application.edocs provides global Technical Support services from the following Support Centers:US Support CenterNatick, MAMon-Fri 8:30am – 8:00pm US ESTTelephone: 508-652-8400Europe Support CenterLondon, United KingdomMon-Fri 9:00am – 5:00 GMTTelephone: 44 20 8956 2673Asia Pac Rim Support CenterMelbourne, AustraliaMon-Fri 9:00am – 5:00pm AUTelephone: 61 3 9909 7301Customer Centralhttps://support.edocs.comEmail Supportmailto:support@edocs.comWhen you report a problem, please be prepared to provide us the following information:!What is your name and role in your organization?!What is your company’s name?!What is your phone number and best times to call you?!What is your e-mail address?!In which edocs product did a problem occur?!What is your Operating System version?!What were you doing when the problem occurred?!How did the system respond to the error?!If the system generated a screen message, please send us that screen message.!If the system wrote information to a log file, please send us that log file.

PrefaceIf the system crashed or hung, please tell us.xiii

ContentsPrefaceiiiAbout WebSphere MQ and the SmartLink (ISF)17Overview of the SmartLink (ISF) ConnectorsAbout the SmartLinkUsing the IBM WebSphere MQ DriverInstalling the WebSphere MQ DriverBefore You InstallInstalling the WebSphere MQ DriverConfiguring Your ConnectorAbout Configuring ConnectorsInstalling the Integration Logic Studio Add-inConfiguring the Connector to use WebSphere MQProgramming User ExitsThe MQCustomIF InterfaceSetting Environment VariablesGenerating Your ConnectorAbout Generating Your ConnectorRunning Your ConnectorStarting and Stopping the Synchronizer ConnectorAbout Synchronizer Run ModesStarting and Stopping the OSS ConnectorAdministrating the ConnectorAbout Administrating ConnectorsTool ReferenceSynchronizer Connector Administration Toolsagentstart Syntaxagentadm SyntaxOSS Connector Administration Toolsossstart Syntaxossadm SyntaxConnector Generator ToolilccGenerator 5252535656565757

xviUsing the WebSphere MQ DriverIndex59

CHAPTER 1About WebSphere MQ and theSmartLink (ISF)SmartLink (ISF) drivers are communication drivers for Telco Service Manager (TSM).This driver is for Telco Service Manager (TSM) that communicate with OSS using IBM'sWebSphere MQ middleware.In This SectionOverview of the SmartLink (ISF) Connectors . 18About the SmartLink (ISF) . 20Using the IBM WebSphere MQ Driver. 21

18Using the WebSphere MQ DriverOverview of the SmartLink (ISF)ConnectorsThe SmartLink (ISF) is not only a set of application integration services, but is aframework in which the providers of the services work together.In order to integrate an application, these service providers, or SmartLink (ISF)components, are arranged into dataflows. This means that they are connected togetherand organized into a step-by-step sequence. A connector is part of the SmartLink (ISF)that is responsible for moving data between applications and transport layers.There are two types of connectors:!SynchronizersThey are responsible for data exchanged between your Telco Service Manager(TSM) and the transport layer!OSS ConnectorsThey are responsible for data exchanged between the BSS/OSS applications andthe transport layerFor example, the Synchronizer connector is responsible for moving data between theTelco Service Manager (TSM) and the transport layer. This connector uses differentconnector components to carry out the following tasks:!Send data to the middleware1. Extract the requests from the request queue located in the CID2. Use these requests to generate XML messages3. Send this XML message to the middleware backbone

About WebSphere MQ and the SmartLink (ISF)!Receive data from the middleware4. Receive the XML message from the middleware5. Use these messages to create CID objects6. Update the CID by running scripts which use the CID objects19

20About the SmartLinkThe SmartLink (ISF) enables the Telco Service Manager (TSM) to communicate, orintegrate with the core CSP technology infrastructure, for example billing platforms,Customer Relationship Management (CRM) software, and other business andoperational support systems (BSS/OSS). This in turn allows the CID to maintain asynchronized cache of semi-static customer and service data, as well as passingrequests and responses between the various systems.The SmartLink (ISF) can be considered to comprise:!Connectors that move data between Telco Service Manager (TSM) and thetransport layer. These connectors are called Synchronizers.!Connectors that move data between BSS/OSS applications and the transport layer.These connectors are called BSS/OSS Connectors.!A repository of message definitions to build and process messages for all commontransactions. This is the Message Schema Reference Repository.!Associated tools to design and configure Connectors along with administration toolsto run and manage them.

About WebSphere MQ and the SmartLink (ISF)21Using the IBM WebSphere MQ DriverConnectors are responsible for moving data between applications and transport layers.This driver allows your connectors to use WebSphere MQ to exchange messages.Before you get started, you must create and configure the WebSphere MQ MessageQueues. You use the WebSphere MQ tools to create the queue manager and queuesfor your connector. When you are finished, you are ready to begin using the driver.Using this driver involves:!Installing the ConnectorYou install the required runtime files so the connector can communicate withWebSphere MQ.!Configuring the Integration Logic StudioYou use the WebSphere MQ add-in to import the inbound and outboundWebSphere MQ message queues.!Configure your Connector to use these queuesUsing the Integration Logic Studio, you modify Integration Processes to use thequeues. Depending on the type of connector, your Integration Process may use theinbound queue to receive messages or the outbound queue to send messages.!Generating and Running the ConnectorYou then have to configure the queues for your environment. Once you configureyour connectors to use these queues, you generate the connector runtime files. Youcan then run the connector.For more information about Connectors and using the Integration Logic Studio, refer toDeveloping Connectors

CHAPTER 2Installing the WebSphere MQDriverIn This SectionBefore You Install . 24Installing the WebSphere MQ Driver . 25

24Before You InstallBefore you install this driver, you must install at least one of the following:!Telco Service & Analytics Manager 4.2 Framework including the Integration LogicStudio!Telco Service & Analytics Manager 4.2 Loopback Connector!Telco Service & Analytics Manager 4.2 Connector Template

25Installing the WebSphere MQ DriverInsert the Telco Service & Analytics Manager WebSphere MQ Driver CD-ROM andopen Contents.html. This page contains a link to the installer page. On the installerpage, click the link to the driver to run the installer.If you install the WebSphere MQ Driver on a computer running Windows2000, you mustuse the Windows Install/Remove Programs utility to run the installer you download. Youcan find this utility in the Control Panel. Go to Start Settings Control Panel.To install the WebSphere MQ driver1Run the installer application for your platform that you downloaded from edocsCustomer Central or that is on the Telco Service & Analytics Manager CD-ROM.The Installer appears.!AIX: wsmq aix.bin!HPUX: wsmq hpux.bin!Solaris: wsmq solaris.bin!Windows: wsmq windows.exe2 Click Next. The License Agreement window appears.3 Read and accept the license agreement then click Next. The Location windowappears4 Select the component to install:!ISF Driver to install the driver runtime files.!Integration Logic Studio Add-in to install the add-in.!Full Installation to install all of the components.5 Follow the onscreen instructions to enter the different paths of installed software.Depending on your installation type, you may have to enter:!The home directory of Telco Service Manager!The home directory of the Telco Service Manager Composer!The location of the WebSphere MQ Client6 Click Next. The Pre-Installation Summary window appears. Review the installationinformation. If necessary, you can click Previous to modify the installationconfiguration.7 Click Install to install the driver.When finished, the installer displays a confirmation message.

CHAPTER 3Configuring Your ConnectorIn This SectionAbout Configuring Connectors. 28Installing the Integration Logic Studio Add-in . 29Configuring the Connector to use WebSphere MQ . 30Programming User Exits . 34Setting Environment Variables . 38

28About Configuring ConnectorsAfter you install the WebSphere MQ driver, you have configure your environment to usethe driver.Configuring your environment involves:!Installing the WebSphere MQ Addin!Configuring the connectors to use the queues!Configuring User Exits!Setting environment variables

Configuring Your Connector29Installing the Integration LogicStudio Add-inIn order for your connectors to use the WebSphere MQ driver, you need to install theaddin for the ILS.This addin installs the following:!Inbound MQSeries QueueThis queue is for inbound messages coming from WebSphere MQ!Outbound MQSeries QueueThis queue is for outbound messages going to WebSphere MQTo install add-ins1Run the ILS2 Select Tools Addins. The directory selection dialog box appears.3 Select the location of the addin install files.By default, the WebSphere MQ install files are in ils home /addins/ils/mqseries4 Select OK. The ILS imports the addin. When finished, the ILS displays a message.5 Restart the ILS.

30Using the WebSphere MQ DriverConfiguring the Connector to useWebSphere MQAfter installing the WebSphere MQ addin, you can open and configure your connectorto use the WebSphere MQ queues.Configuring the connector involves:!Opening the connector and Integration Processes to modify!Create the Message Queue processors!Configure the Message Queue processors!Connect the Message Queue processors!Validate the connectorTo open connectors1Choose File Open. The Open Connector dialog box opens.2 Select the connector file to open.3 Choose Open. The connector opens in the Connector Explorer.To open Integration Processes1Open the connector.2 In the Connector Explorer, expand Integration Processes.3 Double-click the Integration Process. The Integration Process appears in theWorkspace.To create the queues1Open the Integration Process.2 Right-click Processors then select New Processor. The Choose a Processor Typedialog box appears.3 Expand the Message Queue node.4 Select one of the following:!Inbound MQSeries Queue!Outbound MQSeries Queue

Configuring Your Connector315 Enter the name of the Processor.6 Select Confirm. The new processor appears in the Connector Explorer and theIntegration Process displayed in the Workspace.To specify the properties of outbound queues1Open the Integration Process.2 Expand the Processors node.3 Select the Inbound MQ Series Processor to modify.4 In the Properties pane, enter the following:PROPERTYDESCRIPTIONQueue Manager NameThe queue manager nameQueue NameThe queue nameHost NameThe host namePort NumberThe host port numberChannel NameThe channel nameUser NameUser name to connect to WebSphere MQUser PasswordAssociated passwordNapping timeTime between polling (in milliseconds)User ExitsClass containing user exit code to executeNumber of threadsNumber of threads to allocateJava priorityJVM priority of the threadsTime To LiveOptional parameterInteger containing the lifespan of the message in thequeue (tenths of seconds)This value corresponds to the EXPIRY property of theMQSeries message.1Add MQ Options as required.1. Select Options node under the WebSphere MQ Outbound Message Queue. Theproperties appear in the Properties pane. The Add button on the Properties paneis active.2. Choose Add to add a new property. A new row is created in the Properties pane.3. In the new row, enter the name of the MQ Option.

32Using the WebSphere MQ DriverFor instance, for outbound queues, you can add the following options:!MQOO OUTPUT!MQOO SET IDENTITY CONTEXT!MQOO BIND NOT FIXEDFor more information about the available MQ Options, refer to your WebSphere MQdocumentation.To specify the properties of inbound queues1Open the Integration Process.2 Expand the Processors node.3 Select the Outbound MQSeries Queue Processor to modify.4 In the Properties pane, enter the following:PROPERTYDESCRIPTIONQueue Manager NameThe queue manager nameQueue NameThe queue nameHost NameThe host namePort NumberThe host port numberChannel NameThe channel nameUser NameUser name to connect to WebSphere MQUser PasswordAssociated passwordTime To LiveOptional parameterInteger containing the lifespan of the message in thequeue (tenths of seconds)This value corresponds to the EXPIRY property of theMQSeries message.User Exits1Class containing user exit code to executeAdd MQ Options as required.1. Select Options node under the WebSphere MQ Inbound Message Queue. Theproperties appear in the Properties pane. The Add button on the Properties paneis active.2. Choose Add to add a new property. A new row is created in the Properties pane.3. In the new row, enter the name of the MQ Option.For instance, for inbound queues, you can add the following options:!MQOO OUTPUT

Configuring Your Connector!MQOO SET IDENTITY CONTEXT!MQOO INPUT AS Q DEF33For more information about the available MQ Options, refer to your WebSphere MQdocumentation.To connect the queues1Open the Integration Process in the Workspace.2 Find the Processor you want to connect.3 Click the Processor then drag the pointer to the destination Processor. Dependingon the type of destination Processor, the following may occur:!An arrow appears connecting the two Processors.!A menu appears asking you to select the type of connection.!A dialog box appears informing you that you cannot connect the Processors.To save connectors1Do one of the following:!Choose File Save to save the connector.!Choose File Save As to save the connector with a different name.To validate connectorsChoose Connector Check connector. The ILS validates the connector.After verification, the ILS displays the result in the message pane. If your connector isinvalid or if a problem occured during verification, the ILS displays messages to helpyou resolve the problem.

34Using the WebSphere MQ DriverProgramming User ExitsIf you need to customize the processing of messages in the WebSphere MQ inboundand outbound queue processors, you can specify a User Exit. A User Exit is a call tocustom methods to process messages in a queue.If your solution requires specific processing of messages before getting or sendingmessages using WebSphere MQ, you can use the MQCustomIF User Exit class thatcomes with this driver.Programming User Exits involves:!Implementing the custom User Exit class!Specifying the User Exit classTo implement the default User Exit classThe WebSphere MQ driver comes with class for programming user exits. This class isMQCustomIF and is located in the drv mqseries.jar file. This file contains thefollowing methods:!beforePutThe code in this method is executed before the the Put API.!afterPutThe code in this method is executed after calling the Put API.!beforeGetThe code in this method is executed before calling the Get API.!afterGetThe code in this method is executed after calling the Get API.To create your User Exit class, implement this class in your class containing the customcode to run before and after calling WebSphere MQ PUT and GET API.

Configuring Your ConnectorThe MQCustomIF Interface35

36Using the WebSphere MQ Driver/** Determines the requirements for a WebSphere MQ Driver User Exit.* p * This interface has a set of methods to execute before and after calling MQSeries PUT and GET API*/public interface MQCustomIF {/*** Contains the code to run before calling the PUT API.* @param eaiMsg the ISF EAI message* @param queue the MQ queue* @param mmsg the MQ message* @param pmo MQ message options* @throws Exception if an error occurs*/void beforePut(EaiMessage eaiMsg, MQQueue queue,MQMessage mmsg, MQPutMessageOptions pmo) throws Exception;/*** Contains the code to run after calling the PUT API.* @param eaiMsg the ISF EAI message* @param mmsg the MQ message* @throws Exception if an error occurs*/void afterPut(EaiMessage eaiMsg, MQMessage mmsg) throws Exception;/*** Contains the code to run before calling the GET API.* @param mmsg the the MQ message* @param queue the MQ queue* @param gmo MQ message options* @throws Exception if an error occurs*/void beforeGet(MQMessage mmsg, MQQueue queue, MQGetMessageOptions gmo) throws Exception;/*** Contains the code to run after calling the GET API.* @param eaiMsg the ISF EAI message* @param mmsg the MQ message* @throws Exception if an error occurs*/void afterGet(EaiMessage eaiMsg,}MQMessage mmsg) throws Exception;

Configuring Your ConnectorTo specify the User Exit class1Open the Integration Process.2 Expand the Processors node.3 Select the MQ Series Queue Processor to modify.4 In the Properties pane, enter the following:1PROPERTYDESCRIPTIONUser ExitsClass containing user exit code to executeSave your changes.37

38Setting Environment VariablesDepending on your system and environment, you may need to modify or set somededicated environment variables.The values for this driver are declared in the mqseries.env environment setting file.This file is located in:! home dir /bin/env.cmd/isf for Windows! home dir /bin/env.cmd/isf for UNIXThe default values of these variables comes from the values you entered duringinstallation.For more information about .env environment setting files and how they work, refer toConfiguring Environment Variables in Installing Telco Service Manager (TSM).

CHAPTER 4Generating Your ConnectorIn This SectionAbout Generating Your Connector . 40To generate connectors. 41To generate connectors using the Connector Generator . 42

40Using the WebSphere MQ DriverAbout Generating Your ConnectorThe ILS uses the Integration Logic Connector Design file ( connector name .ilcd)to store the design and configuration of your connector. This file is for configuring anddesigning connectors. In order to run your connector, you need to generate the runtimefiles.The generated connector runtime files are:!Integration Logic Connector Configuration file ( connector name .ilcc)This file is an internal configuration file used by the connector. It contains theconfiguration of your connector.This file is automatically generated and should not be edited. Use the ILS to changeyour configuration.

Generating Your Connector41Integration Logic Connector run time configuration file template( connector name .ilcr.template)!This run time configuration file contains the parameters defined for your connector.You edit this file manually and change its name.The Generation process is as follows:ilcd Connector DesignfileGeneration(ILS or Connector Generator)Connector Configuration fileilccConnector ParametersTemplate fileilcr.templateManually editparameters(if required)Rename thefile to ilcrRun the connectorTo generate the runtime files, you can:!Use the ILS!Use the Connector Generator command line toolTo generate connectors1Choose Connector Generate. The Generate Connector Configuration dialog boxappears.2 If you want the ILS to validate the connector before generation, select PerformValidation before Generation.

42Using the WebSphere MQ Driver3 In Output directory, enter the location of the generated connector files.4 Choose Generate. The ILS generates the following connector runtime files:! connector name .ilcc! connector name .ilcr.template5 When finished, the ILS displays a message in the message pane.6 If you need to change the runtime parameters before running your connector, open connector name .ilcr.template and edit the parameters.7 Change the file name to connector name .ilcr.To generate connectors using the Connector Generator1Go to ils dir /bin.2 Run the ilccGenerator tool. Use the syntax:ilccGenerator connector name where connector name is the full path of the Integration Logic ConnectorDesign .ilcd fileThe tool generates the the following runtime files in the same directory as theIntegration Logic Connector Design .ilcd file.! connector name .ilcc! connector name .ilcr.template3 If you need to change the runtime parameters before running your connector, open connector name .ilcr.template and edit the parameters.4 Change the file name to connector name .ilcr.

CHAPTER 5Running Your ConnectorIn This SectionStarting and Stopping the Synchronizer Connector. 44Starting and Stopping the OSS Connector . 46Administrating the Connector . 47

44Using the WebSphere MQ DriverStarting and Stopping theSynchronizer ConnectorYou use a set of administration tools to start and stop the Synchronizer connector. Theadministration tools are:!agentstart!agentadmThese administration tools are located in home dir /bin.About Synchronizer Run ModesThe Synchronizer connector works in one of the following modes:MODEDESCRIPTIONNORMALTHE DEFAULT MODE IN WHICH THE SYNCHRONIZERSCANS THE CID AT A REGULAR, FIXED TIME INTERVALSAND EXTRACTS THE REQUESTSPAUSEDTHE SYNCHRONIZER CONNECTOR STOPS SCANNING THECID FOR REQUESTS, AND WAITS FOR A RESTARTCOMMAND BEFORE IT RESUMESRECOVERTHE SYNCHRONIZER CONNECTOR MAKES A FINALATTEMPT TO SEND REQUESTS (WITH THE STATUS‘TRANSPORTFAILED’) THAT HAVE NOT BEEN SENT DUE TOA TRANSPORT PROBLEM. WHEN FINISHED, IT GOES BACKTO THE NORMAL MODE.To start the Synchronizer connector1Go to home dir /bin.2 Run agentstart. Use the syntax:agentstart connector name The connector is loaded and it starts the processes it needs.To stop the Synchronizer connector1Go to home dir /bin.2 Run agentadm. Use the syntax:

Running Your Connectoragentadm host port shutdownWhen finished, it displays a message.45

46Using the WebSphere MQ DriverStarting and Stopping the OSSConnectorYou use a set of administration tools to start and stop the OSS connector. Theadministration tools are:!ossstart!ossadmThese administration tools are located in home dir /bin.To start the OSS connector1Go to home dir /bin.2 Run ossstart. Use the syntax:ossstart connector name The connector is loaded and it starts the processes it needs.To stop the OSS connector1Go to home dir /bin.2 Run ossadm. Use the syntax:ossadm host port connector shutdownWhen finished, it displays a message.

Running Your Connector47Administrating the ConnectorYou can stop, start and manage the connector interactively.You use a set of administration tools to start, stop and manage the Synchronizer andOSS Connector.About Administrating ConnectorsTo administer the connectors, you have a complete set of commands you can use tostart, stop, or change the settings of the connector while it runs.Whenever you send a command, the connector responds confirming the execution ofyo

About WebSphere MQ and the SmartLink (ISF) 21 Using the IBM WebSphere MQ Driver Connectors are responsible for moving data between applications and transport layers. This driver allows your connectors to use WebSphere MQ to exchange messages. Before you get started, you must create and co

Related Documents:

May 02, 2018 · D. Program Evaluation ͟The organization has provided a description of the framework for how each program will be evaluated. The framework should include all the elements below: ͟The evaluation methods are cost-effective for the organization ͟Quantitative and qualitative data is being collected (at Basics tier, data collection must have begun)

Silat is a combative art of self-defense and survival rooted from Matay archipelago. It was traced at thé early of Langkasuka Kingdom (2nd century CE) till thé reign of Melaka (Malaysia) Sultanate era (13th century). Silat has now evolved to become part of social culture and tradition with thé appearance of a fine physical and spiritual .

On an exceptional basis, Member States may request UNESCO to provide thé candidates with access to thé platform so they can complète thé form by themselves. Thèse requests must be addressed to esd rize unesco. or by 15 A ril 2021 UNESCO will provide thé nomineewith accessto thé platform via their émail address.

̶The leading indicator of employee engagement is based on the quality of the relationship between employee and supervisor Empower your managers! ̶Help them understand the impact on the organization ̶Share important changes, plan options, tasks, and deadlines ̶Provide key messages and talking points ̶Prepare them to answer employee questions

Dr. Sunita Bharatwal** Dr. Pawan Garga*** Abstract Customer satisfaction is derived from thè functionalities and values, a product or Service can provide. The current study aims to segregate thè dimensions of ordine Service quality and gather insights on its impact on web shopping. The trends of purchases have

In the three volumes of the IBM WebSphere Portal V4.1 Handbook, we cover WebSphere Portal Enable and Extend. The IBM WebSphere Portal V4.1 Handbook will help you to understand the WebSphere Portal architecture, how to install and configure WebSphere Portal, how to administer portal pages using WebSphere Portal; it will also discuss the

Unit Objectives 2 This unit was designed to enable you to: Start a development project that implements WebSphere Commerce V7. Describe the Runtime architecture of WebSphere Commerce. Describe the development model for WebSphere Commerce. Explain the application of Struts in WebSphere Commerce. Describe the presentation layer for WebSphere Commerce by using both

WebSphere Application Server WebSphere MQ Use the most appropriate protocol C .net Java C JMS COBOL Java Jacl JMS Jython Web-Sockets C# HTTP WebSphere Application Server is a fully compliant Java Enterprise Edition (JEE) application server. The Java Message Service (JMS) is the JEE application messaging protocol. WebSphere MQ provides a fully