Set endpoint URL information to directly access enterprise beans

WAS supports directly accessing an enterprise bean as a Web service, as an alternative to using HTTP or JMS to transport requests between the server and the client. The EJB module used as a Web service contains a WSDL file that contains EJB bindings.

To learn more about the process of directly accessing an enterprise bean as a Web service, review the topic Use EJB bindings to invoke an enterprise bean from a Web services client .

Set a service endpoint is necessary to connect Web service clients to any Web services among the components being assembled or to any external Web services.

We can specify Web address endpoints of the enterprise bean for Web services that are accessed directly by EJB bindings using the Provide JMS and EJB endpoint Web address information panel in the admin console.

If we have modules that are configured for using direct EJB access, the modules are listed on the Provide JMS and EJB endpoint Web address information panel in the admin console. The EJB endpoint is only available in the WSDL that is found in the application_name_ExtendedWSDLfiles.zip file.

You can specify a fragment of the endpoint Web address for the Web services in each module. To configure the Web address endpoints of the enterprise bean with the admin console:

 

1. Open the admin console.

2. Click Applications > Enterprise Applications > application_instance > Provide JMS and EJB endpoint URL information.

3. Locate the list of EJB modules.

4. Select the application module.

5. Type the Web address fragment in the URL fragment field.

   Enter a Web address fragment that is a suffix to the initial Web address part that is obtained by examining the Web service deployment information. See the example following this task for more information.

   The value that you enter is used to define the location attribute of the port generic:address element within the WSDL file that is published using the application_name_ExtendedWSDLFiles.zip file name link on the Publish WSDL zip files panel. The zip file names are listed as links on the panel.

6. Click OK.

7. Click Save.

 

Results

we have configured endpoints of the enterprise bean for Web services that are accessed directly by EJB bindings.

 

Example

The following example illustrates a Web address fragment to enter in the URL fragment field.

The following Web address information can be obtained from the deployment descriptor of an enterprise bean:

wsejb:/com.acme.sample.MyStockQuoteHome?jndiName=ejb/MyStockQuoteHome

Enter the following Web address fragment in the URL fragment field:

jndiProviderURL=corbaloc:iiop:myhost.mycompany.com:2089

The results are shown in the following example:

wsejb:/com.acme.sample.MyStockQuoteHome?jndiName=ejb/MyStockQuoteHome&jndiProviderURL= corbaloc:iiop:myhost.mycompany.com:2089

 

Next steps

Provide a description of the Web service to the service requestor by publishing WSDL files.

 

Related tasks

Set endpoint URL information for HTTP bindings
Set endpoint URL information for JMS bindings
Provide JMS and EJB endpoint URL information

 

Related

EJB endpoint URL syntax