Transport Details

The Transport Details tab allows you to specify additional configuration information based on the type of transport used for the SOAP request. When HTTP is the transport, the HTTP sub-tab appears on this tab. When JMS is the transport, the JNDI and JMS sub-tabs appear. For more information about SOAP over the JMS transport, see SOAP Messages Over the JMS Transport.

The Transport Details tab contains the following fields:

Field

Global Var?

Description

HTTP Sub-Tab

Endpoint URL

Yes

The URL of the web service that you are sending a request to. This field is automatically populated with the choice made when selecting the service.

You can specify URLs that use the HTTPS (secure sockets) protocol. If you specify HTTPS as the protocol, the SSL field becomes enabled.

Use HTTP Proxy

No

When checked, this field specifies that an HTTP proxy server is used to connect to the SOAP server. Enabling this field causes the Proxy field to appear.

Proxy

No

Appears when the Use HTTP Proxy field is enabled. This field specifies the Proxy Configuration shared configuration resource that describes the HTTP proxy server. For more information, see Proxy Configuration.

HTTP Authentication

No

Specifies what authentication should be used . An authentication can be of the following three types:

  • NONE - is default.

  • BASIC - to continue with the current implementation of using username and password credentials. The Identity field appears when this field is enabled.

  • NTLM - Identity and Domain fields appear when NTLM is selected. Identity is a reference of the Username and Password combination.

Identity

No

This is an Identity resource that contains the client’s username and password. This identity is used to perform only Basic and NTLM authentication.

Domain

No

Specifies the domain to be used for Authentication. The user name and password specified in the Identity field must exist in the domain.

JNDI Sub-Tab

Context URL

Yes

This is the URL to the JNDI service provider (javax.naming.Context.PROVIDER_URL). The value for this field is taken from the WSDL file, if it is available in the <jndi:context> element in the service specification. You can override the supplied value, if you want to use a different JNDI service provider.

For the syntax of the URL, see your JNDI provider documentation.

User Name

Yes

User name to use when logging into the JNDI server (javax.naming.Context.SECURITY_
PRINCIPAL
). If the JNDI provider does not require access control, this field can be empty.

Password

Yes

Password to use when logging into the JNDI server (javax.naming.Context.SECURITY_
CREDENTIALS
). If the JNDI provider does not require access control, this field can be empty.

Context Factory

Yes

The initial context factory class for accessing JNDI (javax.naming.Context.INITIAL_CONTEXT_
FACTORY
). The value for this field is taken from the WSDL file, if it is available in the <jndi:context> element in the service specification. You can override the supplied value, if you want to use a different context factory.

Note: ActiveMatrix BusinessWorks attempts to find the class. However, you may need to add the Java file supplied by your JNDI service provider to the CLASSPATH environment variable to use JNDI.

Connection Factory

Yes

The QueueConnectionFactory object stored in JNDI. This object is used to create a queue connection with a JMS application. The value for this field is taken from the WSDL file, if it is available in the <jms:connectionFactory> element in the service specification. You can override the supplied value, if you want to use a different connection factory.

For more information about creating and storing QueueConnectionFactory objects, see your JNDI provider documentation.

SSL

No

Specifies whether you want to use SSL for the connection to the JNDI server. SSL is used when the Use SSL? check box is selected. Click the Configure SSL button to configure the SSL connection parameters. For more information, see Configure SSL.

SSL Password

Yes

Password to use during the SSL connection.

Validate Security Context

Yes

Checking this field ensures that the security context provided on this tab is the one used to connect to the JNDI server.

Some application servers store the security context on the thread used to establish the JNDI connection. Therefore the first activity to use this resource establishes the security context, and then subsequent activities use the same security context, unless this field is checked. Checking this field ensures that each activity that uses this resource examines the security context to determine if the activity uses the same security context as the security context established on the thread. If they are different, the activity’s configured security context is used.

Checking this field causes additional overhead for activities that use this resource. The only supported application server that requires this field to be checked is WebLogic.

Properties

No

Any additional properties to supply for the connection. You specify a name, datatype, and value for each property.

These properties are typically vendor-specific. For more information about the available properties, see your JNDI provider documentation.

JMS Sub-Tab

User Name

Yes

User name to use to authenticate to the JMS server.

Password

Yes

Password to use to authenticate to the JMS server.

JMS Destination

Yes

Name of the JMS destination for the SOAP request.

The syntax of the destination name is specific to the JMS provider you are using. For more information about destination names, see your JMS provider documentation.

Note: If you are using TIBCO Enterprise Message Service as your JMS provider, you can use the Browse button next to this field after specifying a valid connection in the JMS Connection field. The Browse button displays a list of configured destinations in the JMS server that are appropriate for this activity.

Message Type

Yes

The type of the message. This can be one of the following:

  • Bytes Message — A stream of bytes.

  • Text Message — The message is a java.lang.String.

Delivery Mode

Yes

The delivery mode of the message. Can be one of the following:

  • PERSISTENT: signifies the messages are stored and forwarded.

  • NON-PERSISTENT: messages are not stored and may be lost due to failures in transmission.

  • TIBCO EMS Reliable: this mode is only available when using TIBCO Enterprise Message Service. For more information about this mode, see the TIBCO Enterprise Message Service documentation.

Expiration

Yes

Corresponds to JMSExpiration property that specifies how long the message can remain active (in seconds).

If set to 0, the message does not expire.

This field is set in seconds, but the JMSExpiration property is displayed in milliseconds.

Priority

Yes

Priority of the message. You may set the priority to a value from 0-9. The default value is 4.

Use Shared JMS Configuration

No

Check this field if you want to specify a JMS Connection shared configuration resource to override the JMS transport parameters in the concrete WSDL. When checked, this JMS Connection field appears.

JMS Connection

No

This field only appears when the Use Shared JMS Configuration field is checked. This field allows you to specify a JMS Connection shared configuration resource that contains the connection information you want to use to override the JMS transport parameters in the concrete WSDL.

Enable W3C SOAP JMS 1.0 Compliance

 

This is a read-only field that displays whether the service is W3C SOAP Over JMS 1.0 compliant or not.

Target Service

 

This field is available only when the check box Enable W3C SOAP JMS 1.0 Compliance is selected.

Specify the target service value, if any.

Note: If Target Service is configured, the value is reflected in the WSDL as a query parameter.

Application Properties (Input Message)

 

Any application-specific message properties that are a part of the input message.

Application Properties (Output Message)

 

Any application-specific message properties that are a part of the output message.