Scripting Tool for WebLogic Server

Building the WebLogic Server Domain on Another Machine

Some sites separate the administration of SAS applications and the administration of Web application servers. For sites that do not permit running the SAS Deployment Wizard on the Web application server machine, the configuration scripting tool can be used to configure a WebLogic Server domain. The configuration scripting tool is archived from the machine where the SAS Deployment Wizard was run and provided to the Web application server administrator. The configuration scripting tool can configure WebLogic Server identically to what is created with an automated deployment with SAS Deployment Wizard. The configuration scripting tool is located in SAS-config-dir\Lev1\Web\Scripts\WebLogic. The name of the command is saswls.cmd. The wlst.commands.txt file in the same directory contains all the commands that are needed to configure the domain. The following example shows the syntax for using the configuration scripting tool to configure domain:

saswls.cmd wlst.commands.txt

Note: For UNIX deployments, the command is named saswls.sh.

If the Cache Credentials check box was not selected on the Web Application Server: Scripting Configuration page in the SAS Deployment Wizard, then you are prompted for credentials when you run the command.

When the configuration scripting tool is used to create the domain, after the script completes, the domain is configured with all the resources that are needed for the SAS Web applications. The configuration scripting tool deploys the applications and starts the servers.

On the Web application server machine, create the directory structure that was used on the machine where the SAS Deployment Wizard was run. The following commands are examples for a Windows environment:
```
mkdir c:\SAS\Config\Lev1\Web\Staging
mkdir c:\SAS\Config\Lev1\Web\Scripts
mkdir c:\SAS\Config\Lev1\Web\Common
mkdir c:\SAS\Config\Lev1\Web\Temp
mkdir c:\SAS\Config\Lev1\AppData
```
Note: These directory paths must be archived from the machine where the SAS Deployment Wizard was run. The archive must be transferred to the Web application server machine.
Extract the archive into the directories that were created in the previous step.
Open the Scripts\Weblogic\props\global.properties file in a text editor. Review the properties to make sure that values for the JDK path, WebLogic Server installation path, host names, and ports are accurate.

Begin the configuration by running saswlst.cmd wlsct.commands.txt.

If the Cache Credentials check box was not selected on the Web Application Server: Scripting Configuration page in the SAS Deployment Wizard then monitor the progress because the tool prompts you for credentials. The following code is an example:

16 Dec 2011 14:28:08,730 - CredentialsDialogPrep-processCredentials: Determine 
if credentials need to be solicited for those resources that require 
authentication...

*=*=*=*=*=*=*  BEGIN Prompting for credentials *=*=*=*=*=*=*

------------------------------------------------------------------------
Please enter credentials for: SAS Trusted User
Enter username: sastrust@saspw
Is "sastrust@saspw" correct? (y/n): y
Username "sastrust@saspw" accepted.
Enter password:
Re-enter password:

If this is the first time the scripting tool is run on the machine, then there is a prompt to confirm that you want to create a key file:
```
Creating the key file can reduce the security of your system if it is not 
kept in a secured location after it is created. Do you want to create the key 
file? y or n
```

After the configuration scripting tool runs and WebLogic Server is configured, some additional tasks must be performed manually on the machine where the SAS Deployment Wizard was run. (For a multiple-machine deployment, this is the machine where the middle-tier configuration was performed.) These tasks are recorded in the Instructions.html file that is generated by the SAS Deployment Wizard. Before you perform those tasks, confirm or correct the JDK_HOME environment variable that is identified in SAS-config-dir\Lev1\level_env.bat . For UNIX deployments, the file is named level_env.sh. Open the file in an editor and make sure that the value for JDK_HOME identifies the path to a JDK or JRE.

Rebuilding the WebLogic Server Configuration

You can rebuild the WebLogic Server configuration by running the configuration scripting tool. The tool can re-create the entire WebLogic Server configuration and restore it to the originally configured state. The tool reads the commands in the commands file and configures the resources according to the settings in the properties files.

Executing a Batch Script

You can supply a file that contains a series of commands for the configuration scripting tool to execute. This approach is the same strategy that is used for rebuilding the domain with the commands listed in the wlst.commands.txt file. However, you can supply a file with different commands to configure different resources. The following example shows the syntax for using the configuration scripting tool with a commands file that is named cmds.txt:

saswls.cmds cmds.txt

In the batch script file, the commands take the following form:

<operation> <resource_type> <resource_name>

The following example shows the commands for undeploying and redeploying the SAS Web Application Themes:

undeploy application sas.themes.ear
deploy application sas.themes.ear

Executing a single command from the command line uses the same three parts for the command syntax.

If you are creating a resource that requires credentials, such as a data source, remember to create property keys in the credentials.properties file.

Executing a Single Command

You can execute a single command on a single resource from a command line. The following example shows how to undeploy SAS Web Application Themes:

saswls.cmd undeploy application sas.themes.ear

Executing Commands Interactively

In addition to running the configuration scripting tool in batch mode or executing a single command, the configuration scripting tool can be run interactively. The following example shows how to check the status of the SASServer1 server instance:

saslws.cmd

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

29 Apr 2011 13:44:43,134 - Running in script mode, forcing autoConfigure and 
autoDeploy.
Enter commands interactively:
Usage: operation type name
> check server SASServer1
...
RUNNING
Disconnected from weblogic server: AdminServer
***** This step took 1.9210000038146973 seconds to complete. *****
operation completed with return code '0'

The command syntax and operations can be found by entering help at the interactive command prompt. The following display shows the results of the help command:

saswls operation resource_type resource_name [additional_options]

additional options that can appear anywhere on the command line to launch 
the script:

credentials=file_name
promptMode=TEXT|GRAPHIC

valid resource types (supported operations):

application         (compile deploy undeploy)
connectionfactory   (create delete)
dataSource          (create delete)
domain              (create customize listservers listjmsservers 
                     createloginmodule)
foreignjndiprovider (create)
jdbcprovider        (create delete)
jmsServer           (create delete)
mailSession         (create delete)
nodemanager         (start stop)
policy              (set)
queue               (create delete)
server              (check create delete start stop)
topic               (create delete)
user                (create)

Properties Reference

Global Properties

Property files are used by the configuration scripting tool to configure the middle-tier environment. These properties are found in SAS-config-dir/Lev1/Web/Scripts/Weblogic/props. Each of the properties are described in the following list:

SASDomainName

is the name of the WebLogic Server domain that is used for the SAS Web applications. This property is not used by the configuration scripting tool. This property is used by SAS Deployment Wizard to generate documentation only.

SASWlstScriptHome

identifies the fully qualified path to the configuration scripting tool directory.

adminHost

is the host name of the administration server for this domain.

adminJvmOptions

is the list of JVM options for the administration server.

adminPort

is the port number that the administration server listens on.

adminSSLPort

is the port number for SSL communication with the administration server. This value can be set in the properties file, but the configuration scripting tool do not support configuring servers with SSL.

adminServerName

is the name of the administration server. This property is not currently used by the configuration scripting tool. The name is always AdminServer.

adminServiceName

is the Windows service name for the administration server. This property is used to generate the scripts that install Windows services.

adminUrl

is the URL that is used by the wlst command to connect to the administration server.

applicationStagingDir

is the fully qualified path to the staging directory for the SAS Web applications. This property is not used by the configuration scripting tool. This property is used to generate documentation only.

autoConfigure

is a Boolean value. If set to false, then manual configuration is requested and the SAS Deployment Wizard creates a sample domain and configures servers in off-line mode only. All configuration steps that are run outside of SAS Deployment Wizard and SAS Deployment Manager are automated regardless of this setting.

autoDeploy

is a Boolean value. If set to false, then the SAS Deployment Wizard does not deploy the SAS Web applications. This property is not used by the configuration scripting tool. This property is used by SAS Deployment Wizard to generate documentation.

backupBinDir

identifies the fully qualified path to a directory that is used to save previous versions of the scripts in the domain/bin directory.

bitwidthOption

is used to set the -d64 JVM option for machines that need this JVM option. This property is used in the commEnvSAS.sh script.

configureJMSSecurity

is used by SAS Deployment Wizard to generate documentation only.

domainChanges

is used to generate a report of configuration changes in the instructions that are generated by SAS Deployment Wizard or SAS Deployment Manager. It is not used by the configuration scripting tool.

domainDir

identifies the fully qualified path to the domain to configure.

host

is the host name for this machine.

isAdminHost

is a Boolean value. If the administration server is installed on this machine, then set this value to true.

javaHome

set this property to the same value as the JAVA_HOME environment variable. The property is inherited by the managed servers and tool that are launched by the configuration scripting tool.

javaVendor

identifies the Java vendor. Values include Sun, Oracle, IBM, BEA, and HP. The values are case sensitive.

jdkBugWorkaround

is set to a JVM option that is required by most recent JDKs. Do not modify this property.

loginModuleFile

identifies the path of the JAAS loginModuleFile that is set as a JVM option for WebLogic managed servers.

midtierMulticastIpJavaOptions

is a list of JVM options that configure multicast communications with the SAS Remote Services application. These values must match the values used by the SAS Remote Services application.

minimumUlimit

is the minimum acceptable unlimit setting for file descriptors on UNIX machines. The create domain operation fails if a lower setting is detected.

mwHomeDir

identifies the Oracle middleware home directory (MW_HOME). This is typically the parent directory of the WebLogic Server installation directory, but the WebLogic Server installers permit installing WebLogic Server in a different location.

nodeManagerPort

is the port number that the nodemanager server for this domain is listening on.

osLinuxVendor

is set to a valid Linux vendor name. Values are redhat or SuSE. The values are case sensitive. On other operating systems, the value is set to UNKNOWN. This value is used in the commEnvSAS.sh script.

osLinuxVersion

identifies the Linux operating system version number. On other operating systems, the value is set to UNKNOWN.

osType

identifies the operating system type. Values are win or unx. The values are case sensitive.

pythonCachedirOption

identifies the location of the Python cache. This value is passed to the wlst command line.

rcFileName

identifies the fully qualified path to a file that is used by wlst commands to return values in properties and return code status.

returnCodeProperties

identifies the fully qualified path to the return code properties file that maps return code keys to numeric values. Do not change this property.

startScript

identifies the fully qualified path to the domain setup script. This file is named setDomainEnv.cmd or setDomainEnv.sh.

templateDirectoryName

identifies the fully qualified path to the directory that contains the velocity templates. The templates are used to create scripts in the domain/bin directory.

webappsrvScriptingCacheCredentials

is a Boolean value. If set to true, then credential values are cached in the credentials.properties file. If set to false, then values are purged from credentials.properties when the configuration scripting tool exits.

webauthIsComment

is set to the string or character that is used as a comment. Several lines are included in commEnvSAS.cmd or commEnvSAS.sh for the support of Web authentication. These lines are commented out unless you have manually modified the SAS deployment to support Web authentication. If Web authentication is configured, then this property contains an empty value.

weblogicBarName

is a string that is used to create the name of the Windows services in installNodeMgrSvc.cmd and uninstallNodeMgrSvc.cmd.

weblogicHome

identifies the fully qualified path to the WebLogic Server installation. The WL_HOME environment variable is set to this value in generated scripts.

weblogicInstalled

is a Boolean value. Set to true to indicate that WebLogic Server is installed on the machine that is used for the SAS middle tier. This value is used to generate documentation and is not used by the configuration scripting tool.

weblogicNodeManagerServiceName

is the Windows service name for the nodemanager server.

weblogicProdName

is the WebLogic product name that is used as part of the Windows service name for the nodemanager server.

weblogicReconfigured

is a Boolean value. This property is set to true if the last SAS Deployment Wizard run was a reconfiguration. This property is used to generate documentation only and is not used by the configuration scripting tool.

weblogicSelectedVersion

is used by SAS Deployment Wizard to generate documentation only. It is not used by the configuration scripting tool.

Credential Properties

All properties that are related to credentials are stored in the credentials.properties file. The tool prompts you for these properties. This properties file does not need to be edited directly. These values are cleared from the file after the tool completes if the global property webappsrvScriptingCacheCredentials is set to false. When stored, these values are stored in SAS base-64 encoding, not clear-text. If you chose to store passwords in this file, then they are updated when you use the Update passwords feature of the SAS Deployment Manager.

datasource.create_resource_passwd

is the data source user password.

datasource.create_resource_userid

is the data source user name.

domain.create_WeblogicAdmin_passwd

is the WebLogic Server administrator password.

domain.create_WeblogicAdmin_userid

is the WebLogic Server administrator user.

domain.createloginmodule_SASTrust_passwd

is the SAS Trusted User password.

domain.createloginmodule_SASTrust_userid

is the SAS Trusted User. This identity is used to configure the JAAS login module.

mailsession.create_SASMailSession_passwd

is the mail session user password.

mailsession.create_SASMailSession_userid

is the mail session user ID. This credential is used only if the mailsession property mailsrvRequiresAuthentication is set to true.

user.create_resource_passwd

is the WebLogic Server user's password.

user.create_resource_userid

is the WebLogic Server default realm user ID.

Resource Properties

Each property file governs the configuration of a specific resource. The next section lists and describes a group of properties that are common to many resources. The subsequent sections identify properties that are specific to each resource type.

Properties Common to Many Resources

The following properties are common to a number of resource types.

deleted

is a Boolean value. If set to true, then this resource has been marked as deleted.

deletedTargets

is a comma-separated list of target servers that contain this resource that are marked for deletion. A Delete operation removes these targets and removes the resource if no targets remain.

targets

is a comma-separated list of servers that this resource instance is targeted to.

thisOperation

is a field that is used internally by SAS Deployment Wizard and SAS Deployment Manager to manage resource files. It is not used by the configuration scripting tool.

thisTarget

is a field that is used internally by SAS Deployment Wizard and SAS Deployment Manager to manage resource files. It is not used by the configuration scripting tool.

Application Properties

These resources represent applications deployed in a WebLogic Server domain. The properties files are named in the pattern application.application_name.properties. For information about how these properties control WebLogic Server configuration, see the online Help in the WebLogic Administration Console. More information is available in the WebLogic Server documentation on the Oracle Web site. The WebLogic Server 10.3.3 documentation for this resource is available at http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13952/taskhelp/applications/DeployEnterpriseApplications.html.

applicationName

is the name of the SAS Web application.

applicationPath

identifies the fully qualified path to the application archive file or directory.

compileMaxMemory

is the -Xmx option used on the weblogic.appc command line when compiling a Web application.

docApplicationName

is the name of the application that is used in documentation. This property is used by SAS Deployment Wizard to generate documentation. It is not used by the configuration scripting tool.

loadOrder

is the application load order.

Data Source Properties

Data source properties are used to configure data source resources in WebLogic. The resource files are named in the pattern datasource.datasource_name.properties. For information about how these properties control WebLogic Server configuration, see the online Help in the WebLogic Administration Console. More information is available in the WebLogic Server documentation on the Oracle Web site. The WebLogic Server 10.3.3 documentation for this resource is available at http://download.oracle.com/docs/cd/E14571_01/web.1111/e13737/toc.htm.

capacityIncrement

is the number of connections that are created when new connections are added to the connection pool.

classPath

is the classpath that includes the JAR files required for the JDBC driver. This classpath is used only to keep track of JDBC JAR files used by the various data sources and the JDBC providers.

databaseServerURL

is the JDBC URL for communication with the database server.

datasourceName

is the data source name. This name must be unique in a WebLogic Server domain.

driverName

is the fully qualified JDBC driver class name.

globalTransactionsProtocol

is the global transactions protocol. Values include TwoPhaseCommit, LoggingLastResource, OnePhaseCommit, EmulateTwoPhaseCommit, and None. SAS applications depend on correct settings. Do not change this property.

initialCapacity

is the number of physical connections to create when creating the connection pool.

inputJarLocation

identifies the fully qualified path for the directory where the JDBC driver JAR files have been staged.

jdbcDriverJarDir

identifies the fully qualified path for the directory where the JDBC driver JAR files are copied and used by the configuration.

jndiName

is the data source JNDI name. This name is configured in application configuration files and should not be changed without corresponding changes to the applications that use this datasource.

keepLogicalConnOpenOnRelease

keepXaConnTillTxComplete

is a Boolean value. If set to true, then it enables WebLogic Server to keep the logical JDBC connection open for a global transaction when the physical XA connection is returned to the connection pool. SAS applications might depend on particular JDBC transaction settings. Do not change this property.

loginDelaySeconds

is the number of seconds to delay before creating each physical database connection. This delay supports database servers that cannot handle multiple connection requests in rapid succession.

maxCapacity

is the maximum number of physical connections that this connection pool can contain.

needTxCtxOnClose

is a Boolean value. If set to true, it specifies whether the XA driver requires a distributed transaction context when closing various JDBC objects (result sets, statements, connections, and so on). This property applies only to connection pools that use an XA driver. SAS applications might depend on particular JDBC transaction settings. Do not change this property.

options

is a list of properties that are passed to the JDBC driver. The options are used to create physical database connections.

shrinkFrequencySeconds

is the number of seconds to wait before shrinking a connection pool that has incrementally increased to meet demand.

testConnectionsOnReserve

is a Boolean value. If set to true , then WebLogic Server can test a connection before giving it to a client. (This feature requires that you specify a value for testTableName.)

testTableName

is the name of the database table to use when testing physical database connections. This name is required when you specify a Test Frequency and enable Test Reserved Connections.

xaEndOnlyOnce

is a Boolean value. If set to true, then it specifies that XAResource.end() is called only once for each pending XAResource.start(). This option prevents the XA driver from calling XAResource.end(TMSUSPEND) and XAResource.end(TMSUCCESS) successively. This property applies to data sources that use an XA driver only. SAS applications might depend on particular JDBC transaction settings. Do not change this property.

Domain Properties

Most domain configuration properties are defined in global.properties. The file domain.domainName.properties contains properties needed exclusively to create a new domain and is not required by operations on other resources.

domainTemplatePath

identifies the fully qualified path to the template JAR file that is used to create the domain.

Foreign JNDI Provider Properties

Resources are stored in properties files that are named in the pattern foreignjndiprovider.resource.properties. For information about how these properties control WebLogic Server configuration, see the online Help in the WebLogic Administration Console. More information is available in the WebLogic Server documentation on the Oracle Web site. The WebLogic Server 10.3.3 documentation for this resource is available at http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13952/taskhelp/jndi/ConfigureForeignJNDIProvider.html.

foreignJNDIName

is the foreign JNDI Name for a linked name.

foreignLinkName

is the user-specified name of the foreign JNDI link MBean instance.

foreignProviderName

is the user-specified name of the foreign JNDI MBean instance.

foreignProviderURL

is the foreign provider URL that is used to make connections to the remote server.

initialContextFactory

is the initial context factory to use to connect. This class name depends on the JNDI provider and the vendor that are being used. The value corresponds to the standard JNDI property, java.naming.factory.initial.

localJNDIName

is the local JNDI name for a linked name.

JDBC Provider Properties

JDBC provider properties are used to configure JDBC drivers in WebLogic Server. The resource files are named in the pattern jdbcprovider.resource_name.properties. WebLogic Server does not use the concept of a JDBC provider. These properties are used by the SAS Deployment Wizard to manage the JDBC driver JAR files only.

classPath

is the classpath that includes the JAR files required for the JDBC driver. This is used only to keep track of JDBC JAR files used by the various data sources and the JDBC providers.

inputJarLocation

identifies the fully qualified path for the directory where the JDBC driver JAR files have been staged.

jdbcDriverJarDir

identifies the fully qualified path for the directory where the JDBC driver JAR files are copied and used by the configuration.

jdbcProvider

is a name that is used to keep track of the JAR files related to this JDBC driver by a particular application. This name must be unique in a WebLogic Server domain.

JMS Resource Properties

Three types of JMS resources are supported. Depending on the type of resource, they are stored in properties files that are named in the pattern connectionfactory.resource.properties, queue.resource.properties, or topic.resource.properties. For information about how these properties control WebLogic Server configuration, see the online Help in the WebLogic Administration Console. More information is available in the WebLogic Server documentation on the Oracle Web site. The WebLogic Server 10.3.3 documentation for this resource is available at http://download.oracle.com/docs/cd/E14571_01/web.1111/e13738/toc.htm.

cfXAEnabled

is a Boolean value. If set to true, then it indicates whether an XA queue or XA topic connection factory is returned, instead of a queue or topic connection factory. This property applies to connection factories only. SAS applications might depend on particular JDBC transaction settings. Do not change this property.

jmsModuleName

is the name of the JMS system module to target this resource to.

jmsServerName

is the name of the JMS server instance to which this module is targeted.

jndiName

is the global JNDI name used to look up the destination within the JNDI namespace. This name is configured in application configuration files and should not be changed without corresponding changes to the applications that use this JMS resource.

resourceName

is the name of this JMS resource.

resourceType

is the type of JMS resource to be configured. Supported values are ConnectionFactory, Queue, and Topic.

subdeploymentName

is the name of the subdeployment with which this resource is associated.

JMS Server Properties

Resources are stored in properties files that are named in the pattern jmsserver.resource.properties. For information about how these properties control WebLogic Server configuration, see the online Help in the WebLogic Administration Console. More information is available in the WebLogic Server documentation on the Oracle Web site. The WebLogic Server 10.3.3 documentation for this resource is available at http://download.oracle.com/docs/cd/E14571_01/web.1111/e13738/toc.htm.

dataSourceName

is the data source to use for a JDBC persistent store. If a data source is not configured, the value is not-set. SAS applications might depend on particular settings. Do not change this property.

jdbcStoreName

is the name of the file or database in which this JMS server stores persistent messages. If a data store is not configured, then the value of dataSourceName is not-set. SAS applications might depend on particular settings. Do not change this property.

jmsServerName

is the name of the JMS Server.

tablePrefix

is a name to prefix to the table name in this JDBC store. If a table prefix is not configured, the value is not-set.

targetServerName

is the name of the managed server that is associated with this JMS server.

Login Module Properties

JAAS login modules are configured in a flat file as documented at: http://download.oracle.com/javase/6/docs/api/javax/security/auth/login/Configuration.html. The module configuration properties are stored in properties files that are named in the pattern loginmodule.resource.properties. Modules are grouped together under an application name.

aliasdomain

is the name of another domain that this module responds to. This domain is used when this module runs in a remote JVM and receives generated credentials from an environment that uses the trusted authentication module.

applicationPolicy

is the application policy that these properties apply to.

debug

set this property to true to generate debugging information to the System.out stream.

domain

is the authentication domain that this module authenticates to. Requests to authenticate users outside this domain are ignored.

hasCredentials

set this property to true if this module incorporates credentials found in the credentials property file.

holdOpenConnection

is a Boolean value that controls how the login module interacts with the SAS Metadata Server. If set to false, then the login module opens a connection to the SAS Metadata Server and closes it when it is finished. Setting this property to true causes the module to store a handle to the connection object in the Subject object. This connection can then be reused by the UserContext object. This option should not be set to true if the module is being used by an application container. Otherwise, the connection is not closed until the Subject object is destroyed by garbage collection.

host

is the host name for the SAS Metadata Server.

loginModuleCode

is the fully qualified class name for the login module.

loginModuleFlag

is one of the following values: required, requisite, sufficient, optional. For more information, see http://download.oracle.com/javase/6/docs/api/javax/security/auth/login/Configuration.html.

port

is the port number that the SAS Metadata Server is listening on for new connections.

repository

is the name of the repository that is set as the default repository. For the primary authentication, the typical value is Foundation.

Login Policy Properties

JAAS login modules are configured in a flat file as documented at : http://download.oracle.com/javase/6/docs/api/javax/security/auth/login/Configuration.html. The login policy configuration properties are stored in properties files that are named in the pattern loginpolicy.resource.properties. Modules are grouped together under an application name that is based on these policy names.

applicationPolicy

is the login policy name. Typical values for a SAS deployment are PFS, SCS, and UsernamePassword.

Mail Session Properties

Resources are stored in properties files that are named in the pattern mailsession.resource.properties. For information about how these properties control WebLogic Server configuration, see the online Help in the WebLogic Administration Console. More information is available in the WebLogic Server documentation on the Oracle Web site. For example, the WebLogic Server 10.3.3 documentation is available at http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13952/taskhelp/mail/CreateMailSessions.html.

mailSessionJNDIName

is the JNDI name for the mail session. This name is configured in application configuration files and should not be changed without corresponding changes to the applications that use this mail session.

mailSessionName

is the name of the mail session resource.

mailSessionSMTPHost

is the host name of SMTP server for the mail session.

mailsrvRequiresAuthentication

is a Boolean value. Set to true if credentials are required to access this mail server.

Policy Properties

These resources represent a WebLogic default realm policy that is configured in a WebLogic domain. The properties files are named in the pattern policy.policyname.properties. For information about how these properties control WebLogic Server configuration, see the online Help in the WebLogic Administration Console. More information is available in the WebLogic Server documentation on the Oracle Web site. The WebLogic Server 10.3.3 documentation for this resource is available at http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13952/taskhelp/security/UseRolesAndPoliciesToSecureResources.html.

policyExpression

is the policy expression to set for the resource.

policyName

is the policy name. This property is set but is not used.

securedResource

is the resource ID.

Server Properties

Server resources are stored in properties files that are named in the pattern server.servername.properties. For information about how these properties control WebLogic Server configuration, see the online Help in the WebLogic Administration Console. More information is available in the WebLogic Server documentation on the Oracle Web site. The WebLogic Server 10.3.3 documentation for this resource is available at http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13952/taskhelp/domainconfig/CreateManagedServers.html.

JDKOptions

is a list of JVM options for this server.

cmdLineChanges

is a list of command line changes. This property is used by SAS Deployment Wizard to produce documentation. It is not used by the configuration scripting tool.

cmdLineScriptChanges

is a list of command line script changes. This property is used by SAS Deployment Wizard to produce documentation. It is not used by the configuration scripting tool.

javaPolicySettings

is a list of JVM options to use when a Java security manager is used. This option is not currently supported with WebLogic Server, and this property is ignored.

listenPort

is the port number that this server uses for HTTP connections.

managedServerName

is the name of the managed server.

scriptJDKOptions

is a list of JVM options for this server. This property is used by velocity templates to create the setDomainEnv.cmd and setDomainEnv.sh scripts. The value is usually identical to JDKOptions.

serverChanges

is used by SAS Deployment Wizard to produce documentation. It is not used by the configuration scripting tool.

serviceName

is the Windows service name. This value is used to create a Windows service for the server.

sslListenPort

is the port number that this server uses for SSL connections. The configuration scripting tool does not currently support SSL configuration.

startScript

is the location of the domain setup script, setDomainEnv.cmd.

User Properties

These resources represent WebLogic Server users in the default realm. The properties files are named in the pattern user.servername.properties. The credentials are stored in the credentials.properties file. For information about how these properties control WebLogic Server configuration, see the online Help in the WebLogic Administration Console. More information is available in the WebLogic Server documentation on the Oracle Web site. The WebLogic Server 10.3.3 documentation for this resource is available at http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13952/taskhelp/security/DefineUsers.html.

description

is a description of the user.