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 that is used as a Web service contains a Web Services Description Language (WSDL) file that contains EJB bindings.
Configuring 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.
You 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 administrative console.
If you 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 administrative 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 administrative console:The following example illustrates a Web address fragment to enter in the URL fragment field.
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
In this information ...Related tasks
Related reference
| IBM Redbooks, demos, education, and more(Index) |