Create EJB Service Dialog or Update Reference or Update Service Dialog

1.13 Create EJB Service Dialog or Update Reference or Update Service Dialog

Use to integrate Enterprise JavaBeans with SOA composite applications.

Integration is achieved through use of service data object (SDO) parameters or Java interfaces. Integration with SDO-based EJBs uses a Web Services Description Language (WSDL) file to define the interface. Integration with Java interfaces does not use a WSDL file to define the interface.

SDOs enable you to modify business data regardless of how it is physically accessed. Knowledge is not required about how to access a particular back-end data source to use SDO in a SOA composite application. Consequently, you can use static or dynamic programming styles and obtain connected and disconnected access.

EJBs are server-side domain objects that fit into a standard component-based architecture for building enterprise applications with Java. These objects become distributed, transactional, and secure components.

Oracle SOA Suite interfaces are described by the WSDL file. EJB interfaces are described by Java interfaces. Invocations between the two are made possible in Oracle SOA Suite by an EJB Java interface that corresponds to an Oracle SOA Suite WSDL interface.

Through this interface, Oracle SOA Suite provides support for the following:

Invoking EJBs with SDO parameters through an EJB reference
Invoking an EJB service through EJBs with SDO parameters

Integration of Enterprise JavaBeans with Oracle SOA Suite through Java interfaces eliminates the need for WSDL file definitions. This type of integration provides support for the following objects:

Native Java objects
Java Architecture for XML Binding (JAXB)

Element	Description
Name	Accept the default value of `Servicenumber` or enter a different name.
Type	Select the direction in which you want the EJB service to operate. Service: Creates an EJB service in the Exposed Services (left) swimlane that provides the outside world with an entry point to the SOA composite application. This direction is selected by default if you dropped the EJB service into the Exposed Services swimlane. More Reference: Creates an EJB service in the External References (right) swimlane that enables messages to be sent from the SOA application to external partners in the outside world. This direction is selected by default if you dropped the EJB service into the External References swimlane. More
Version	Select the version of EJB to support: EJB2 or EJB3 (the default selection). Note: This field only displays if you dragged the EJB Service icon into the External References swimlane.
Interface	Select the interface.
JAVA	Select to create a Java interface-based Enterprise JavaBeans integration with SOA composite applications (does not use a WSDL file to define the interface).
WSDL	Select to create an SDO-based Enterprise JavaBeans integration with SOA composite applications (uses a WSDL file to define the interface).
JNDI Name	Enter the JNDI name. This field only displays if you selected the following: The JAVA radio button in the Interface section. The WSDL radio button in the Interface section, and the EJB service is being created as a reference binding component in the External References swimlane.
JAR File	Click the Search icon to select the EJB JAR file. The JAR file must include the interface class and any supporting classes. Note: If you select a JAR file outside of the current project, Oracle JDeveloper creates a copy of the JAR file in the `SCA-INF/lib` directory of the current project. When prompted, click OK to accept.
JAVA Interface	Click the Browse icon to invoke the Class Browser dialog for selecting the fully qualified Java class name of the previously created Enterprise JavaBeans interface. This class must exist in the selected JAR file. If a JAR file is not specified, it is assumed that the class is in the `/SCA-INF/classes` subdirectory of the current project directory. If you have a new JAR file, you must add it to the project by selecting Project Properties > Libraries and Classpath > Add JAR/Directory from the Application main menu. This enables the JAR file to display in the Class Browser.
WSDL URL	Note: Ensure that have already created the annotations for the EJB interface before generating the WSDL file. Select the Web Services Description Language (WSDL) file to use. This field only displays if you selected the WSDL radio button in the Interface section. This file describes the capabilities of the service that provides an entry point into a SOA application or a reference point from a SOA application. The WSDL file provides a standard contract language and is central for understanding the capabilities of a service. Note: Do not manually update the WSDL location in your file in Source View. This action is not supported. Only updates made in Design View are supported.
Find existing WSDLs icon	Click to select an existing WSDL file.
Generate WSDL from Java Interface Class icon	Click to generate a WSDL file from a Java interface class that represents the EJB interface. If no JAR is specified, then classes in `SCA-INF/classes` are used.
Port Type	Select the port type or use the automatically specified value. This field only displays if you selected the WSDL radio button in the Interface section.
Callback Port Type	Select the callback port type for asynchronous processes. This field only displays if you selected the WSDL radio button in the Interface section.