Difference between revisions of "JNDIHelper"
(Created page with "The JNDIHelper Element is used by: DataSourceConnection, j2ee-ejb-call, j2ee-jca-call, jms-dequeue, jms-enqueue, pop-call, ServiceCallerTask, [[smtp-c...") |
|||
| Line 1: | Line 1: | ||
The JNDIHelper Element is used by: [[DataSourceConnection]], [[j2ee-ejb-call]], [[j2ee-jca-call]], [[jms-dequeue]], [[jms-enqueue]], [[pop-call]], [[ServiceCallerTask]], [[smtp-call]] and [[XAHelper]]. It has the following attributes: | The JNDIHelper Element is used by: [[DataSourceConnection]], [[j2ee-ejb-call]], [[j2ee-jca-call]], [[jms-dequeue]], [[jms-enqueue]], [[pop-call]], [[ServiceCallerTask]], [[smtp-call]] and [[XAHelper]]. It has the following attributes: | ||
| − | + | * ''initial-context-factory'': Initial context factory for the JNDI tree containing connection-factory and the destination-name. <br/> Where {{GVESB}} and the server to contact are installed on the application server of the same type, you may leave this parameter unspecified. <br/> Where the application servers are rather different, as well as configure the initial context factory, make sure also that are present in the classpath the classes necessary to connect remote application server. | |
| − | * initial-context-factory: Initial context factory for the JNDI tree containing connection-factory and the destination-name. <br/> Where {{GVESB}} and the server to contact are installed on the application server of the same type, you may leave this parameter unspecified. <br/> Where the application servers are rather different, as well as configure the initial context factory, make sure also that are present in the classpath the classes necessary to connect remote application server. | + | * ''provider-url'': Application server connection URL. Refer to your application server documentation for the configuration of this parameter <br/> If the JNDI Context to be created refers to the current application server you can leave this parameter unspecified. |
| + | * ''security-principal'': Username used to connect the application server. If security is not enabled, you can leave unspecified this parameter. | ||
| + | * ''security-credentials'': Password to connect the application server. <br/>If security is not enabled, you can leave unspecified this parameter. | ||
Revision as of 14:03, 26 January 2012
The JNDIHelper Element is used by: DataSourceConnection, j2ee-ejb-call, j2ee-jca-call, jms-dequeue, jms-enqueue, pop-call, ServiceCallerTask, smtp-call and XAHelper. It has the following attributes:
- initial-context-factory: Initial context factory for the JNDI tree containing connection-factory and the destination-name.
Where GreenVulcano® ESB and the server to contact are installed on the application server of the same type, you may leave this parameter unspecified.
Where the application servers are rather different, as well as configure the initial context factory, make sure also that are present in the classpath the classes necessary to connect remote application server. - provider-url: Application server connection URL. Refer to your application server documentation for the configuration of this parameter
If the JNDI Context to be created refers to the current application server you can leave this parameter unspecified. - security-principal: Username used to connect the application server. If security is not enabled, you can leave unspecified this parameter.
- security-credentials: Password to connect the application server.
If security is not enabled, you can leave unspecified this parameter.
