Niclas,
Okay - it sounds like you've covered the basics:
- You're using WebLogic 8.1SP4
- You haven't changed the default password of the GUEST.ADMIN user
Just to confirm on the second note - you shouldn't have had to change the password in your tomcat.conf, weblogic.conf or database as it should already be setup as the default of CHANGEME.
Were there any errors in your Install Log files - particularly on the OTM Web and App servers? You can find more info for verifying here:
http://www.otmfaq.com/forums/f23/how...d-no-errors-9/ (How do you verify your install had no errors?)
The next most common issue (which usually shows up in the log files) is that either the WebLogic jar files weren't able to be copied into the OTM installation, due to file permission issues. You can check this by ensuring that the following files exist on your OTM Web and App servers under <otm_home>/glog/gc3webapp/WEB-INF/lib/3rdparty/ :
- weblogic.jar
- webservices.jar
- xmlx.jar
Another possibility is that the OTM java security jars weren't able to be copied into the WebLogic directory by the root.sh script on the OTM App server installation. In this case, you should have the following files in your <bea_home>/weblogic81/server/lib/mbeantypes/ directory:
- gc3authenticator.jar
- gc3authorizer.jar
Finally, did you download and install all of the 3rd party jar files into OTM? These are actually required for full functionality, though Oracle won't allow them to be distributed with OTM, due to licensing issues.
If you can check these and report back, I'll help further.
Thanks,
Chris