|
| Hi ...
I did set the value of CS_HOME in the setenv.bat file to point to the cloudscape database. It still did not work. I even reconfigured the portal server to work with MS SQL Server to see if this problem was specific to the cloudscape database. The set of S
QL statements adding the attributes to the database works perfectly fine as stated in the discussions above. But the restart of the portal server does not make available the newly added attribute.
I had to run the enable-security-ldap task again with the new attribute pre-filled in the respective wmmXXXXX.xml files. Then i was able to get it to work. But - this is possible in a sandbox environment like in mine. I do not want to do this in the actua
l production environment.
Theoretically, whatever I did should work - but I cant seem to figure out why it does not.
Any help would be appreciated.
thx
shyam
|
|