JNDI environment references

Similar documents
Figure 1: OpenJMS Integration using GenericJMS RA

IBM EXAM - C IBM WebSphere Enterprise Service Bus V7.0, Integration Development. Buy Full Product.

Java EE 7: Back-End Server Application Development

J2EE Development with Apache Geronimo. Aaron Mulder Chariot Solutions

FLEXCUBE UBS Oracle GL Adapter EJB Deployment Installation Oracle FLEXCUBE Universal Banking Release [December] [2016]

Contents at a Glance. vii

IBM WebSphere Enterprise Service Bus V7.0, Integration Development Exam.

J2EE Development with Apache Geronimo. Aaron Mulder Chariot Solutions

Process Choreographer: High-level architecture

Oracle Fusion Middleware

Course: JBoss Training: JBoss AS 7 and JBoss EAP 6 Administration and Clustering Training

Connecting Enterprise Systems to WebSphere Application Server

Oracle WebLogic Server 11g: Administration Essentials

BEAAquaLogic. Service Bus. MQ Transport User Guide

J2EE Development. Course Detail: Audience. Duration. Course Abstract. Course Objectives. Course Topics. Class Format.

web.xml Deployment Descriptor Elements

NetBeans IDE Field Guide

Inside WebSphere Application Server

Oracle 10g: Build J2EE Applications

Artix for J2EE. Version 4.2, March 2007

JBoss Enterprise Application Platform 5

Using GenericJMSRA with IBMWebSphere MQ

JBOSS AS 7 AND JBOSS EAP 6 ADMINISTRATION AND CLUSTERING (4 Days)

index_ qxd 7/18/02 11:48 AM Page 259 Index

BEAAquaLogic. Service Bus. Native MQ Transport User Guide

Installing and Configuring Apache ActiveMQ With iway Service Manager Version 8

Deccansoft Software Services. J2EE Syllabus

J2EE Development with Apache Geronimo. Aaron Mulder Chariot Solutions

B. Assets are shared-by-copy by default; convert the library into *.jar and configure it as a shared library on the server runtime.

CO Java EE 7: Back-End Server Application Development

J2EE - Version: 25. Developing Enterprise Applications with J2EE Enterprise Technologies

JBoss SOAP Web Services User Guide. Version: M5

WA2031 WebSphere Application Server 8.0 Administration on Windows. Student Labs. Web Age Solutions Inc. Copyright 2012 Web Age Solutions Inc.

Setting up Property File Oracle FLEXCUBE Universal Banking Version [May] [2011]

Using CCDT in an Activation Specification for a Queue Manager Group of separate queue managers in WAS V7, V8.0 and V8.5

Oracle Banking APIs. Part No. E Third Party Simulation Guide Release April 2018

Exam Name: IBM Certified System Administrator - WebSphere Application Server Network Deployment V7.0

Installing and Configuring the Runtime Processes 2

Setting up Property File Oracle FLEXCUBE Universal Banking Version 12.0 [May] [2012]

Administering the JBoss 5.x Application Server

Fast Track to EJB 3.0 and the JPA Using JBoss

Installing and Configuring Apache ActiveMQ With iway Service Manager

EVALUATION ONLY. WA2097 WebSphere Application Server 8.5 Administration on Linux. Student Labs. Web Age Solutions Inc.

11-15 DECEMBER ANTWERP BELGIUM

Java- EE Web Application Development with Enterprise JavaBeans and Web Services

1Z Oracle Weblogic Server 11g: System Administration I

Deploying Applications to Oracle WebLogic Server g Release 1 (10.3.6)

GATEWAY Property File Creation Oracle FLEXCUBE Universal Banking Release [May] [2018]

Gateway Property File Creation Oracle Banking Payments Release [May] [2018]

1Z Oracle WebLogic Server 12c - Administration I Exam Summary Syllabus Questions

Administering JMS Resources for Oracle WebLogic Server c (12.1.3)

Securing Resources Using Roles and Policies for Oracle WebLogic Server c (12.1.3)

Installing MCA Services on WebSphere 5.1

BEAWebLogic Server. WebLogic Web Services: Advanced Programming

Oracle Fusion Middleware

Configuring the module for advanced queue integration

Tutorial 5 : Invoking Siebel Business Object through the Oracle AS Adapter

# Application server configuration

GlassFish 3.1 Admin Console Modules

BEAWebLogic. Server. Programming WebLogic Deployment

Oracle WebLogic Server 12c: Administration I

GATEWAY Property File Creation Oracle FLEXCUBE Universal Banking Release [December] [2016]

Oracle Fusion Middleware

JBoss WS User Guide. Version: CR1

Web Application Development Using JEE, Enterprise JavaBeans and JPA

The main namespace for the deployment plan, which should always be

Fast Track to Java EE

FTM Real Time Payments installation and deployment information for Zelle

BEAWebLogic Server and WebLogic Express. Programming WebLogic JNDI

BEAAquaLogic. Service Bus. JPD Transport User Guide

Distributed Multitiered Application

Compile the source. MDB Single Instance Lab

Web Application Development Using JEE, Enterprise JavaBeans and JPA

Edition 0.1. real scenarios for managing EAP instances. Last Updated:

WAS: WebSphere Appl Server Admin Rel 6

Tibco TB ActiveMatrix BusinessWorks 5 Certification Exam. Practice Test. Version:

BEAAquaLogic. Service Bus. Interoperability With EJB Transport

(9A05803) WEB SERVICES (ELECTIVE - III)

Integration Framework. Architecture

Transaction service settings

Tutorial 6 : Receiving Siebel Integration Object through the Oracle AS Adapter

Oracle Fusion Middleware

Oracle Fusion Middleware

Apache Axis2. Tooling with Axis2

Oracle Fusion Middleware

An Example WebSphere Configuration With MQ and DCS

J2EE Development with Apache Geronimo 1.1. Aaron Mulder CTO, Chariot Solutions Committer, Apache Geronimo

Java 2 Platform, Enterprise Edition: Platform and Component Specifications

Enterprise JavaBeans. Layer 05: Deployment

WebSphere Application Server - Overview

Chapter 2 WEBLOGIC SERVER DOMAINS. SYS-ED/ Computer Education Techniques, Inc.

BEAWebLogic. Server. Deploying Applications to WebLogic Server

Configuring DB2 Datasource

TIBCO ActiveMatrix Adapter Service Engine for Files Examples. Software Release 6.0 April 2009

Java EE 6: Develop Business Components with JMS & EJBs

Red Hat Decision Manager 7.0

Using the JNBridge JMS Adapter for.net with JBoss JMS version 4.0

Installation Guide for the Workspot Enterprise Connector

Interstage JavaEE6 Configuration for FCUBS Oracle FLEXCUBE Universal Banking Version [Dec] [2014]

White Paper. Major Performance Tuning Considerations for Weblogic Server

Transcription:

JNDI environment references JNDI environment references Resources referenced by JNDI names often must be mapped into the names of the resources as deployed in the server. This allows resource programmers to choose names without regard to the server's configuration. Deployment plans contain the information necessary to map the names chosen to resources deployed in the server. References must be defined in the following order. #EJB references #EJB local references #Web service references #Resource references #Resource environment references EJB references Use the <ejb-ref> to map a reference to an EJB's remote home interface. Choose one of the following templates. Choose this template when the referenced remote home interface can be found by searching in your module's EAR (when the module is included in an EAR) or your module's <dependencies>. <ejb-ref> <ejb-link>link</ejb-link> </ejb-ref> name is the name of the remote home interface used in your module. The JNDI name used by your module will be java:/comp/env/n ame and it should map to the ejb-ref-name provided in the Java EE deployment descriptor. link is the name of the remote home interface in the EJB module. Choose this template when the referenced remote home interface can only be found with additional selection criterion. For example, if the remote home interface name is not unique within your module's EAR (when the module is included in an EAR) or your module's <dependencies> this template will remove any ambiguity.

<ejb-ref> <name>link</name> </ejb-ref> name is the name of the remote home interface used in your module. The JNDI name used by your module will be java:/comp/env/n ame and it should map to the ejb-ref-name provided in the Java EE deployment descriptor. group is the directory or directory tree in the repository the unique artifact directory is located. link is the name of the remote home interface in the EJB module. EJB local references Use the <ejb-local-ref> to map a reference to an EJB's local home interface. Choose one of the following templates. Choose this template when the referenced local home interface can be found by searching in your module's EAR (when the module is included in an EAR) or your module's <dependencies>. <ejb-local-ref> <ejb-link>link</ejb-link> </ejb-local-ref> name is the name of the local home interface used in your module. The JNDI name used by your module will be java:/comp/env/name and it should map to the ejb-ref-name provided in the Java EE deployment descriptor. link is the name of the local home interface in the EJB module. Choose this template when the referenced remote home interface can only be found with additional selection criterion. For example, if the remote home interface name is not unique within your module's EAR (when the module is included in an EAR) or your module's <dependencies> this template will remove any ambiguity.

<ejb-local-ref> <name>name</name> </ejb-local-ref> name is the name of the local home interface used in your module. The JNDI name used by your module will be java:/comp/env/name and it should map to the ejb-ref-name provided in the Java EE deployment descriptor. group is the directory or directory tree in the repository the unique artifact directory is located. link is the name of the local home interface in the EJB module. Web service references Use the <service-ref> element to map a reference to a Web service. Choose one of the following templates. Use this template when the WSDL for the referenced Web service is complete. This reference will target only the ports listed. <service-ref> <service-ref-name>name</service-ref-name> <!-- Repeat the port element for each port available through the reference --> <port> <port-name>portname</port-name> <protocol>protocol</protocol> <host>host</host> <port>port</port> <uri>uri</uri> <credentials-name>credentials</credentials-name> </port> </service-ref> name is the name of the service reference used in your module. The JNDI name used by your module will be java:/comp/env/name and it should map to the service-ref-name provided in the Java EE deployment descriptor. portname specifies the name to identify the port to connect to. protocol specifies the protocol to use for the connection, typically http or https.

host specifies the host for the connection. port specifies the port for the connection. uri specifies the web service to connect to. credentials identifies the credentials name to be used for secure connections. Use this template when the WSDL for the referenced service is not complete. The elements specified here will provide the information needed to complete the WSDL. <service-ref> <service-ref-name>name</service-ref-name> <service-name>service</service-name> <!-- Repeat the port-completion element for every port available from the reference --> <port-completion> <port> <port-name>portname</port-name> <protocol>protocol</protocol> <host>host</host> <port>port</port> <uri>uri</uri> <credentials-name>credentials</credentials-name> </port> <binding-name>binding</binding> </port-completion> </service-ref> name is the name of the service reference used in your module. The JNDI name used by your module will be java:/comp/env/name and it should map to the service-ref-name provided in the Java EE deployment descriptor. service is the service name for the service block in the WSDL. portname specifies the name to identify the port to connect to. protocol specifies the protocol to use for the connection, typically http or https. host specifies the host for the connection. port specifies the port for the connection. uri specifies the web service to connect to. credentials identifies the credentials name to be used for secure connections. binding specifies the binding name to that identifies this web service port configuration. Resource references Use the <resource-ref> element to map a reference to a URL or a connector's connection factory Choose one of the following templates. Choose this template when the reference is for a URL. <resource-ref> <url>url</resource-url> </resource-ref>

URL is the URL that is be be mapped to that reference. Choose this template when the reference is used to find a connection factory that can be found by searching in your module's EAR (when the module is included in an EAR) or your module's <dependencies>. Typically, this will be a JDBC or JMS connection factory, but it could be any connection factory from a Java EE connector with an <outbound-resourceadapter>. <resource-ref> <resource-link>link</resource-link> </resource-ref> link is the name to be mapped to the reference and should match the name specified in the <connectiondefinition-instance> element of the connector's deployment plan. Choose this template when the referenced connection factory can only be found with additional selection criterion. For example, if the connection factory name is not unique within your module's EAR (when the module is included in an EAR) or your module's <[dependencies> this template will remove any ambiguity. <resource-ref> <name>name</name> </resource-ref> group is the directory or directory tree in the repository the unique artifact directory is located. link is the name to be mapped to the reference and should match the name specified in the <connectiondefinition-instance> element of the connector's deployment plan. Resource environment references

Use the <resource-env-ref> to map a reference to a Java connector's administered object. If you are deploying an asset that uses Java EE 1.3 conventions for its Java EE deployment descriptors, this can also be used to map JMS topics and queues, but for any asset that follows Java EE 1.4 connections or better, the <message-destination> element should be used instead. Choose this template when the reference is used to find an administered object that can be found by searching in your module's EAR (when the module is included in an EAR) or your module's <dependencies>. <resource-env-ref> <!-- <admin-object-module>module</admin-object-module> --> <admin-object-link>link</admin-object-link> </resource-env-ref> The <admin-object-module> element is required when the queue or topic name is not unique in the server. In this case, module is the name of the connector that contains the topic or queue specified in the <admin-object-link> element. link is the name of the administered object to be mapped to the reference and should match the name specified in the <messagedestination-name> element of the <adminobject-instance> of the connector's deployment plan. Choose this template when the referenced administered object can only be found with additional selection criterion. For example, if the administered object name is not unique within your module's EAR (when the module is included in an EAR) or your module's <dependencies>, this template will remove any ambiguity. <resource-env-ref> <name>link</name> </resource-env-ref> group is the directory or directory tree in the repository the unique artifact directory is located. link is the name of the administered object to be mapped to the reference and should match the name specified in the <messagedestination-name> element of the <adminobject-instance> of the connector's deployment plan.