LDN - Luminis Developer Network

We have 2 INB app servers set up with load balancing and our original implementation had the banportals.config file hardcoded to 1 of the 2 servers. That worked fine until we had to take that particular server down :) So I just 3 weeks ago went through this so I'll try to remember what we did.

When you get these errors - are the channels themselves working? Or you get this error when you click and its supposed to open INB from within the channel. And I'll just ask - which particular channel are you testing out - they all seem to behave differently. Some are pretty much static content with links into Self Service and INB, others are actual informational and load / display content from Banner (Advancement channels in particular).

The OID error can be the restult of a couple different things. I'll go through the list of things I have, I apologize if you know this already or have tried all of this -

• check the logs - there are 2 $CP_ROOT/products/sso/logs/cpipconnector.log and $CP_ROOT/products/ws/https-cpipconnector/logs/errors (and access if you want), there might be clues. Typically the cp.log will have simply the OID message in it you had on the screen. You could bump that up to debug if you wanted for more info - edit the log4j.properties file in $CP_ROOT/config and change the rootLogger from ERROR to DEBUG. This will take effect about 30 seconds after you save it and will spew forth more than you ever wanted to know. Its important to look at the system clock when you test this way to help you narrow down the portion of the debug dump, otherwise you're weeding through transactions that have nothing to do with your testing.
• could be the user doesn't have the connector permissions (this will show up in debug mode above). You can add it with this for everyone -
  cptool sync password -add cpip XXXXX (where XXXXX is the connector name you created - probably inb or ssb)
  or add it to one person with cptool set user jwheat ExternalAccount='XXXXX|jwheat|'
• could be easily solved by simply restarting your cpipconnector server, then bouncing luminis. Luminis tries to connect (ping) each cpip service as it comes up and sometimes if its not up when luminis pings - you get that message.
• could be something mistyped in the .properties and/or .XML file - the most popular issue is trailing spaces in these files. Even on blank lines make sure there's no spaces at all at the end of lines
• also check your cpipconnector.properties file to verify you spelled your connector right
• check configman -g es.systems to make sure its there
• check configman -g es.xxxxx.* to make sure they're all set right
• could be that the system end of the connector is returning something that the luminis side isn't expecting. Make sure wherever you're sending your link to works manually. For example - hit the goksso url and I _think_ you'll get a login box - make sure that works.

initialize the connector with this -
http://portal.college.edu/cp/ip/config?sys=XXXXX

that will yield a blank screen

Test the connector by hitting the configUrl listed in : configman -g es.xxxxx.configURL - it'll look something like -
http://portal.college.edu:8008/cpipconnector/XXXXX/GetConfigVersion2

That should return a querystring looking thing that at quick glance looks like garble. If that happens, the .properties and .xml files are good and the connector is set up right

then give it a whirl.

I think that's all I have for testing. If you do all that and it still doesn't work - I'm stumped.
Good Luck
-Jon