While you are creating a message service using the New service wizard and have chosen to Create an Endpoint Now, you can enter user specified connection properties. Connection properties vary based on the messaging type. Refer to the following:
Connection Properties for Email and FTP
| Property | Description |
| Host | The host name. |
| Password | The user password. |
| Port | The port number used by the email protocol. The default is 25. Field not used for FTP. |
| Protocol | The protocol used. Email: For a service that sends messages (outbound), use SMTP. FTP: Select FTP or FTPS (secure FTP) |
| User | The user name. |
Connection Properties for JMS
| Property | Description |
| Destination Type | Choose queue. |
| Driver Classpath | Enter the driver classpath or choose the Driver Name in the next field. If you choose a Driver Name, the classpath is automatically completed. |
| Driver Name | Select ... to open the Driver Definitions dialog and choose the JMS driver. When you choose a driver, the driver classpath is automatically completed. |
| Initial Context Factory | Name of the initial
context factory that is used to look up connection factory and queue objects. Required.
Example: com.sybase.jms.InitialContextFactory |
| JNDI Provider URL | URL for the server hosting the
session. Required. Legacy Key: JMS_SES_PROVIDER_URL
Example: iiop://<machine name>:9000 The example assumes the default port number, 9000 is used. To verify the port number, check the eas_install.props file in the <server install directory>/EAServer directory. Check the port value for com.Sybase.jaguar.install.listeners.iiop. |
| Queue | Name of the transport specific instance queue name. Required. |
| Queue Connection Factory | Name of the
connection factory that is used to connect to queues. Required.
Example: javax.jms.QueueConnectionFactory |
You can use the user-specified connection properties to connect to a generic JMS provider without a driver.
Verify that the required .jar files have been extracted to the <EAServer install>/java/classes directory. For example, JBoss requires concurrent.jar, jboss-common-client.jar, jbossmq-client.jar, and jnp-client.jar. The documentation from the JMS provider should provide this list of required .jar files.
Enter the user-specified connection properties, excluding the driver. The following example identifies the values for JBoss JMS.
| Property | Value |
| Destination Type | queue |
| Driver Classpath | C:\JBoss\jboss-4.0.0\client\concurrent.jar,C:\JBoss\jboss-4.0.0\client\jboss-common-client.jar,C:\JBoss\jboss-4.0.0\client\jbossmq-client.jar,C:\JBoss\jboss-4.0.0\client\jnp-client.jar |
| Driver Name | no value |
| Initial Context Factory | org.jnp.interfaces.NamingContextFactory |
| Jndi Provider URL | jnp://<host>:<port> |
| Queue | <queue name> |
| Queue Connection Factory | ConnectionFactory |
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com