Connection options

The Progress OpenEdge JMS Adapter supports most of the same connection options as the Progress Application Server for OpenEdge. You specify the desired options as the value of the adapterConnection parameter. The following table lists and explains the valid formats for expressing these options.

Table 1. Progress OpenEdge JMS Adapter connection options
Connection option Description 
-H [host_name|IP-address]
 Specifies the network address that the oemessaging script runs on; or, if you use the -DirectConnect option, the address of a machine hosting the Progress OpenEdge JMS Adapter. You can use either the TCP/IP host name or the IP address of the machine. (Defaults to localhost.) 
-S [port-number|service-name ]
 Specifies the UDP port number that the oemessaging script runs on; or, if you use the -DirectConnect option, the TCP/IP port number for the Progress OpenEdge JMS Adapter. You can use either an explicit port number or a name associated with a port number in the TCP/IP services file. (Defaults to 3620 for a direct connection to a Progress OpenEdge JMS Adapter.) 
-DirectConnect
 If included, causes the -H and -S parameters to be interpreted as the network address and TCP/IP port number of a specific Progress OpenEdge JMS Adapter. If the -DirectConnect switch is omitted, the -H and -S parameters are interpreted as the network address and UDP port number of the Progress OpenEdge JMS Adapter. 
-ssl
 If included, specifies a secure connection to an SSL-enabled OpenEdge JMS Adapter. For more information, see OpenEdge Getting Started: Core Business Services. 
-nohostverify
 If included, turns off host verification for a secure (SSL) connection. In the case of an SSL connection, unless this switch is included, the client compares the host name (specified in the -H parameter or the -URL parameter) with the Common Name specified in the server certificate, and raises an error if they do not match. With -nohostverify in effect, the client never raises the error. This option works only in the context of a secure connection; that is, in combination with the -ssl switch or with HTTPS. For more information, see OpenEdge Getting Started: Core Business Services. 
-nosessionreuse
 If included, prevents the application from reusing the session ID when reconnecting to the same SSL-enabled Progress OpenEdge JMS Adapter .This option works only in the context of a secure (SSL) connection; that is, in combination with the -ssl switch or with HTTPS. For more information, see OpenEdge Getting Started: Core Business Services. 
-pf pathname
 Specifies a text file containing any of the application server connection parameters described in this table. Any other OpenEdge startup parameters in the file are ignored. 
-SMQConnect
 Creates a direct connection to the JMS-provider Broker using the jmssession.p Session object.

The following table shows several examples of valid adapterConnection parameters.

Table 2. Connection parameter examples
Connection parameter Description 
""
 By default, connection to the Progress OpenEdge JMS Adapter running on UDP port 3620 on localhost. 
"-H host1 -S 5163"
 Connection to the Progress OpenEdge JMS Adapter running on UDP port 5163 on the machine host1. 
"-H fortress -S 3621 -DirectConnect -ssl
-nohostverify"
 Secure connection directly to the SSL-enabled Progress OpenEdge JMS Adapter running on TCP/IP port 3621 on the machine fortress, with host verification disabled. 
RUN jms/jmssession.p PERSISTENT SET sessionH ("-SMQConnect").
 Connects directly to the JMS-provider Broker allowing better connection and session management

See OpenEdge Getting Started: Core Business Services for a comprehensive discussion of SSL connections, management of keys and certificates, and other security considerations in OpenEdge.