Core Content Only

Archive for August, 2009

When attempting to install or uninstall Content Server or the related services on a Windows box you may occasionally run into some problems. Whatever the scenario is, you may get to a place where you need to manually uninstall the services.

Note: As you will recall, uninstalling Content Server is generally a very simple task of finding the bin directory on the command line and issuing this command:

Installer UnregisterAll

This should cleanup everything. When it doesn't, you can attempt these maneuvers:

-cs install-\bin\IdcServerNT -uninstall -cs install-\admin\bin\IdcAdminNT -uninstall -ibr install-\bin\IdcRefineryNT -uninstall

If this doesn't work, you can also try this beauty:

sc delete "service name"

And finally, you can go hack the registry at your own risk:

1. Open command prompt
2. Type "regedit"
3. Press enter
4. Navigate to 'HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services'
5. Find service name you wish to remove
6. Select it
7. Delete it

A question was asked on the Oracle ECM forums about what the various values for Release State meant. I knew which states some of the single character values represented, but not all of them. I was interested in finally finding out this answer for myself once and for all so I dug in. What follows is what I found as a result:

N
apStateNew
This item was newly added to the system

Y
apStateCurrent
This refers to the revision status of the content item (so it's the most recent revision of the content item)

O
apStateOld
This refers to the revision status of the content item (so it's not the most recent revision of the content item)

E
apStateWorkflow
This means the content items is currently in a workflow

R
apStateProcessing
This means the content items is currently being processed by the indexer

U
apStateUpdate
This means the content item is being updated

I
apStateIndexing
This means the content items is currently being indexed

A recent client has users who were getting frustrated about the case sensitivity of the UCM logins. Their old system did not have this restriction (feature?) and they wanted this removed. The more of these types of things you remove the less secure the login becomes, but depending on each situation the risk/reward analysis plays to either side of the fence.

This turns out to be a fairly easy task to accomplish. First, the users in question need to be changed to "Global" in the User Admin applet.

NOTE: This means you cannot perform this action with SYSADMIN.

Having switched the appropriate users to Global, you need to add this setting via Admin Server (under General Configuration) or directly to the confing.cfg file. Once added, do not forget to restart the services.

AllowCaseInsensitiveLogin=true