This is the most common error one gets after he configure his bpel/humanworkflow with OID.
The error received are
while trying to log in to bpel console
http://localhost:port/BPELConsole
“No domains accessible to the user logged in.”
and while trying to log in to bpel admin
http://localhost:port/BPELAdmin
User does not have enough privileges to access the Admin Console
There is a very simple solution to this.
The configure.bat command changes the jazn.xml file in home conatiner and not in oc4j_soa container.Our application is running on oc4j_soa container.So to overcome this problem.
Just take the backup of jazn.xml and rename the jazn.xml file in
SOA_HOME\j2ee\oc4j_soa\config to some other file name.
NOw copy and paste the jazn.xml from SOA_HOME\j2ee\home\config to SOA_HOME\j2ee\oc4j_soa\config folder and restart the server.
Thats it now you will be able to log in to bpel console and bpel admin console.
Now you can try to create your own user and assign them roles to log in to the console.
YOu can also grant permission to the user by using jazn shell.
To open up jazn shell
First navigate to $ORACLE_HOME/j2ee/home directory
set ORACLE_HOME
Start the jazn shell via the following command
java -Xbootclasspath/a:/$ORACLE_HOME/bpel/lib/orabpel-boot.jar -jar jazn.jar -shell
AbstractLoginModule username: oc4jadmin
AbstractLoginModule password: welcome1(provide your own password)
After the shell prompt has started you can now grant permissions/create users.
The following example will grant permissions to user orcladmin to the default domain in the jazn.com realm.
grantperm idc -user orcladmin com.collaxa.security.DomainPermission default all
You may get following error while creating or granting users
com.collaxa.security.DomainPermission: Permission class not found.
This is because
Changes made through jazn admin tool are reflected in file located $SOA_HOME/j2ee/home/config/system-jazn-data.xml but the application is using file located in oc4j_soa directory. Due to this JAZN tool is giving "permission class not found" error for any standard BPEL related permissions.
To overcome this issue you need to replace the
$OH/j2ee/home/config/system-jazn-data.xml with $OH/j2ee/oc4j_soa/config/system-jazn-data.xml
and $OH/j2ee/home/config/system-application.xml with $OH/j2ee/oc4j_soa/config/system-application.xml
No comments:
Post a Comment