Weblogic - Administration Server

> (Weblogic|Fusion Middelware|FMW)

1 - About

The central control entity of a domain which maintains the domain's configuration objects and distributes configuration changes to Managed Servers.

The Administration server is a Server that contains administration java components that enable administration of a single or multi-node (that is, distributed) BI domain.

Specifically the Administration Server contains the following java components:

Advertising

3 - How to

3.1 - Start

3.1.1 - With node manager

See node manager. When node manager starts, it will call a start script. The default script is startWebLogic.(cmd|sh). You start it from the command line (see section below). The start script is defined in the configuration file See StartScriptName property

3.1.2 - With the command line

Before you can start the Weblogic AdminServer, the database that you specified during installation must be running, or JDBC errors prevent startup.

To start the Administration Server and all Oracle Business Intelligence Java Components included, start a shell and change to the directory to MW_HOME\user_projects\domains\bifoundation_domain\bin. Then, run the following command (which requires the administrator user name and password):

  • For Windows
startWebLogic.cmd

You can also stop the Java components from the MS-DOS window in which they were started, if you press Ctrl+C.

  • On UNIX
./startWebLogic.sh
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:

See the section below to bypass the user name password prompt

<Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Advertising

3.2 - Stop

The same process than the section above but with this command:

  • Windows:
stopWebLogic.cmd -stop
  • Unix:
./stopWebLogic.sh

3.3 - Status

If the Administration Server is running, then the Oracle WebLogic Server Administration Console login page is displayed.

On Linux:

ps -elf|grep Dweblogic.Name=AdminServer

If you get an output like that it means that an AdminServer is running.

/u01/app/oracle/product/fmw/jrockit_160_29_D1.2.0-10/bin/java 
-jrockit 
-Xms256m 
-Xmx1024m 
-Dweblogic.Name=AdminServer 
-Djava.security.policy=/u01/app/oracle/product/fmw/wlserver_10.3/server/lib/weblogic.policy 
-Dweblogic.ProductionModeEnabled=true 
-da 
-Dplatform.home=/u01/app/oracle/product/fmw/wlserver_10.3 
-Dwls.home=/u01/app/oracle/product/fmw/wlserver_10.3/server 
-Dweblogic.home=/u01/app/oracle/product/fmw/wlserver_10.3/server 
-Dcommon.components.home=/u01/app/oracle/product/fmw/oracle_common 
-Djrf.version=11.1.1 
-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger 
-Ddomain.home=/u01/app/oracle/product/fmw/user_projects/domains/bifoundation_domain_di 
-Djrockit.optfile=/u01/app/oracle/product/fmw/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt 
-Doracle.server.config.dir=/u01/app/oracle/product/fmw/user_projects/domains/bifoundation_domain_di/config/fmwconfig/servers/AdminServer 
-Doracle.domain.config.dir=/u01/app/oracle/product/fmw/user_projects/domains/bifoundation_domain_di/config/fmwconfig 
-Digf.arisidbeans.carmlloc=/u01/app/oracle/product/fmw/user_projects/domains/bifoundation_domain_di/config/fmwconfig/carml 
-Digf.arisidstack.home=/u01/app/oracle/product/fmw/user_projects/domains/bifoundation_domain_di/config/fmwconfig/arisidprovider 
-Doracle.security.jps.config=/u01/app/oracle/product/fmw/user_projects/domains/bifoundation_domain_di/config/fmwconfig/jps-config.xml 
-Doracle.deployed.app.dir=/u01/app/oracle/product/fmw/user_projects/domains/bifoundation_domain_di/servers/AdminServer/tmp/_WL_user 
-Doracle.deployed.app.ext=/- 
-Dweblogic.alternateTypesDirectory=/u01/app/oracle/product/fmw/oracle_common/modules/oracle.ossoiap_11.1.1,/u01/app/oracle/product/fmw/oracle_common/modules/oracle.oamprovider_11.1.1 
-Djava.protocol.handler.pkgs=oracle.mds.net.protocol 
-Dweblogic.jdbc.remoteEnabled=false 
-Dbi.oracle.home=/u01/app/oracle/product/fmw/Oracle_BI1 
-DEPM_ORACLE_HOME=/u01/app/oracle/product/fmw/Oracle_BI1 
-Dweblogic.MaxMessageSize=50000000 
-DEPM_ORACLE_HOME=/u01/app/oracle/product/fmw/Oracle_BI1 
-DHYPERION_HOME=/u01/app/oracle/product/fmw/Oracle_BI1 
-DEPM_ORACLE_INSTANCE=novalue 
-Dhyperion.home=/u01/app/oracle/product/fmw/Oracle_BI1 
-DEPM_REG_PROPERTIES_PATH=/u01/app/oracle/product/fmw/user_projects/domains/bifoundation_domain_di/config/fmwconfig 
-Depm.useApplicationContextId=false 
-Doracle.biee.search.bisearchproperties=/u01/app/oracle/product/fmw/Oracle_BI1/bifoundation/jee/BISearchConfig.properties
-Dweblogic.management.clearTextCredentialAccessEnabled=true
-Doracle.notification.filewatching.interval=2000 
-Dweblogic.security.SSL.ignoreHostnameVerification=true 
-Dweblogic.security.SSL.enableJSSE=true 
-Dfile.encoding=utf-8 
-Doracle.ecsf.security.service=oracle.biee.search.security.BISearchSecurityService 
-Doracle.ecsf.configuration.class=oracle.biee.search.services.BISearchServiceConfiguration 
-Dxdo.server.config.dir=/u01/app/oracle/product/fmw/user_projects/domains/bifoundation_domain_di/config/bipublisher 
-DXDO_FONT_DIR=/u01/app/oracle/product/fmw/Oracle_BI1/common/fonts 
-Drtd.instanceName=RTD_AdminServer 
-Dem.oracle.home=/u01/app/oracle/product/fmw/oracle_common 
-Djava.awt.headless=true 
-Dweblogic.management.discover=true 
-Dwlw.iterativeDev=false 
-Dwlw.testConsole=false 
-Dwlw.logErrorsToConsole=false 
-Dweblogic.ext.dirs=/u01/app/oracle/product/fmw/patch_wls1036/profiles/default/sysext_manifest_classpath:/u01/app/oracle/product/fmw/patch_ocp371/profiles/default/sysext_manifest_classpath weblogic.Server

3.4 - Bypass the user name password prompt

To bypass the user name password prompt when starting domain Admin Server or any of its managed ones, you can do the following steps:

  • Create the “security” directory under the following location :
<MiddleWare_Home>/user_projects/domains/<Domain_Name>/servers/AdminServer/security
MiddelwareHome\user_projects\domains\bifoundation_domain\servers\AdminServer\security
  • Create a text file called boot.properties in the security directory with the following two lines:
username=weblogic
password=password
Advertising

4 - Support

4.1 - Log files

In case of Problem, you can see the message in the log file in the following directory:

\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

Example of log problem:

Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: 
Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied

5 - Documentation / Reference

weblogic/administration_server.txt · Last modified: 2018/03/26 11:09 by gerardnico