Configure WebLogic AdminServer

Application Release Automation: Configuring WebLogic Administration Server

This section describes the configuration steps required for the WebLogic plugin, to configure a WebLogic Administration Server (AdminServer).

This configuration is then used during deployment to create/modify the WebLogic AdminServer. The WebLogic AdminServer (as for the WebLogic Domain) creation is a pre-requisite to any other configuration task, such as the creation of managed servers and clusters, and is the minimum, together with the WebLogic Domain) for any WebLogic configuration task.

Before you begin

Open or create a new Jython environment-specific configuration file. This file will contain the configuration settings that will describe the WebLogic AdminServer being created. Any change made to the AdminServer properties in this file will be reflected in the AdminServer created/modified by the tool.

About this task

This task creates the minimum set required for the creation of a WebLogic AdminServer. Only one AdminServer may be created per configuration file.

Procedure

Open the environment-specific py file and import the AdminServer template. This pre-populated template is typically populated with default values or None (Jython value for null) or a pre-defined name. The pre-defined names should typically be overridden in the environment-specific py file. Where a None value exists, the tool will preserve the default value setting.

from templates.AdminServerTemplate import *

Set up the global properties for the domain to be created.

These global properties define variables such as the location of the domain directory, the username/password and so on. This was explained in the overview section of the WebLogic configuration section.

Make a copy of the AdminServer Template using the provided deepcopy function and assign the name AdminServer to it. There is only one AdminServer object and is the object that will be created by the tool.

AdminServer = copy.deepcopy(AdminServerTemplate)

Change the required set of parameters of the AdminServer template copy by accessing the parameters using Jython syntax. The parameters set will reflect the AdminServer configuration that you want to create.

SSL Configuration

If you want to enable the SSL protocol for the Admin Server (t3s) you will need to set some additional properties. These properties are:

  • Protocol: which can have the values t3 or t3s. For SSL protocol enabling set it to t3s.
  • Listen Port: set to the specific port used for SSL connections.
  • Identity Keystore File Name: the path to the keystore that has the server identification certificate.
  • Identity Keystore Type: depending on the type of the keystore.
  • Identity Keystore Passphrase: the passphrase to access the keystore.
  • Private Key Alias: the alias of the private key inside the keystore used for the server identification.
  • Private Key PassPhrase: the passphrase used to access the private key.
  • Trust Keystore File Name: the path to the keystore that has the trusting certificates (CAs).
  • Trust Keystore Type: depending on the type of the keystore.
  • Trust Keystore Passphrase: the passphrase to access the keystore.
  • Hostname Verification Ignored: to ignore the hostname verification.
  • Client Certificate Enforced: to enforce the client certification.

Example

The example below shows the configuration required to create a new AdminServer with the name AdminServer and the SSL configuration set. Open and view the AdminServer template (AdminServerTemplate.py) file for a list of all the parameters that may be set and to understand the syntax to be used to set each property.

AdminServer = copy.deepcopy(AdminServer)
AdminServer['Name'] = 'GenericAdminServer'
AdminServer['ListenPort'] = 7001
AdminServer['ListenAddress'] = '82.165.195.36'

protocol = 't3s'

# SSL configuration
AdminServer['SSL']['ListenPort'] = 7002
AdminServer['SSL']['HostnameVerificationIgnored'] = 'true'
AdminServer['SSL']['ClientCertificateEnforced'] = 'false'

AdminServer['KeyStores'] = 'CustomIdentityAndCommandLineTrust'
AdminServer['CustomIdentityKeyStoreFileName'] = 'C:/tmp/DemoIdentity.jks'
AdminServer['CustomIdentityKeyStoreType'] = 'jks'
AdminServer['CustomIdentityKeyStorePassPhraseEncrypted'] = 'DemoIdentityKeyStorePassPhrase'
AdminServer['SSL']['ServerPrivateKeyAlias'] = 'demoidentity'
AdminServer['SSL']['ServerPrivateKeyPassPhraseEncrypted'] = 'DemoIdentityPassPhrase'

AdminServer['CustomTrustKeyStoreFileName'] = 'C:/tmp/DemoTrust.jks'
AdminServer['CustomTrustKeyStoreType'] = 'jks'
AdminServer['CustomTrustKeyStorePassPhraseEncrypted'] = 'DemoTrustKeyStorePassPhrase'

What to do next

You can now configure the other domain objects, such as WebLogic Servers.