Configure endpoint URL information to directly access enterprise beans
WebSphere Application Server supports directly accessing an enterprise bean as a web service, as an alternative to using HTTP or Java Message Service (JMS) to transport requests between the server and the client. The EJB module used as a web service contains a Web Services Description Language (WSDL) file containing EJB bindings.
To learn more about the process of directly accessing an enterprise bean as a web service, see the using WSDL EJB bindings to invoke an EJB from a JAX-RPC web services client.
We can use either the administrative console or property files to configure and manage EJB endpoint URL fragments. To learn about using property files to set and manage the URL fragments, see the information about working with web services endpoint URL fragment property files.
This task describes using the administrative console to configure endpoint URL information to directly access enterprise beans.
Configure a service endpoint 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 accessed directly by EJB bindings using the Provide JMS and EJB endpoint web address information panel in the administrative console.
If we have modules configured for using direct EJB access, the modules are listed on the Provide JMS and EJB endpoint web address information panel in the administrative console. The EJB endpoint is only available in the WSDL found in the application_name_ExtendedWSDLfiles.zip file.
We 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 administrative console:
Tasks
- Open the administrative console.
- Click Applications > Enterprise Applications > application_instance > Provide JMS and EJB endpoint URL information.
- Locate the list of EJB modules.
- Select the application module.
- 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.
- Click OK.
- Click Save.
We have configured endpoints of the enterprise bean for Web services 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/MyStockQuoteHomeEnter the following web address fragment in the URL fragment field:jndiProviderURL=corbaloc:iiop:myhost.mycompany.com:2089The results are shown in the following example:wsejb:/com.acme.sample.MyStockQuoteHome?jndiName=ejb/MyStockQuoteHome&jndiProviderURL= corbaloc:iiop:myhost.mycompany.com:2089
What to do next
Provide a description of the web service to the service requestor by publishing WSDL files. To learn more, read about making deployed web services applications available to clients.
Configure endpoint URL information for HTTP bindings Configure endpoint URL information for JMS bindings Use WSDL EJB bindings to invoke an EJB from a JAX-RPC Web services client Making deployed web services applications available to clients Work with web services endpoint URL fragment property files EJB endpoint URL syntax