This content has been marked as final. Show 1 reply
Lets go item by item :
- Using JCA DB Adapters (From OSB or SCA Application)
- In OSB You can use a EJB-Transport Business Service, that utilizes a Foreign JNDI provider (Configuration Component made on OSB console) pointing to the External JNDI Context on which the EJB's are published. (EJB Transport)
- If you want to access an EJB from a Composite Application you can use the EJB Service tool, which act as a EJB Control on the good old WLI Workshop. Here is a good tutorial : Calling an EJB from a SOA Composite Application using the EJB Binding based on Java Interface</title> //<tit…
- If you use the solution i propoused on item nr 2-A, i would make a EJB-Business for each EJB and then make a Local Proxy for each Business made this way. Then its up to you building further PS that would expose the Local PS in any way you require (HTTP/HTTPs, JMS, SB, Etc.).
- If you use the solution i propoused on item nr 2-B, you can make Service-Binding components and a Mediator Component to expose the EJB Service i mentioned , they way as you need, and apply any transformation/translation/error handling requiered.
- In both ways you can abstract the EJB message model from potential clients and also expose its functionality in a more canonical way (Message and Transport scoped).
- I would preffer a more ADMIN-Based user to answer this question.
- Same as 4
Please tell me if you need further help or examples.