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.
 
 
Deleting a WebLogic domain can be accomplished through a series of manual tasks.  There is no script or application to run that will accomplish deleting a domain or removing a domain.  The good news is the steps are fairly short and easy.  In the sample steps below it is assumed that your domain is named base_domain.

  1. Delete the domain folder (meaning base_domain) under %WL_HOME%/user_projects/domains
  2. Delete the domain folder (meaning base_domain) under %WL_HOME%/user_projects/apps
  3. Remove any references to the domain in the %WL_HOME%/domain-registry.xml file
  4. Remove any references to the domain in the file WL_HOME/common/nodemanager/nodemanager.domains
  5. Remove any schema/database associated with the domain
 
 
Oracle recently released WebLogic 12c.  I have had a lot of customers ask about running ECM products and ADF on the newly released WebLogic Application server.  We talked with Oracle and basically the current releases of 11.1.1.5 ECM Products and ADF are not certified for WebLogic Application Server 12c.  Also, it does not look like 11.1.1.6 will be certified either.

In short, 12c looks neat and there looks to be a lot of new features but those toys are not currently part of our playground.
 
 
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.

 
 
Previously we showed how to install WebLogic Application Server 11gR1 PS3 (10.3.4) using the graphical mode installation.  You can also perform the installation in “Console Mode” which may be helpful if you only have terminal access (such as ssh).

Once you have download the generic installation jar you can execute a command line this to kick off the installation:
java -jar wls1035_generic.jar -mode=console
Upon executing this command you will basically get a text based version of the graphical installation.  You can enter Next to move to the next step or enter numeric keystrokes to toggle selected options.  Once all your choices are mad you’ll be presented with a text-based progress bar.  Once installation is complete you’ll be notified and control of the command line will be returned to you.

The installation is very fast!

Also, take a little bit to check out silent install info.
 
 
Last Friday (Jan 14) Oracle released Patch Set 3 for fusion middleware.  The blogo-sphere has picked this up already and a surprising amount of information is already available.  Here is a list of reference links:

Download WebLogic

 

Redstone Content Solutions