It looks like you didn't enable LDAP through the Windows ADMIN client for the server you are now trying to set up.

Log into your server, Right click on it and select "System Parameters". Click the Login Information tab and make sure the Enable LDAP box is checked.

You will need to recycle arssockd once this change is made.

Sounds like some certs may have expired/changed.

This would be a great question for your IBM Software Rep.

On multiplatform, OnDemand is typically licensed by user, not CPU.

Version 7 UUIDS weren't a thing when the feature was added to CMOD.

Quote from: Nils Engerby on June 05, 2024, 03:08:20 PM
Thanks Justin,

Sorry to correct you but UUIDs are 128-bit and the dashes are in very specific positions. :) Nicely described on Wikipedia: https://en.wikipedia.org/wiki/Universally_unique_identifier

After testing the export/reload approach on some 100 thousand documents it is quite clear that the CMOD generated UUIDs are version 4 (random), indicated by the number "4" in the first position of the third group (xxxxxxxx-xxxx-4xxx-xxxx-xxxxxxxxxxxx). Version 7 would probably have been a better choice to improve the database indexes. Or you could by all means identify it as version 4 and still use a combination of timestamp and randomness, which is what we have done in our UDF tests to update existing data.

Oh well, it's never easy, is it? Heads or tails ... :-\
//Nils

Probably the wrong version of java on aix

That isn't correct. Base DN needs to be DC=XXX,DC=XXXX,DC=XXXXX,DC=com

Your IBM Consultant will reach out to you.

You are missing the ARS_LDAP_BASE_DN parameter. Can you share that?

I can't speak for all of IBM -  8) - but it's fine.  I'd say our opinion is have a perfect backout strategy if the OS upgrade fails.

ok... This comment:

"The following components are running on this Linux RHEL 7.9 server:
IBM Content Navigator 3.0.11
IBM Content Manager OnDemand 10.5.0.5
IBM Websphere Application Server 9.0.5.13 ND?"

This led me to believe everything is on the same server.... Sounds like you have a good distribution, so all is well.   BTW: I just upgraded a server this week from 7.9 to 8.9. No issues. Your mileage may vary.

While I think I understand what you are driving at, what does support mean to you in this case? Ideally, we always recommend new hardware/VMs. It is so much safer of a process. We also never recommend having all these components on the same server. ICN should be separate from the CMOD server.

https://www.ibm.com/docs/en/content-navigator/3.0.15?topic=navigator-whats-new-in-content-3015

Off the top of my head, not sure.

Probably a config error. Double check all required LDAP attributes are defined in the ars.cfg correctly. You can also enable LDAP trace on the server. There is likely another error somewhere else you might have missed. I would enable trace, stop the server, remove existing trace file, start the server and then test. This way you have a clean trace. L2 will need that anyway if you open a case.

There is not.

arsdoc get Assumes every "hit" is a document, so if you have 10 hits you are going to get 10 documents, regardless of the fact that they may all be the same document. 

https://www.ibm.com/docs/en/cmofm/10.5.0?topic=parameters-disable-logoff-password-change-x

look in the windows customization guide - There is a flag you can pass to start the client which will disable the change password option.