Forum Discussion

haeoraki_127471's avatar
haeoraki_127471
Icon for Nimbostratus rankNimbostratus
Mar 05, 2004

Please let me know.

The following is the sequence of general procedures to use when setting up the interaction between a CORBA client application and the iControl components.

 

 

Create an object reference to the ITCMPortal::Portal interface on a specific target system. The only required information is the name or IP address, and the port that the Portal is using for the system you want to control. Note that you must use port 683.

 

 

Q1. 'specific target system' means my development machine and 'the system you want to control' is BIG-IP machine, I think. Right?

 

 

Q2. Under /shlib directory, libOB.so, libOB.so.4.0 and libOB.4.04 are AcusORB?

 

 

Q3. If ITCMPortal Object is on BIG-IP, how can I get the ITCMPortal Object without IOR of the object? To my thinking, only IP and Port information is not enough. If possible where can I get the example?

 

 

Q4. ITCMPortal Object is running on BIG-IP machine which I want to control. ITCMPortal is in /usr/local/corba/bin. Using telnet program like SecureCRT, I connect to BIG-IP and run ITCMPortal at command line like this : ./ITCMPortal

 

But ITCMPortal is shut down soon. What's wrong?
dev
devops
iControl
v4
  • Joe_Pruitt's avatar
    Joe_Pruitt
    Mar 06, 2004
    A1: "Specific target system" and "the system you want to control" are both the BIG-IP.

     

     

    A2: We are using ORBacus as our CORBA implementation.

     

     

    A3: ITCMPortal is our Server based CORBA ORB. You need to have server address and port to be able to build a corbaloc reference to it. The format is "corbaloc:::/ITCMPortalObjectFactory". The client application must use a corbaloc reference to connect to the server object on the client system.

     

     

    A4: I think you are missing the point. You should not be running any client code on the BIG-IP. The ITCMPortal deamon is controlled by the BIG-IP and should not be run on the command line. It should be treated as a server based daemon and turning it on and off are to be done by the "bigstart" script on the BIG-IP. But, the daemon is running by default so you should have no need to log onto the BIG-IP in a shell session to work with our CORBA interfaces.

     

     

    I'll try to sum everything up to get you going.

     

     

    1. Unzip the SDK.

     

    2. Configure your environment per the documentation.

     

    3. cd /sdk/support/c++ (or java)

     

    4. Make the samples.

     

     

    Basically what this does is compile the idl into client stubs and compile support libraries from the idl bindings. You also need to use our included ITCMConnection class in the sdk/support/c++/clientlib directory to handle the authentication requirements.

     

     

    The source for all of this is included in the SDK. This should get you going on the procedure to develop a client side application. From this point you can take our support code and integrate it into your build environment.

     

     

    As a side note, the CORBA interface is much more complicated to configure and run from a development environment. I would recommend you look into our SOAP interface as that is what the vast majority of our customers have chosen for their app development.

     

     

    Also, let me reiterate that you should not be running any code on the BIG-IP that isn't already installed and running on there.

     

     

    -Joe