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

encoded string can be obtained by invoking the getHeader() method on the
HttpServletRequest object. The encoded string must then be passed to a
StringTokenizer object, and decoded using an appropriate decode method. We
utilized a separate utility class, Base64, for this purpose. This supplies the
decode and encode methods and is packaged with CTGTesterCCI.
For further details on HTTP basic authentication and Base64 encoding, refer to
the redbook Securing Web Access to CICS, SG24-5756.
The user ID and password from HTTP basic authentication are sent to the JSP
for output. However, they are not flowed to CICS. The code for doing this if using
an unmanaged connection factory is included in the source, but commented out.
The next section of code performs a JNDI lookup for our session bean, shown in
Figure B-25.
// lookup our session bean
Context ic = new InitialContext();
Object or = ic.lookup("java:comp/env/ejb/CTGTesterCCI");
CTGTesterCCI tester = null;
if (or != null)
{
CTGTesterCCIHome home = (CTGTesterCCIHome)PortableRemoteObject.narrow(or,
CTGTesterCCIHome.class);
tester = home.create();
}
Figure B-25 JNDI lookup and remote method invocation
We get a JNDI InitialContext and then perform a lookup using the JNDI name
java:comp/env/ejb/CTGTesterCCI. This is a local JNDI name that will be mapped
to the actual JNDI name of the session bean at deploy time. To indicate we want
such a mapping, we create an EJB reference in the Web deployment descriptor
with the name ejb/CTGTesterCCI.
Once we have looked up the object, we get the home interface of our session
bean using the narrow() method call of the RMI class PortableRemoteObject.
This method performs any operations necessary to allow us to invoke the bean’s
create() method and returns a reference to the session bean home interface.
We then call the create() method on this home interface to get a reference to the
remote interface we will use to invoke our business logic.
Next, we execute our business logic on the session bean and collect the results,
as shown in Figure B-26 on page 364.
Appendix B. Sample applications 363