Monday, August 17, 2009

Adding OES to a SOA 11g Domain - Part 3

Greetings from Amsterdam. After a trans-Atlantic flight and a 13 hour work day, more progress to report on getting OES to protect a SOA 11g domain.

First, a clarification from a previous post. When installing the SM, make sure that the ARME listening ports are not 8001. This is because this is the default port for the managed server. This is why I explicitly chose 28000 and 28001 (i.e. not 8000 and 8001). Apologies for not being clearer.

Next, a Linux only issue that we encountered that caused some serious consternation. The script calls out to BEA_HOME/wlserever_10.3/server/bin/ In this script, the MEM_ARGS are set to some vendor specific values, but regardless of the JDK vendor the values are too small to start the 11g admin or managed server. The work around is to make sure that the original MEM_ARGS in the are preserved and not overridden by the If you don't do this, the server will start, but will soon die with an OutOfMemory Exception.

Finally, and this was a tricky one. If you want to access Enterprise Manager, then the user needs to be in a role called soa_admin. If you don't then you'll be able to log into the em console, but you won't be able to access any of the composites. This one is made especially tricky because EM is not making an isAccessAllowed call, but rather an isCallerInRole which is not discoverable.

Hopefully, this is the last post on my somewhat epic (all great stories are trilogies) quest to OES enable 11g SOA Domain. I'm almost there with the OES/BPEL integration, and should have it posted during some future bout of insomnia later this week.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.