IPS- IAS integration

Question

Hi
I am faced with a problem related to IAS 6.0 SP2 and iPlanet Portal
Server 3.0 SP2. I have deployed the beans on IAS and can access it from
a rich client.
I've servlets running in IPS and from these, I want to access the beans
on IAS. I'm getting an unsatisfied link error. The exception thrown is :
[03/Jul/2001:14:37:02] info (15110): PortalInterface: init
[03/Jul/2001:14:37:09] failure (15110): Internal error: exception thrown
from the servlet service function (uri=/PortalInterface):
java.lang.UnsatisfiedLinkError: specialLoadClass, Stack:
java.lang.UnsatisfiedLinkError: specialLoadClass
at
com.sun.corba.ee.internal.util.JDKClassLoader.loadClass(JDKClassLoader.java:58)
at
com.sun.corba.ee.internal.util.JDKBridge.loadClassM(JDKBridge.java:180)
at
com.sun.corba.ee.internal.util.JDKBridge.loadClass(JDKBridge.java:83)
at javax.rmi.CORBA.Util.loadClass(Util.java:215)
at javax.rmi.CORBA.Util.createDelegateIfSpecified(Util.java:306)
at <Unloaded Method>
at
javax.rmi.PortableRemoteObject.createDelegateIfSpecified(PortableRemoteObject.java:182)
at <Unloaded Method>
at
com.iplanet.portalserver.api.SabreFlightDetails.getPriceAvailabilityInfo(Compiled
Code)
at
com.iplanet.portalserver.api.SabreFlightDetails.getSabreFlights(SabreFlightDetails.java:74)
at com.iplanet.portalserver.api.PortalInterface.doPost(Compiled
Code)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at
com.netscape.server.http.servlet.NSServletRunner.Service(Compiled Code)
I've set classpaths for the rich client in kjs and also in jvm12.conf of
IPS 3.0. But going by the rich client examples given with IAS, like the
converter client example, we have to set
a LD_LIBRARY_PATH as in runclient.sh. There is no place in IPS where we
can set the LD_LIBRARY_PATH. Is that the reason ?
I would appreciate your thoughts on this issue.
Thanks

Answer 1

Hi Aslam
You will use class maps to divert the traffic to the module. Here are some basic steps.
!Identify the traffic that needs to be diverted to the IPS SSP.
   access-list IPS permit ip any any
!Classify the traffic using a class map.
  class-map IPS
  match access-list IPS
!Specify the action to be taken on the traffic using a policy map. !Since there is already a policy map attached globally in the FW, !the class-map defined above will be added here !only.
policy-map global_policy
class IPS
ips promiscuous fail-close (or fail-open)
Once that is done, the rest of the configuration needs to be done on the IPS using CLI or preferrably the IDM.
HTH. Please rate if useful.
Zubair