Server templates let you easily manage configuration for a group of server instances in one centralized location. You define common configuration attributes in a server template and then apply the template to other server instances without having to manually configure each one. If you need to update an attribute across all server instances, then you can simply change the value in the server template and the new value takes effect in all of the server instances that use the server template.
For more information, see Server Templates in Understanding Domain Configuration for Oracle WebLogic Server
Note:
If you are logged into a domain partition, navigate from the Domain Partition menu.
This chapter includes the following sections:
This section describes how to configure server templates. This section includes the following tasks:
Changes to your general settings for a template will apply to every server that references the template unless explicitly overridden.
To configure general settings for a sever template:
A WebLogic Server cluster is a group of servers that work together to provide a scalable and reliable application platform.
To configure cluster configuration settings for a server template:
Keystores ensure the secure storage and management of private keys and trusted certificate authorities (CAs). You can view and define various keystore configurations which help you manage the security of message transmissions.
To configure keystore settings for a server template:
From the WebLogic Domain menu, select Environment, then select Server Templates.
The Server Templates table displays information about each server template that has been configured in the current WebLogic Server domain.
In the Server Templates table, select the name of the server template you want to configure.
Select Configuration, then select Keystores.
To change your keystore configuration:
Click Change.
From the Keystores menu, select the keystore configuration you want to use.
Click Save.
From the Keystore page, you can define the keystore configuration settings for this server template, such as:
Identity settings
Trust settings
For more information about these fields, see Configuration Options.
Click Save.
You can view and define various Secure Sockets Layer (SSL) settings for a server template, which help you manage the security of message transmissions.
To configure SSL settings for a server template:
You can configure a WebLogic Server instance to function as a producer or as a consumer of SAML assertions that can be used for the following:
Web single sign-on between online business partners
Exchange of identity information in Web services security
The general process of configuring Federation Services depends upon the version of SAML you are using. WebLogic Server supports both SAML 1.1 and SAML 2.0.
To configure WebLogic Server to serve as a SAML 1.1 federated partner:
To configure WebLogic Server to serve as a SAML 2.0 federated partner:
Before you begin
You must first configure a SAML Credential Mapper V2 security provider in the server's security realm.
You can configure a WebLogic Server instance to function as a SAML source site. A SAML source site is a site that provides an Intersite Transfer Service (ITS). A source site generates assertions that are conveyed to a destination site using one of the single sign-on profiles.
To configure a server as a SAML source site:
Before you begin
You must first configure a SAML Identity Asserter V2 security provider in the server's security realm.
You can configure a WebLogic Server instance to function as a SAML destination site. A destination site can receive SAML assertions and use them to authenticate local subjects.
To configure a server as a SAML destination site:
You can configure general SAML 2.0 services for a server. If you are configuring SAML 2.0 Web single sign-on services with your federated partners, then the site information you configure is published in a metadata file that you send to your federated partners.
To configure the general SAML 2.0 properties of this server:
For more information, see Configuration Options.
After you finish
After you have configured this server's general SAML 2.0 services, select the SAML 2.0 Identity Provider page or the SAML 2.0 Service Provider page to configure this server as an Identity Provider or Service Provider, respectively. For more information, see Configure SAML 2.0 Identity Provider services and Configure SAML 2.0 Service Provider services.
You can configure a server in the role of SAML 2.0 Identity Provider. A SAML 2.0 Identity Provider creates, maintains, and manages identity information for principals, and provides principal authentication to other Service Provider partners within a federation by generating SAML 2.0 assertions for those partners.
To configure a server as a SAML 2.0 Identity Provider:
For more information, see Configuration Options.
After you finish
Coordinate with your federated partners to ensure that the SAML bindings you have enabled for this SAML authority, as well as your requirements for signed documents, are compatible with your partners.
You can configure a WebLogic Server instances as a SAML 2.0 Service Provider. A Service Provider is a SAML authority that can receive SAML assertions and extract identity information from those assertions. The identity information can then be mapped to local Subjects, and optionally groups as well, that can be authenticated.
To configure a server as a SAML 2.0 Service Provider:
For more information, see Configuration Options.
After you finish
Coordinate with your federated partners to ensure that the SAML bindings you have enabled for this SAML authority, as well as your requirements for signed documents, are compatible with your partners.
To configure deployment settings for a server template:
WebLogic Server provides a self-health monitoring capability to improve the reliability and availability of servers in a WebLogic Server domain. Selected subsystems within each server monitor their health status based on criteria specific to the subsystem.
To configure health monitoring settings for a server template:
Node Manager is a WebLogic Server utility that you can use to start, suspend, shut down, and restart servers in normal or unexpected conditions.
To configure startup settings for a server template:
This section describes how to configure Web services for a server template.
This section includes the following tasks:
To configure messaging buffering settings for a server template:
Web service reliable messaging is a framework that enables an application running on one application server to reliably invoke a Web service running on another application server, assuming that both servers implement the WS-Reliable Messaging specification. Reliable is defined as the ability to guarantee message delivery between the two Web services.
To configure reliable messaging settings for a server template:
To configure Coherence settings for a server template:
This section describes how to configure server template protocols.
This section includes the following tasks:
To configure general protocol settings for a server template:
To configure Java to COM (jCOM) protocol settings for a server template:
To configure Internet Inter-ORB Protocol (IIOP) settings for a server template:
To monitor network channel protocol settings for a server template:
To create notes for server configuration:
For more information, see Configuration Options.