A server is an instance of WebLogic Server that runs in its own Java Virtual Machine (JVM) and has its own configuration.
When you create a domain, you also create an Administration Server, which distributes configuration changes to other servers in the domain. In a typical production environment, you create one or more Managed Servers in the domain to host business applications and use the Administration Server only to configure and monitor the Managed Servers.
This section describes how to configure servers. This section includes the following tasks:
To configure general settings for a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select General Settings.
From the General Settings page, you can define the configuration settings for this server instance, such as:
Template
Machine
Cluster
Listen Address
Listen Port Enabled
Listen Port
SSL Listen Port Enabled
SSL Listen Port
Client Cert Proxy Enabled
Java Compiler
Diagnostic Volume
For more information about these fields, see Configuration Options.
Optionally, expand Advanced to define advanced configuration settings for this server instance.
Click Save.
To change the server template associated with a server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select General Settings.
Click Change and select the server template from the Server Templates dropdown menu.
Click Yes.
The startup mode specifies the state in which a server instance should be started. The default is to start in the RUNNING state.
To specify the startup mode for a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select General Settings.
On the General page, expand Advanced at the bottom of the page to display the advanced configuration options.
In the Startup Mode field, select:
Running: In the RUNNING state, a server offers its services to clients and can operate as a full member of a cluster.
Administration: In the ADMIN state, the server is up and running, but available only for administration operations, allowing you to perform server and application-level administration tasks without risk to running applications.
Standby: In the STANDBY mode, the server listens for administrative requests only on the domain-wide administration port and only accepts life cycle commands that transition the server instance to either the RUNNING or SHUTDOWN state. Other administration requests are not accepted. If you specify STANDBY, you must also enable the domain-wide administration port.
For more information, see Configuration Options.
Click Save.
To configure the listen address of a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select General Settings.
On the General Settings page, enter a value in Listen Address.
For more information, see Configuration Options.
Click Save.
To configure the listen ports of a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select General Settings.
If you want to disable the non-SSL listen port so that the server listens only on the SSL listen port, deselect Listen Port Enabled. If you want to disable the SSL listen port so that the server listens only on the non-SSL listen port, deselect SSL Listen Port Enabled.
Note:
You cannot disable both the non-SSL listen port and the SSL listen port. At least one port must be active.If you are using the non-SSL listen port and you want to modify the default port number, change the value in Listen Port.
If you want to modify the default SSL listen port number, change the value in SSL Listen Port.
For more information, see Configuration Options.
Click Save.
To change the standard Java compiler values for a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select General Settings.
On the General Settings page, update the Java Compiler field with the full path of the compiler to use for all applications hosted on this server that need to compile Java code.
Expand Advanced to display advanced configuration options.
Update the following compile options as necessary:
Prepend to classpath: Options to prepend to the Java compiler classpath when compiling Java code.
Append to classpath: Options to append to the Java compiler classpath when compiling Java code.
Extra RMI Compiler Options: Options passed to the RMIC compiler during server-side generation.
Extra EJB Compiler Options: Options passed to the EJB compiler during server-side generation.
For more information about these fields, see Configuration Options.
Click Save.
A WebLogic Server cluster is a group of servers that work together to provide a scalable and reliable application platform.
To configure cluster settings for a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Clusters.
From the Cluster page, you can define the cluster configuration settings for this server instance, such as:
Replication Group
Preferred Secondary Group
Cluster Weight
Interface Address
Replication Ports
For more information about these fields, see Configuration Options.
Click Save.
To configure WebLogic service settings for a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Services.
From the Services page, you can define the service configuration settings for this server instance, such as:
JMS Configuration
Default Store
Transaction Log Store
Messaging Bridge Configuration
XML Services Configuration
For more information about these fields, see Configuration Options.
Click Save.
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 specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Keystores.
To change your keystore configuration:
Click Change.
From the Keystores dropdown menu, select the keystore configuration you want to use.
Click Save.
From the Keystore page, you can define other keystore configuration settings for this server instance, such as:
Keystores
Demo Identity Keystore
Demo Identity Keystore Type
Demo Identity Keystore Passphrase
Demo Trust Keystore
Demo Trust Keystore Type
Demo Trust Keystore Passphrase
Java Standard Trust Keystore
Java Standard Trust Keystore Type
Java Standard Trust Keystore Passphrase
For more information about these fields, see Configuration Options.
Click Save.
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 change the keystore:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Keystores.
Click Change.
From the Keystores dropdown menu, select the keystore configuration you want to use.
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 instance, which help you manage the security of message transmissions.
To configure SSL settings for a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select SSL.
To change your identity and trust location:
Click Change.
From the Identity and Trust Locations dropdown menu, select the location you want to use.
Click Save.
From the SSL page, you can define the SSL configuration settings for this server instance, such as:
Identity and Trust Locations
Private Key Location
Private Key Alias
Private Key Passphrase
Certificate Location
Trusted Certificate Authorities
For more information about these fields, see Configuration Options.
Optionally, expand Advanced to define advanced configuration settings for this server instance.
Click Save.
You can view and define various Secure Sockets Layer (SSL) settings for a server instance, which help you manage the security of message transmissions.
To change the identity and trust location:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select SSL.
Click Change.
From the Identity and Trust Locations dropdown menu, select the location you want to use.
For more information about these fields, see Configuration Options.
Click Save.
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:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Federation Services.
Select the SAML 1.1 Source Site page.
Select the Source Site Enabled attribute to cause this server to act as a source for SAML assertions.
From the SAML 1.1 Source Site page, you can also define other desired configuration settings for this server instance, such as:
Source Site URL
Signing Key Alias
Intersite Transfer URIs
ITS Requires SSL
Assertion Retrieval URIs
ARS Requires SSL
ARS Requires Two-Way SSL Authentication
Assertion Store Class Name
Assertion Store Properties
For more information about these fields, see Configuration Options.
Click Save.
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:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Federation Services.
Select the SAML 1.1 Destination Site page.
Select the Destination Site Enabled attribute to enable the Assertion Consumer Service.
From the SAML 1.1 Destination Site page, you can also define other desired configuration settings for this server instance, such as:
Assertion Consumer URIs
ACS Requires SSL
SSL Client Identity Alias
POST Recipient Check Enabled
POST One-Use Check Enabled
Used Assertion Cache Class Name
Used Assertion Cache Properties
For more information about these fields, see Configuration Options.
Click Save.
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, 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:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Federation Services.
Select the SAML 2.0 General page.
Select the Replicated Cache Enabled attribute to use the persistent cache for storing SAML 2.0 artifacts.
This option is required if you are configuring SAML 2.0 services in two or more WebLogic Server instances in your domain. For example, if you are configuring SAML 2.0 services in a cluster, you must enable this option in each Managed Server instance individually.
Note:
If you are configuring SAML 2.0 services in two or more WebLogic Server instances in your domain, you must configure the RDBMS security store. The embedded LDAP server is not supported in these configurations.In the Site Info section, enter the following information about your SAML 2.0 site:
Contact person details
Your organization's name and URL
The Published Site URL, which is the top-level URL for your site's SAML 2.0 service endpoints. This URL must be appended with the string /saml2, which will be automatically combined with constant suffixes to create full endpoint URLs.
In the Bindings section, enter the common binding information to be used by this SAML 2.0 server instance.
If you do not specify a Transport Layer Security key alias and passphrase, the server's configured SSL private key alias and passphrase from the server's SSL configuration is used for the TLS alias by default.
If the Artifact binding is enabled for any SAML 2.0 security provider hosted on this server instance, define the Artifact Resolution Service settings in the Artifact Resolution Service section.
In the Single Sign-on section, enter the keystore alias and passphrase for the key to be used for signing documents sent to federated partners.
If you do not specify a single sign-on signing key alias and passphrase, the server's configured SSL private key alias and passphrase from the server's SSL configuration is used by default.
For more information, see Configuration Options.
Click Save.
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 instance 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:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Federation Services.
Select the SAML 2.0 Identity Provider page.
Select the Enabled attribute to activate this server's SAML 2.0 services in the role of Identity Provider.
Select Only Accept Signed Authentication Requests if you want to ensure that any incoming authentication requests must be signed.
If you are using a custom login Web application to which unauthenticated requests are directed:
Select Login Customized.
Enter the URL of the custom login Web application.
Enter the login return query parameter
The query parameter is a unique string that the SAML 2.0 services uses to hold the login return URL for the local single sign-on service servlet. (Note that, as an alternative, the login return URL can also be specified in the login Web application.)
Set the SAML bindings for which this server instance is enabled, and select the preferred binding type.
For more information, see Configuration Options.
Click Save.
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:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Federation Services.
Select the SAML 2.0 Service Provider page.
Select the Enabled attribute to activate SAML 2.0 services in this server instance in the role of Identity Provider.
Set the configuration options for the local SAML 2.0 Service Provider services as appropriate. Note the following:
Choose options for Always Sign Authentication Requests and Only Accept Signed Assertions as desired and in a manner that is coordinated with your federated partners so that authentication requests and assertions are accepted.
Communicate the SAML bindings settings for this server instance with your federated partners to ensure compatibility.
For more information, see Configuration Options.
Click Save.
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 the default deployment staging on a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Deployment.
From the Deployment page, you can define the default deployment staging configuration for this server instance, such as:
Staging Mode
Staging Directory Mode
Upload Directory Name
For more information about these fields, see Configuration Options.
Click Save.
To configure migration settings for clustered servers:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Migration.
From the Migration page, you can define the configuration settings for this server instance, such as:
Automatic Server Migration Enabled
Candidate Machines
JMS Service Candidate Servers
Automatic JTA Migration Enabled
JTA Candidate Servers
Pre-Migration Script Path
Post-Migration Script Path
Post-Migration Script Fail Cancels Automatic Migration
Allow Post-Migration Script to Run on a Different Machine
Enable Strict Ownership Check
For more information about these fields, see Configuration Options.
Click Save.
You can tune the performance and functionality of a server instance by configuring the tuning settings.
To configure tuning settings for a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Tuning.
From the Tuning page, you can define the tuning configuration settings for this server instance, such as:
Enable Native IO
JavaSocketMuxer Socket Readers
Enable Gathered Writes
Enable Scattered Reads
Maximum Open Sockets
Stuck Thread Max Time
Stuck Thread Timer Interval
Accept Backlog
Login Timeout
SSL Login Timeout
Reverse DNS Allowed
For more information about these fields, see Configuration Options.
Optionally, expand Advanced to define advanced configuration settings for this server instance.
Click Save.
To enable native IO for a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Tuning.
On the Tuning page, if the Enable Native IO check box is not selected, select the check box.
For more information, see Configuration Options.
Click Save.
To enable non-blocking IO for a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Tuning.
Expand Advanced to access advanced tuning parameters.
Enter weblogic.socket.NIOSocketMuxer in the Muxer Class field.
For more information, see Configuration Options.
Click Save.
You can tune the number of connection requests that a WebLogic Server instance will accept before refusing additional requests.
To tune connection backlog buffering for a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Tuning.
Modify the Accept Backlog value as necessary to tune the number of TCP connections the server instance can buffer in the wait queue.
If many connections are dropped or refused at the client, and no other error messages are on the server, the Accept Backlog value might be set too low.
If you receive "connection refused" messages when you try to access WebLogic Server, raise the Accept Backlog value from the default by 25 percent. Continue increasing the value by 25 percent until the messages cease to appear.
For more information about these fields, see Configuration Options.
Click Save.
WebLogic Server diagnoses a thread as stuck if it is continually working (not idle) for a set period of time. You can tune a server's thread detection behavior by changing the length of time before a thread is diagnosed as stuck, and by changing the frequency with which the server checks for stuck threads.
To configure stuck thread detection behavior for a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Tuning.
From the Tuning page, update the following options as necessary:
Stuck Thread Max Time: Amount of time, in seconds, that a thread must be continually working before a server instance diagnoses a thread as being stuck.
Stuck Thread Timer Interval: Amount of time, in seconds, after which a server instance periodically scans threads to see if they have been continually working for the configured Stuck Thread Max Time.
For more information about these fields, see Configuration Options.
Click Save.
The server instance for which you configure Managed Server Independence (MSI) replication does not need to be running.
To configure a Managed Server to replicate a domain's configuration files:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Tuning.
On the Tuning page, click Advanced at the bottom of the page to display advanced configuration settings.
Ensure that the Managed Server Independence Enabled check box is selected.
For more information, see Configuration Options.
Click Save.
After you finish
If the Managed Server is running, restart it.
You can configure how WebLogic Server should react in the case of an overload or failure condition.
To configure overload settings for a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Overload.
From the Overload page, you can define the overload configuration settings for this server, such as:
Shared Capacity for Work Managers
Failure Action
Panic Action
Free Memory Percent High Threshold
Free Memory Percent Low Threshold
Max Stuck Thread Time
Stuck Thread Count
For more information about these fields, see Configuration Options.
Click Save.
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.
You can configure the frequency of a server's automated health checks and the frequency with which the Node Manager application (optional) checks the server's health state. You can also use this page to specify whether Node Manager automatically stops and restarts the server if the server reaches the "failed" health state.
To configure health monitoring settings for a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Health Monitoring.
From the Health Monitoring page, you can define the health monitoring configuration settings for this server instance, such as:
Health Check Interval
Auto Kill If Failed
Auto Restart
Restart Interval
Max Restarts Within Interval
Restart Delay Seconds
For more information about these fields, see Configuration Options.
Click Save.
Node Manager is a WebLogic Server utility that you can use to start, suspend, shut down, and restart servers in normal or unexpected conditions. You can configure the startup settings that Node Manager will use to start this server on a remote machine.
To configure the startup options that Node Manager uses to start a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Server Start.
From the Server Start page, you can define the startup configuration settings for this server instance, such as:
Java Home
Java Vendor
BEA Home
Root Directory
Class Path
Arguments
Security Policy File
User Name
Password
Confirm Password
For more information about these fields, see Configuration Options.
Click Save.
To configure the startup and shutdown settings for a server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Start/Stop.
From the Start/Stop page, you can define the startup and shutdown configuration settings for this server instance, such as:
Ignore Sessions During Shutdown
Graceful Shutdown Timeout
Startup Timeout
Server LifeCycle Timeout
For more information about these fields, see Configuration Options.
Click Save.
You must install a Web service before you can view and modify its configuration. This section includes the following tasks:
To configure message buffering for Web services:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Web Services.
Select the Buffering page.
From the Buffering page, you can define the message buffering configuration properties for this server instance, such as:
Retry Count
Retry Delay
Request Queue Enabled
Request Queue Connection Factory JNDI Name
Request Queue Transaction Enabled
Response Queue Enabled
Response Queue Connection Factory JNDI Name
Response Queue Transaction Enabled
For more information about these fields, see Configuration Options.
Click Save.
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. Use this page to customize reliable messaging configuration on the Web service endpoint.
To configure reliable messaging for Web services:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Web Services.
Select the Reliable Message page.
From the Reliable Messaging page, you can define the reliable messaging configuration properties for this server instance, such as:
Base Retransmission Interval
Enable Retransmission Exponential Backoff
Non-buffered Source
Non-buffered Destination
Acknowledgement Interval
Inactivity Timeout
Sequence Expiration
For more information about these fields, see Configuration Options.
Click Save.
A logical store is a named unit of storage that provides the business configuration requirements and connects the Web service to the physical store and buffering queue.
To view the logical stores configured for this server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Web Services.
Select the Logical Stores page.
From the Logical Stores page, you can view configuration information for each logical store configured for this server instance, such as:
Name
Persistence Strategy
Request Buffering Queue JNDI Name
Response Buffering Queue JNDI Name
Default
For more information about these fields, see Configuration Options.
To configure Coherence for a specific server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Coherence.
From the Coherence page, you can specify the Coherence cluster you want to use for this server instance and also define configuration settings such as:
Unicast Listen Address
Unicast Listen Port
Unicast Port Auto Adjust
Local Storage Enabled
Coherence Web Logical Storage Enabled
Site Name
Rack Name
Click Save.
For more information, see Configuration Options.
This section describes how to configure server protocols.
This section includes the following tasks:
To configure general protocol settings for a server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Protocols.
Select the General Settings page.
From the General Settings page, you can define connections settings for various communication protocols that this server instance uses, such as:
Complete Message Timeout
Idle Connection Timeout
Enable Tunneling
Tunneling Client Ping
Tunneling Client Timeout
Maximum Message Size
For more information about these fields, see Configuration Options.
Click Save.
To configure HTTP protocol settings for a server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Protocols.
Select the HTTP page.
From the HTTP page, you can define the HTTP settings for this server instance, such as:
Default WebApp Context Root
Post Timeout
Max Post Size
Enable Keepalives
Duration
HTTPS Duration
Frontend Host
Frontend HTTP Port
Frontend HTTPS Port
WAP Enabled
Remote Address Override
Send Server Header
Accept Context Path in Get Real Path
HTTP Max Message Size
Enable Tunneling
Tunneling Client Ping
Tunneling Client Timeout
For more information about these fields, see Configuration Options.
Click Save.
To configure Java to COM (jCOM) protocol settings for a server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Protocols.
Select the jCOM page.
From the jCOM page, you can define jCOM protocol settings for this server instance, such as:
Enable COM
NT Authentication Host
Enable Native Mode
Verbose Logging Enabled
Enable Memory Logging
Prefetch Enumeration
Apartment Threaded
For more information about these fields, see Configuration Options.
Click Save.
To configure Internet Inter-ORB Protocol (IIOP) settings for a server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Protocols.
Select the IIOP page.
From the IIOP page, you can enable IIOP for this server instance.
For more information about these fields, see Configuration Options.
Optionally, expand Advanced to define advanced configuration settings for this server instance.
Click Save.
To monitor network channel protocol settings for a server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Protocols.
Select the Channels page.
The Channels table displays information about each network channel that has been configured for this server instance, such as:
Name
Protocol
Enabled
Listen Address
Listen Port
Public Address
Public Port
For more information about these fields, see Configuration Options.
Click Save.
To configure network channel protocol settings for a server instance:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server dropdown menu, select Administration, then select Protocols.
Select the Channels page.
In the Channels table, select the name of the channel you want to configure.
Select Configuration.
From the General page, you can define general configuration settings for the network channel, such as:
Name
Protocol
Listen Port
Listen Address
External Listen Address
External Listen Port
Enabled
For more information about these fields, see Configuration Options.
Optionally, expand Advanced to define advanced configuration settings for this network channel.
Click Save.
From the Security page, you can define security configuration options for the network channel, such as:
Two Way SSL Enabled
Client Certificate Enforced
For more information about these fields, see Configuration Options.
Optionally, expand Advanced to define advanced configuration settings for this network channel.
Click Save.
Note:
For information about configuring server template network channel settings, see Configure server template network channel settings.To create notes for server configuration:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server menu, select Administration, then select Notes.
On the Notes page, enter your notes.
Click Save.
For more information, see Configuration Options.
To view or change the server template configuration for a dynamic server:
From the Welcome Page, select Targets, then select Middleware.
In the Targets table, select your WebLogic domain. If prompted, enter your user credentials to log in to the WebLogic domain.
From the Target Navigation pane, select the server instance you want to configure.
From the WebLogic Server menu, select Administration, then select Server Template.
To view or change the configuration for the server template associated with this dynamic server, click the Server Template link.
For more information, see Configuration Options.