Please let me know.

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