What is the sysadmin user for in WebCenter Content 11g?
The primary administrative user ID in WebCenter Content 11g out-of-the-box is the weblogic user. This user and password is created when the WebLogic Domain is created.
So what is that sysadmin user in the User Admin Applet? And what is the sysadmin password?
Out-of-the-box WebCenter Content uses the Oracle WebLogic Server User Store to manage user names and associated passwords. Typically, user management is handled in the Oracle WebLogic Server Administration Console instead of the WebCenter Content User Admin applet. If you create a user only through WebCenter Content User Admin Applet Oracle WebLogic Server does not recognize that user. These kinds of users are called local users.
The sysadmin user can be used to run the stand-alone administration applets. Before you can do that you need to use the User Admin Applet to change the default, randomly encoded password that the sysadmin user is created with.
You might also create local users for integration activities like web service calls or using UXIdcCommand.
If you need to change the memory allocation to your WebLogic administration server and/or managed server, the following guide will show you how. Note: This will raise the limit for both the WebLogic administration server and managed server. You can verify these settings by watching the server startup script. Optionally, if you are setting the memory for Oracle UCM, you can verify this setting on the System Audit Information page.
Windows
1. Open the domain environment cmd file:
<middleware home>\user_projects\domains\base_domain\bin\setDomainEnv.cmd
2. Locate the following remark, inside the cmd file: (‘Search’ -> “@REM IF USER_MEM_ARGS”)
@REM IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values
3. Directly after this remark, add the following line:
set USER_MEM_ARGS=-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
4. The portion of the file you have edited looks like this:
@REM IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values
set USER_MEM_ARGS=-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
if NOT “%USER_MEM_ARGS%”==”" (
set MEM_ARGS=%USER_MEM_ARGS
)
UNIX/Linux
1. Open the domain environment sh file:
<middleware home>\user_projects\domains\base_domain\bin\setDomainEnv.sh
2. Locate the following remark, inside the sh file: (‘Search’ -> “#REM IF USER_MEM_ARGS”)
#REM IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values
3. Directly after this remark, add the following line:
USER_MEM_ARGS=-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m - XX:MaxPermSize=512m
4. The portion of the file you have edited looks like this:
#REM IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values
USER_MEM_ARGS=-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
if NOT “%USER_MEM_ARGS%”==”" (
MEM_ARGS=%USER_MEM_ARGS
)
References
Note that the basic difference between Windows and UNIX/Linux regarding this issue is the use of the “set” command for the Windows environment.
Final Thoughts
This is certainly not the only way to accomplish this task, and it does affect all managed servers in the domain. However, if you’re running a dev box with plenty of memory it is the simplest and gives you the best “umph” when running your various instances with the least amount of work.