You can customize the settings of the WebLogic Remote Console to fit your needs.
The Networking section manages connection related settings for the WebLogic Remote Console.
You can learn about other system properties related to networking at Networking Properties in the Java Platform, SE and JDK 11 API Specification. To avoid unexpected behavior, make sure your settings don’t conflict with each other.
If you specify HTTPS for the domain URL in the Connect to WebLogic Domain window, then the WebLogic Remote Console uses SSL/TLS to communicate with the WebLogic domain.
The SSL/TLS connection requires trust in the WebLogic domain, where the trust configuration is handled by the underlying JDK JSSE support. By default, the JDK uses the
cacerts truststore provided with the JDK. If the WebLogic domain requires additional trust, separate trust, or is using the WebLogic demo trust (
demotrust.jks), then you’ll need to configure SSL/TLS trust using one of these options:
Import the required trust certificates into the
cacerts truststore supplied with the JDK using the
Configure the type and location of the trust store.
You may need to configure settings for a proxy server to facilitate communication between a WebLogic Server domain that resides in a different network and the WebLogic Remote Console. You can configure a global proxy server that applies to all administration server connections or assign proxy server settings individually to each administration server connection. You can also configure a combination of global and individual settings; the individual proxy server settings will supersede the global proxy server settings.
This proxy server will apply to all administration server connections (unless superseded by an individual proxy server setting).
Because you can also use Java system properties to configure proxy server settings, it is technically possible to create multiple global proxy servers. We do not recommend this as configuring multiple global proxy servers can lead to unexpected behavior. The proxy server value in the Settings dialog box takes precedence over all other global proxy server settings. Additionally, if you use Java system properties to add one proxy server that uses HTTPS and another that uses SOCKS, the WebLogic Remote Console will ignore the SOCKS proxy server.
Open the Providers drawer.
Beside the Administration Server provider where you want to configure a proxy server, click the Settings icon.
In the Proxy Override field, enter the address of the proxy server, including both the host name and port.
NOTE: If you want the WebLogic Remote Console to make a direct connection and bypass a global proxy server setting, enter
Individual proxy server settings take precedence over global proxy server settings.
You can change the default settings for the connection and read timeout limits used with a WebLogic domain from the WebLogic Remote Console.
When changing network timeout settings, the primary impact will be to the response time for Console threads, while the application will show no data when a timeout occurs. Timeouts are more likely to occur during requests where WebLogic Server experiences longer initialization or execution times, such as during runtime monitoring actions of servers.
When using WebLogic demo trust to connect to the WebLogic domain, you may need to disable host name verification. Disabling host name verification causes the WebLogic Remote Console to skip the verification check of ensuring that the host name in the URL to which a connection is made matches the host name in the digital certificate that the server sends back as part of the SSL connection.
We do not recommend using the demo certificates or turning off host name verification in production environments.
The Other Java System Properties section lets you use Java system properties to customize the WebLogic Remote Console if a specific setting is not available elsewhere in the Settings dialog box.
Open the Settings dialog box and select the Other Java System Properties section. Click + to add a new row and enter the Java system property as a name-value pair, separated by
=. For example,
To delete a property, select the row and click -.
If an equivalent setting already exists in the Settings dialog box, we recommend using that configuration option instead of the Java system property. For example, use the Proxy Address option under Networking rather than
When the WebLogic Remote Console establishes a connection with the WebLogic Domain, a HTTP Cookie is established with the Web Browser session.
For security reasons, the
SameSite attribute of the HTTP Cookie may need to be set for the Web Browser to accept the HTTP session Cookie. There are two settings that control the Remote Console behavior:
console.enableSameSiteCookieValue=true to include the
SameSite attribute in the HTTP Cookie.
console.valueSameSiteCookie=<value> to specify the value of the
SameSite attribute. Possible values are
Lax. The default is
You can configure the WebLogic Remote Console to use a JDK at a different location.