WebLogic学习笔记－Domain

最新推荐文章于 2021-11-22 20:36:33 发布

原创最新推荐文章于 2021-11-22 20:36:33 发布 · 3.4k 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#weblogic #domain #server #credentials #file #library

OS、DB 专栏收录该内容

34 篇文章

订阅专栏

WebLogic Summary - Domain

WebLogic Server management and configuration services are based on JMX API from Sun Microsystems. The config.xml file is a persistent store for the managed objects that WebLogic Server creates and modifies during its executing using BEA implementation of JMX API.

There are 2 XML-Schema, one is for the main config.xml, and one for the security subsection:

http://www.bea.com/ns/weblogic/90/domain.xsd

http://www.bea.com/ns/weblogic/90/security.xsd

The schema are also located in a JAR file in the file system at:

BEA_HOME/weblogic90/server/lib/schema/weblogic-domain-binding.jar

Prior to WLS9.0, the config.xml was a repository for all configuration information. Now WLS subsystems are configured in subsidiary configuration files that are referred to by the central config.xml file. These subsidiary configuration files resides in subdirectories of the /domains/DOMAIN_NAME/config directory.

When the Admin Server starts up, it saves a JAR file named config-booted.jar that contains the configuration files. When you make changes to the files, the old files are saved in the configArchive directory under the domain directory, in a JAR file with a sequentially-numbered name like config-1.jar.

If you create config.xml by hand, you need to locate these credentials, encrypt them, and copy the encrypted credential into your config.xml file.

Security file needed for every server: SerializedSystemIni.dat

Security files only needed for the Admin Server:

DefaultAuthorizerInit.ldift, DefaultAuthenticatorInit.ldift, DefaultRoleMapperInit.ldift

All instances of WLS use a server root directory to store runtime data and to provide the context for any relative pathnames in the server’s configuration.

You can specify the path for the server root directory by –Dweblogic.RootDirectory=path, if you use NodeManager to start a WebLogic Server instance, you can specify a server root directory with the Root Directory attribute in the Admin Console.

If you did not specify a root directory in the Admin Console, then the server root directory is:

BEA_HOME/WL_HOME/common/nodemanager

(If any path cannot be found, the working directory will be the root directory.)

An sample config.mxl:

<?xml version="1.0" encoding="UTF-8"?>
<domain xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security
http://www.bea.com/ns/weblogic/90/security.xsd
http://www.bea.com/ns/weblogic/90/security/wls
http://www.bea.com/ns/weblogic/90/security/wls.xsd
http://www.bea.com/ns/weblogic/90/security/xacml
http://www.bea.com/ns/weblogic/90/security/xacml.xsd
http://www.bea.com/ns/weblogic/920/domain
http://www.bea.com/ns/weblogic/920/domain.xsd" xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<name>medrec</name>
<domain-version>10.3.0.0</domain-version>
<security-configuration xmlns:xacml="http://www.bea.com/ns/weblogic/90/security/xacml">
    <name>medrec</name>
    <realm>
      <sec:authentication-provider xsi:type="wls:default-authenticatorType"/>
      <sec:authentication-provider xsi:type="wls:default-identity-asserterType">
        <sec:active-type>AuthenticatedUser</sec:active-type>
      </sec:authentication-provider>
      <sec:role-mapper xsi:type="xacml:xacml-role-mapperType"/>
      <sec:authorizer xsi:type="xacml:xacml-authorizerType"/>
      <sec:adjudicator xsi:type="wls:default-adjudicatorType"/>
      <sec:credential-mapper xsi:type="wls:default-credential-mapperType"/>
      <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"/>
      <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
      <sec:name>myrealm</sec:name>
    </realm>
    <default-realm>myrealm</default-realm>
    <credential-encrypted>{3DES}usV0S9eAZZOoXBdumArMoaBrHXw5KYH5i9WZ0l9feo/XhvsOPvVCr1Dl1vO4swnl6+CZ55VqLFeZtNHUO7cFBgF1drCbnKzq</credential-encrypted>
    <node-manager-username>weblogic</node-manager-username>
    <node-manager-password-encrypted>{3DES}WdcpzbHSy/dpU/PCb5DQ0A==</node-manager-password-encrypted>
</security-configuration>
<server>
    <name>MedRecServer</name>
    <ssl>
      <name>MedRecServer</name>
      <enabled>true</enabled>
      <listen-port>7012</listen-port>
    </ssl>
    <listen-port>7011</listen-port>
    <listen-address>Ren</listen-address>
    <network-access-point>
      <name>MedRec Local Network Channel</name>
      <listen-address>localhost</listen-address>
      <public-address>localhost</public-address>
      <listen-port>7011</listen-port>
      <public-port>7011</public-port>
      <tunneling-enabled>true</tunneling-enabled>
      <two-way-ssl-enabled>true</two-way-ssl-enabled>
    </network-access-point>
</server>
<embedded-ldap>
    <name>medrec</name>
    <credential-encrypted>{3DES}xUioZTARbTCuR3Yqxyxnq14zKd/r2xpYWNEWzUh8fQ8=</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.0.0</configuration-version>
<app-deployment>
    <name>medrec</name>
    <target>MedRecServer</target>
    <module-type>ear</module-type>
    <source-path>C:/bea/wlserver_10.3/samples/server/medrec/modules/medrec/assembly/target/medrec.ear</source-path>
    <deployment-order>1</deployment-order>
    <deployment-principal-name>weblogic</deployment-principal-name>
    <security-dd-model>CustomRolesAndPolicies</security-dd-model>
</app-deployment>
<app-deployment>
    <name>physician</name>
    <target>MedRecServer</target>
    <module-type>ear</module-type>
    <source-path>C:/bea/wlserver_10.3/samples/server/medrec/modules/physician/assembly/target/physician.ear</source-path>
    <deployment-order>100</deployment-order>
    <security-dd-model>CustomRolesAndPolicies</security-dd-model>
</app-deployment>
<app-deployment>
    <name>browser-starter</name>
    <target>MedRecServer</target>
    <module-type>war</module-type>
    <source-path>C:/bea/wlserver_10.3/samples/server/medrec/modules/browser-starter/target/browser-starter.war</source-path>
    <deployment-order>100</deployment-order>
    <security-dd-model>CustomRolesAndPolicies</security-dd-model>
</app-deployment>
<library>
    <name>jsf#1.2@1.2.3.2</name>
    <target>MedRecServer</target>
    <module-type>war</module-type>
    <source-path>C:/bea/wlserver_10.3/common/deployable-libraries/jsf-1.2.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
</library>
<library>
    <name>jstl#1.2@1.2.0.1</name>
    <target>MedRecServer</target>
    <module-type>war</module-type>
    <source-path>C:/bea/wlserver_10.3/common/deployable-libraries/jstl-1.2.war</source-path>
    <security-dd-model>DDOnly</security-dd-model>
</library>
<file-realm>
    <name>wl_default_file_realm</name>
</file-realm>
<realm>
    <name>wl_default_realm</name>
    <file-realm>wl_default_file_realm</file-realm>
</realm>
<password-policy>
    <name>wl_default_password_policy</name>
</password-policy>
<jms-server>
    <name>MedRecJMSServer</name>
    <target>MedRecServer</target>
</jms-server>
<self-tuning>
    <work-manager>
      <name>weblogic.wsee.mdb.DispatchPolicy</name>
      <target>MedRecServer</target>
    </work-manager>
</self-tuning>
<mail-session>
    <name>mail/MedRecMailSession</name>
    <target>MedRecServer</target>
    <jndi-name>mail/MedRecMailSession</jndi-name>
    <properties>mail.user=joe;mail.host=mail.mycompany.com</properties>
</mail-session>
<jms-system-resource>
    <name>MedRec-jms</name>
    
    <target>MedRecServer</target>
    <sub-deployment>
      <name>MedRecJMSServer</name>
      <target>MedRecJMSServer</target>
    </sub-deployment>
    <descriptor-file-name>jms/MedRec-jms.xml</descriptor-file-name>
</jms-system-resource>
<admin-server-name>MedRecServer</admin-server-name>
<wldf-system-resource>
    <name>MedRecWLDF</name>
    <target>MedRecServer</target>
    <descriptor-file-name>diagnostics/MedRecWLDF.xml</descriptor-file-name>
</wldf-system-resource>
<jdbc-system-resource>
    <name>MedRecGlobalDataSourceXA</name>
    <target>MedRecServer</target>
    <descriptor-file-name>jdbc/MedRec-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<saf-agent>
    <name>WsrmAgent</name>
    <target>MedRecServer</target>
    <service-type>Both</service-type>
</saf-agent>
</domain>