LDN - Luminis Developer Network

I hated getting those when I would create a new connector.

The unsupported OID can sometimes be a result of missing CGF configuration data, and/or start up sequences. It essentially means that the portal can not connect to a parameter called configURL. Go through these steps to verify that the connector is set up properly.

For this example I'll use a connector called – bssa – yours could be called mail, ssb, banweb, report, etc.

CPIPCONNECTOR.PROPERTIES file:

First verify that the connector is listed in the master connector list.
Look at this file :

/opt/luminis/webapps/cpipconnector/WEBINF/config/cpipconnector.properties

look for this line (should be at the top) :
property.files = comexp.properties,messengerexpress.properties,bssa.properties

Verify there is a bssa.properties listed in the comma separated list.

Depending on what connectors you have, this list might be long, it should also be on one line (ie - no line breaks) if your connector is not listed, simply add ,bssa.properties to the end of the list (changing bssa to your connector name) save that file

While in this directory, simply look at the files and verify there is indeed a bssa.properties file as well as a bssa.xml file. These two files make up the GCF connector.

CONFIGMAN ES.SYSTEMS SETTINGS

The second major item to check is the internal configuration using configman.
From the command prompt type -
configman -g es.systems

Configman will list the es.systems property setting, which should be a set of space delimited connector names. It could look something like this - sct bssa

If your connector is not listed follow this procedure –

configman –s “sct bssa”

Copy all of the connectors listed on your system and paste them between double quotes above. The connector names will be space delimited. Add yours to the end.

CONFIGMAN CONNECTOR SETTINGS

Next check for the actual configman settings for that connector –
configman –g es.bssa.* (again changing bssa for your connector name)
you should get something that looks similar to this :

es.bssa.configURL=http://myfuture.messiah.edu:8008/cpipconnector/bssa/GetConfigVersion2
es.bssa.configattempts=60
es.bssa.configsleeptime=10000
es.bssa.shortcircuitlogin=false

if you do not –then you’ll have to set each of these options with something like –

configman –s es.bssa.shortcircuitlogin false (notice the spaces, no = sign when setting these from the command line) Obviously you’ll change the domain name and the port and the
connector name in the configURL setting.

If all of that was setup properly (meaning you did not make any changes above), copy the configURL setting and paste that into a browser.

You should see a long list of what looks like parameters:

authenticate=http%3A%2F%2Fmyfuture.messiah.edu%3A8008%2Fcp
ipconnector%2Fbssa%2FAuthenticate&authenticateOIDlist=1.3.6.1.4.1
.4409.1.1.4.2&createonlogin=0&deauthenticate=http%3A%2F%2Fmyf
uture.messiah.edu%3A8008%2Fcpipconnector%2Fbssa%2FDeauthenti
cate&deauthenticateOIDlist=1.3.6.1.4.1.4409.1.1.6.1&lastactive=http
%3A%2F%2Fmyfuture.messiah.edu%3A8008%2Fcpipconnector%2Fbs
sa%2FLastActive&lastactiveOIDlist=1.3.6.1.4.1.4409.1.1.5.1&sessionP
laceHolder=sessionPlaceHolder&sendcpsession=true&sendtimeout=fals
e&sendlogin=true&useSISCredentials=false&usePDSCredentials=false
&sendimmutableid=true

These are the parameters from your bssa.properties file. If you get an error or a blank screen, something is not configured properly.

At this point all the internal / backend items should be configured properly, so please restart luminis –
cpstop –a
cpstart

When Luminis comes back up – check that configURL in your browser again.

If it is still blank, try this url to initialize the connector, occasionally the startup sequence misfires and the connector webserver isn’t up and running when Luminis checks for each connector configuration. When that happens, Luminis then thinks the destination is unreachable.

Log into your portal as an admin, then paste this url in (changing it to work with your portal and connector

https://myfuture.messiah.edu/cp/ip/config?sys=bssa

This should initialize the connector and (hopefully) reset Luminis.
Test the GCF connection with a link from within Luminis.
If this still does not work, the .properties files and .xml files will have to be checked for syntactical errors.

Hope that helps

-Jon

Joyce,

Did you ever get the cpipconnector to work as SSL on port 8443? What version of Luminis are you on? The info in FAQ 1-3F9V5I doesn't work for LP 4.2... I *think* it's supposed to work for LP 4.3, but I haven't been able to get it to work.

We ended up combining the cp & cpipconnector tomcat web servers so both run on port 443... see Sungard FAQ 1-54G63I, but now we're on LP 4.3 and we have one GCF SSO that looks like it's not encrypted... I'm trying to get FAQ 1-3F9V5I to work but haven't quite got it working yet...

If you got FAQ 1-54G63I to work, were there any tricks you had to do to make it work?

Thanks...Ginny Lee
Colorado School of Mines