The HATS entry servlet is set to load on startup and seems to initialise the
runtime.  So if our project is a HATS web project we don't seem to need to
initialise the runtime.  But what about a non-HATS web project?  What if we
want to use integration object in our own (non-tool generated) web
services - or making web services out of our own stateless session EJBs that
call IOs?

There is a lack of clarity in the documentation about the initialisation of
the HATS runtime, be it in the EJB container, or the Web.

Can someone make it clear how the initialisation should work.  We are trying
to workout the best implementation for using our own custom web services
that have to call integration objects.

Do we use static code in the class to initialise the HATS runtime once?

What happens if two calls try to initialise the runtime?

Do we initialise it on every call?

If so, that's a bit expensive isn't it?


"KBDRand" <kbdrand@hotmail.com> wrote in message
news:cn349j$59kk$1@news.boulder.ibm.com...
>I need to create my own Java bean and expose it as a web service, and so I
> want to call the Integration Object (IO) from my bean.
>
> The online documentation explains how to call an IO from a Servlet/JSP or
> EJB, but not how to call it from a plain Java Bean. anyone have any
> pointers?
>
> My biggest point of mis-understanding (confusion) is the initial setup for
> the IO. Based on the EJB call (which is closer than the Servlet since my
> bean doesn't have a context object) this is what I'm going to try:
> com.ibm.hats.util.Ras.initializeRas(this);
>
> com.ibm.hats.util.LicenseManager.getInstance();
>
> com.ibm.hats.runtime.connmgr.Runtime.initRuntime("", this);
>
> I will then instantiate the IO and call 'processRequest()' to run the IO.
>
> Should that work, or should I be doing something different?
>
>

[ Post a follow-up to this message ]