CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

To show what the resource reference is bound to, it is necessary to open the
ibm-ejb-jar-bnd.xmi file. To view this file, from the J2EE Perspective Navigator
view, expand CTGTesterCCIEJB -> ejbModule -> META-INF, right-click
ibm-ejb-jar-bnd.xmi, and select Open. Click the Bindings tab to see the
Bindings pane.
To see the resource reference binding, from the Bindings pane expand
CTGTesterCCIEJB -> CTGTesterCCI -> ResourceRef ECI and click
ResourceRef ECI. As shown in Figure B-53, the resource reference ECI is
bound to the JNDI name eis/CICSA. This can be changed to a deployed
connection factory at deploy time. However, when testing we had to define a
connection factory in the test server with the JNDI name eis/CICSA so that this
reference would be valid and we could test using managed CICS connections.
Figure B-53 CTGTesterCCI bean resource reference binding
To see the JNDI name our session bean is bound to, from the Bindings pane click
CTGTesterCCI. Figure B-54 on page 386 shows that our bean has a suggested
JNDI name of ejbs/CTGTesterCCI. This is the same name we used in our Web
deployment descriptor as the JNDI name of the session bean, in Figure B-46 on
page 379. Because these names are the same, the servlet will look up our
session bean using the same JNDI name as it was bound with. Therefore the
servlet will find our session bean.
Appendix B. Sample applications 385