JMS Binding Component User's Guide

Creating JMS-Based Concrete WSDL Documents

You can use a wizard to create a concrete WSDL document that contains JMS binding and service information.

In the initial part of the wizard, you must select one of the following types:

The configuration steps that appear next depend on the type that you selected.

ProcedureTo Create a JMS-Based Concrete WSDL Document from the New WSDL Document Wizard

  1. In the Projects window of the NetBeans IDE, right-click the project node and choose New ⇒ WSDL Document.

  2. Set the WSDL Type option to Concrete WSDL Document.

  3. Set the Binding drop-down list to JMS.

  4. Set the Type drop-down list to the appropriate type of JMS-based WSDL document.

  5. Click Next.

  6. Complete the configuration steps that appear next. For a description of each step, see the following topics.

ProcedureTo Create a JMS-Based Concrete WSDL Document from the New File Wizard

  1. In the Projects window of the NetBeans IDE, right-click the project node and choose New ⇒ Other.

  2. In the Categories list, select ESB.

  3. In the File Types list, select Binding.

  4. Click Next.

  5. Set the Binding drop-down list to JMS.

  6. Set the Type drop-down list to the appropriate type of JMS-based WSDL document.

  7. Click Next.

  8. Complete the configuration steps that appear next. For a description of each step, see the following topics.

Request Connection Configuration

When you are creating a JMS-based concrete WSDL document, the Request Connection Configuration step appears for all of the possible types.

Screen capture of the Request Connection Configuration
step.

The JMS Connection section enables you to specify information for connecting to the JMS server.

The Payload Processing section enables you to define the type of JMS messages being created and sent to the JMS destination.

Request Consumer Configuration

When you are creating a JMS-based concrete WSDL document, the Request Consumer Configuration step appears when you select the Receive type.

Screen capture of the Request Consumer Configuration
step.

The Destination Properties section enables you to specify the JMS destination from which messages are received.

The JMS Consumer Properties section enables you to configure properties that apply only to consumer message flows.

Request Publisher Configuration

When you are creating a JMS-based concrete WSDL document, the Request Publisher Configuration step appears when you select the Send type.

Screen capture of the Request Publisher Configuration
step.

The Destination Properties section enables you to specify the JMS destination to which messages are sent.

The JMS Publisher Properties section enables you to configure properties that apply only to provider message flows.

Response Destination Configuration

When you are creating a JMS-based concrete WSDL document, the Response Destination Configuration step appears when you select the Receive with Reply type or the Send and Wait for Reply type.

Screen capture of the Response Destination Configuration
step.

The Destination Properties section enables you to specify the JMS destination to which messages are sent.

The Payload Processing section enables you to define the type of JMS messages being created and sent to the JMS destination.

Response Consumer Configuration

When you are creating a JMS-based concrete WSDL document, the Response Consumer Configuration step appears when you select the Receive with Reply type.

Screen capture of the Response Consumer Configuration
step.

The JMS Consumer Properties section enables you to configure properties that apply only to consumer message flows.

Response Publisher Configuration

When you are creating a JMS-based concrete WSDL document, the Response Publisher Configuration step appears when you select the Send and Wait for Reply type.

Screen capture of the Response Publisher Configuration
step.

The JMS Publisher Properties section enables you to configure properties that apply only to provider message flows.

Advanced Configuration

When you are creating a JMS-based concrete WSDL document, the Advanced Configuration step appears for all of the possible types.

Screen capture of the Advanced Configuration
step.

You can specify any option supported by JMSJCA in the Advanced Configuration step. For example:


JMSJCA.NoXA=false

If you set the connection URL to jndi:// in the Request Connection Configuration step, then you specify the JNDI options in the Advanced Configuration step. For example:


JMSJCA.UnifiedCF=JNDI-name
JMSJCA.TopicCF=JNDI-name
JMSJCA.QueueCF=JNDI-name
java.naming.factory.initial=com.sonicsw.jndi.mfcontext.MFContextFactory
java.naming.provider.url=tcp://localhost:2506
java.naming.security.principal=Administrator
java.naming.security.credentials=Administrator
com.sonicsw.jndi.mfcontext.domain=Domain1
com.sonicsw.jndi.mfcontext.idleTimeout=60000

For more information about using the jndi approach, see Connecting to the JMS Server.