Based on the oxid returns the JISession (and thus the COM Server) associated with it. This is required, since there are
cases where a different JISession may be passed in JIObjectFactory for an JIInterfacePointer which does not belong to this JISession.
Under those scenarios, the COM factory will create a new instance of a JISession and associate that Interface pointer with the session.
But that is not the right approach as a COM Server for that interface and thus a session might already exist and these have to be tied together.