Novell ACCESS MANAGER 3.1 SP1 - AGENT GUIDE Manual page 40

After the installation of J2EE Agents, the security policy refers to the
weblogic.policy
There appears to be a bug in WebLogic 9.2 that prevents the Administration Console applications
from functioning with the default permissions in the
some of the Java 2 permissions for the agent to be explicitly set when the security manager is
enabled. The only workaround Novell has found is to grant Java 2 permissions to everything.
The
<AGENT_HOME>/weblogic.policy
grant {
java.security.AllPermission
};
This should not add any more security risk than running WebLogic without the security manager
enabled, which is the default configuration for WebLogic.
Configuring the Login
To configure the login, you can use either use a script or the WebLogic Administration Console:
"Using a Script to Configure Login" on page 40
"Using the Administration Console to Configure Login" on page 41
Using a Script to Configure Login
1 Start WebLogic.
2 Execute the WebLogic scripting tool. Specify the command appropriate for the platform:
Linux:
Windows:
3 To the command, add the appropriate parameters to execute the
Separate each parameter with a space. Running the script without additional parameters prints
the required parameters.
Parameter
WebLogic administrator
username
WebLogic administrator
password
Domain name
Server name
Hostname and port
40 Novell Access Manager 3.1 SP1 Agent Guide
file.
WL_HOME/common/bin/wlst.sh
WL_HOME\common\bin\wlst.cmd
Possible Value
weblogic
password
base_domain
AdminServer
localhost:7001
weblogic.policy
file contains the following lines.
Description
The name of the administrator that
you specified when you installed
WebLogic.
The password for the specified
user.
Specify the WebLogic domain
name.
By default, WebLogic names the
server AdminServer. If you
changed this name during
installation, specify your name.
The host and port are separated
with a colon.
<AGENT_HOME>/
file. This bug also prevents
script.
weblogic_config.jy