Index Changes

Difference between version and version     

Back to Connecting To The JMS Server, or Connecting To The JMS Server Info


At line 1 added 2 lines.
!!Using the JMS Binding Component
At line 2 changed 1 line.
* [JMS Binding Component User Guide|JMSBindingComponentUserGuide]
* [Using the JMS Binding Component|UsingJMSBindingComponent]
* [JMS Binding Component Overview]
* [JMS Binding Component Features]
* [JMS Binding Component Scenarios]
* [Creating JMS-Based Concrete WSDL Documents]
* __Connecting to the JMS Server__
** Specifying the Protocol, Server, and Port
** Connecting to the JMS Server by Using JNDI
* [Configuring Redelivery Handling]
* [Using the Normalized Message Properties]
* [JMS WSDL Extensibility Elements]
* [JMS Binding Component Clustering]
* [Publishing and Subscribing to Multiple WebSphere Queues]
At line 18 added 2 lines.
At line 6 changed 1 line.
You use a connection URL to specify the information for connecting to the JMS server.
You use a ''connection URL'' to specify the information for connecting to the JMS server.
At line 30 added 1 line.
You can connect to any JMS server by using the Java Naming and Directory Interface%%sup TM%% (JNDI) to locate an existing JMS connection factory.
At line 15 changed 1 line.
You can connect to any JMS server by using the Java Naming and Directory InterfaceTM (JNDI) to locate an existing JMS connection factory.
A ''connection factory'' is a Java class supplied by the JMS provider. For example:
At line 17 removed 2 lines.
A connection factory is a Java class supplied by the JMS provider. For example:
At line 35 added 1 line.
At line 29 changed 1 line.
The following connection URL includes a protocol, server, and port for Sun JavaTM System Message Queue:
The following connection URL includes a protocol, server, and port for Sun Java%%sup TM%% System Message Queue:
At line 52 added 1 line.
At line 39 changed 1 line.
When you use a wizard to create a JMS-based concrete WSDL document, you set the connection URL in the Request Connection Configuration step of the wizard. For more information, see Creating JMS-Based Concrete WSDL Documents.
When you use a wizard to create a JMS-based concrete WSDL document, you set the connection URL in the Request Connection Configuration step of the wizard. For more information, see [Creating JMS-Based Concrete WSDL Documents|CreatingJMSBasedConcreteWSDLDocuments].
At line 60 added 1 line.
At line 54 changed 1 line.
You can connect to any JMS server by using the Java Naming and Directory InterfaceTM (JNDI) to locate an existing JMS connection factory.
You can connect to any JMS server by using the Java Naming and Directory Interface%%sup TM%% (JNDI) to locate an existing JMS connection factory.
At line 64 changed 1 line.
This scenario can occur when a managed connection factory has been created. Managed connection factories provide additional services on top of a connection factory. The additional services include connection pooling. The managed connection factory creates a connection factory wrapper.
This scenario can occur when a ''managed connection factory'' has been created. Managed connection factories provide additional services on top of a connection factory. The additional services include connection pooling. The managed connection factory creates a connection factory wrapper.
At line 86 added 1 line.
At line 71 changed 1 line.
When you use a wizard to create a JMS-based concrete WSDL document, you set the connection URL in the Request Connection Configuration step of the wizard. For more information, see Creating JMS-Based Concrete WSDL Documents.
When you use a wizard to create a JMS-based concrete WSDL document, you set the connection URL in the Request Connection Configuration step of the wizard. For more information, see [Creating JMS-Based Concrete WSDL Documents|CreatingJMSBasedConcreteWSDLDocuments].
At line 94 added 1 line.
At line 108 added 1 line.
At line 92 changed 1 line.
When you use a wizard to create a JMS-based concrete WSDL document, you set the connection URL in the Request Connection Configuration step of the wizard. You then specify the JNDI options in the Advanced Configuration step of the wizard. For more information, see Creating JMS-Based Concrete WSDL Documents.
When you use a wizard to create a JMS-based concrete WSDL document, you set the connection URL in the Request Connection Configuration step of the wizard. You then specify the JNDI options in the Advanced Configuration step of the wizard. For more information, see [Creating JMS-Based Concrete WSDL Documents|CreatingJMSBasedConcreteWSDLDocuments].
At line 117 added 1 line.
At line 130 added 1 line.
At line 142 added 1 line.
At line 122 changed 1 line.
<![CDATA[JMSJCA.UnifiedCF=connectionfactories/xaconnectionfactory JMSJCA.TopicCF=connectionfactories/xatopicconnectionfactory JMSJCA.QueueCF=connectionfactories/xaqueueconnectionfactory java.naming.factory.initial=com.stc.jms.jndispi.InitialContextFactory java.naming.provider.url=stcms://localhost:18007 java.naming.security.principal=Administrator java.naming.security.credentials=STC]]&gt;
<![CDATA[JMSJCA.UnifiedCF=connectionfactories/xaconnectionfactory
JMSJCA.TopicCF=connectionfactories/xatopicconnectionfactory
JMSJCA.QueueCF=connectionfactories/xaqueueconnectionfactory
java.naming.factory.initial=com.stc.jms.jndispi.InitialContextFactory
java.naming.provider.url=stcms://localhost:18007
java.naming.security.principal=Administrator
java.naming.security.credentials=STC]]>

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-17) was last changed on 03-Jun-09 18:56 PM, -0700 by CarolT