Installing Comms: Lowering the Barriers, Day 2
By joesciallo on Apr 28, 2008
The subtitle of Installing Comms Suite, Day 2, ought to read "I'm my own worst enemy." After finally getting past the point of installing Application Server, Directory Server, Access Manager, and Web Server, as detailed here, I finally got on to the long-awaited installation of Comms products themselves, and then being able to run the
comm_dssetup.pl script, which would apply the necessary schema for Comms to the Directory Server. Ah, at last, smooth sailing ahead.
Except that the script would not recognize my Access Manager installation. When choosing my Schema type as Schema 2, (which the Single Host Deployment Example uses), the script responded:
Please enter the Schema Type (1, 1.5, 2) : 2 Access Manager has not been configured for this new user/group suffix You can opt to continue, but you will not be able to use features that depend on Access ManagerHmmm, odd I thought. No problem, I'll just uninstall Access Manager and reinstall, just to be sure. One uninstall/reinstall, same result. Twice, same result. Okay, third times the charm. Same error message.
Then I actually stopped to read a little burp of an error in my term window:
has_naming_context_ds6 get-suffix-prop result: execv(/opt/bits/jre1.5.0_15/java/bin/java): No such file or directoryA little poking around, and sure enough, I was setting a bogus
comm_dssetup.plwas complaining! Naturally, when I fixed this I was on my merry way.
Next step: Running all those Comms configurators. Where's the easy button when you need it?