This content has been marked as final. Show 5 replies
I have not get it up and running.
You guy's been busy, It's a much more nicer interface.
I have not yet been able to test all functionality, but I plan to do that soon.
Well, what was the problem then,
The first time I used config.sh script to create a vanilla Weblogic Server, I answer no on everything ( fix database and App server later). That was obviously not a smart move, but I would like to to it the hard way to see what happens.
After some deep digging in the documentation (RTFM) I find that TSAM now need Oracle JRF, so after install of that and extend my TSAM Server I was able to deplay and up and running. But then I run into next problem, since I did not choose to select any database I could not log on. The user admin or any password was not recogniced. At this time at night I become lazy and reinstalled TSAM and this time selected Oracle as database. But I choose to deploy it manually. Then it was rocking.
So, my solution was to download Oracle JRF and extend my WLS Server.
And install TSAM again and choose Oracle during the installation, then it was cooking.
Here is a response to your issues from R&D:
- I think it should be a lot more clear that TSAM need Oracle JRF, a
good section for would be in owerview or in requirements.
Yes, we missed this part and will add it.
- And maybe some note how to create super-user admin if you choose to
install Oracle after or whatever.
We do provide a tool to deploy TSAM to an existing database (including creating super-user admin): http://download-llnw.oracle.com/docs/cd/E15261_01/tsam/docs11gr1/deployment/deploy.html#wp1061763
- Then I read that you have to edit web.xml file if you using WLS. Ok,
no problem with that. But what should be changed and to what. Maybe even
some info how to unpack and pack the ear file. You are dealing with
Tuxedo and C people (like me), old and grunchy. Even if most of us fix
easy, could someone use some unnecessary time to find out. Guess who
takes the blame?
In most cases end user doesn’t need to edit the web.xml file. We intend to remove the description of manually edit web.xml to avoid unnecessary confusion.
Again, thanks for your input and we are working to resolve these issues.
Oracle Tuxedo Chief Architect