...
It uses message queues to exchange information and offers a single messaging solution for cloud, on premise, mobile and IoT environments.
To configure WebSphereMQ connection you have to fill following parameters:
- region - concrete Oracle SID of your region name
- transport type - usually it equals 1
- port - WebSphere port for client connections
- channel - WebSphere channel name
- queue manager - WebSphere Queue Manager name
- host name - address of WebSphereMQ
These are minimal required configuration parameters.
All optional parameters can be omitted (do not include them in config for just in case).
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
{
"Region": "Oracle SID of the region", /*Oracle SID of region name to which this config belongs*/
"Connections": [
{
"ConnectionName": "default.wmq.connection", /* connection name */
"ComponentName": "wmq", /* name of component */
"Parameters": {
"transportType": 1, /* sets the transport type */
"port": 1414, /* sets the port for a client connection */
"channel": "S_eglwwvm24c", /* sets the name of the channel - applies to client transport mode only */
"queueManager": "QM_eglwwvm24c", /* sets the name of the queue manager */
"HostName": "1.2.3.4" /* Sets the name of the host (or IP) */
, "ClientID": "enterprise" /* optional: sets the client ID */
, "CCSID": 1 /* optional: sets the character set to be used when connecting to the queue manager */
, "clientReconnectTimeout": 10 /* optional: set the amount of time, in seconds, that a client connection will attempt to reconnect */
},
"UseConnectionPool": true, /* optional */
"SessionCacheSize": 50 /* optional: size of connection pool */
}
]
} |
...