domainRestart
- Karl Henselin
This operation restarts entire WebLogic domain. Servers in the FDWLS_STOP_SERVER_ EXCLUDE_LIST property are not stopped, and servers in the FDWLS_START_SERVER_EXCLUDE_LIST property are not started. If admin server restart is desired, configure node manager (NODEMANAGER) related properties on Target. This operation supports rolling restart to make sure application is available to users during restart operation.
Order of restarts is:
admin server (if not skipped by
FDWLS_INP_SKIP_ADMIN),WSM servers (
WLS_WSM1, WLS_WSM2 etc. if included in input), thenthe other clusters and servers.
This order is managed as various Fusion Middleware products are dependent on WSM servers. This order applies for both modes of restarts.
If FDWLS_INP_USE_ROLLING_MODE is checked, some percentage of servers within cluster are restarted individually to make sure that application is available during restart. You can indicate FDWLS_INP_MAX_PERCENT_SIMULTANEOUS to control percentage of cluster members to restart simultaneously. This value will default to 20 percent. Cluster members for restart are selected using its machine name such that all servers on specific machine are eligible first for restart. Basically list servers within cluster are sorted by machine name and percentage is applied on that list. Maximum percentage allowed for this mode is 50, if higher value is specified only 50 will be used. This approach is taken here as session for cluster will be replicated across physical nodes by default. Once admin server and WSM servers are restarted, all remaining clusters of WebLogic domain are stopped and started in parallel with each cluster started in rolling manner.
If FDWLS_INP_USE_ROLLING_MODE is not checked, entire domain is stopped and started. Managed servers on various machines are stopped and started in parallel. You can control what percent of the servers of each cluster are stopped and started together with the FDWLS_INP_MAX_PERCENT_SIMULTANEOUS input.
Blog Posts
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Oracle Weblogic Home (WL_HOME) |
| Yes | WebLogic Home Directory. (e.g. /u01/oracle/products/fmw/wlserver) |
Weblogic Domain Name |
| Yes | WebLogic Domain Name. |
Weblogic Admin Listen Address |
| Yes | The listener address of the WLS admin server. (e.g. localhost) |
Weblogic Admin Listen Port |
| Yes | The port of the WLS admin server. (e.g. 7001) |
Weblogic Admin SSL Connection |
| No | Indicates whether the admin server is using SSL. |
Weblogic Admin User |
| Yes | The username for the WLS admin server. |
Weblogic Admin Password |
| Yes | The password for |
Weblogic Start Server Timeout |
| No | Time in milliseconds that the plugin operation will wait for server start. Plugin operation will return as soon as server starts, and if the server fails to start in timeout specified, plugin operation will fail. |
Weblogic Stop Server Timeout |
| No | Time in milliseconds that the plugin operation will wait for server stop. Plugin operation will return as soon as server stops, and if the server fails to stop in timeout specified, plugin operation will fail. |
Weblogic Admin Server Name |
| No | WebLogic Admin Server Name. Defaults to AdminServer. |
Weblogic Admin Domain Directory |
| No | WebLogic Domain Directory for AdminServer. Used when the admin server runs from a different domain folder than managed servers |
Weblogic Domain Directory |
| Yes | WebLogic Domain Directory for managed servers. |
Weblogic Node Manager Port |
| Yes | The port for the WLS Node Manager. |
Weblogic Node Manager User |
| Yes | The user id for the WLS Node Manager. |
Weblogic Node Manager Password |
| Yes | The password for |
Weblogic Node Manager Host |
| Yes | Host for Node Manager connection. |
Weblogic Node Manager Type |
| No | Node Manager Type. (e.g. ssl, plain, SSH, RSH) |
Weblogic Start Server Exclude List |
| No | Provide comma-separated names of managed servers (not clusters), which you do not want started during start operation. |
Weblogic Stop Server Exclude List |
| No | Provide comma-separated names of managed servers (not clusters), which you do not want stopped or restarted. They will be started at the end if not also in |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Rolling Mode |
| No | If checked, servers will be restarted so that application delivery continues through the restart operation. |
Skip Admin Server |
| No | If checked, the Admin server will not be restarted. |
Max Parallel Percentage |
| No | The maximum percentage of cluster members to restart at the same time. Defaults to 20%. |
Artifacts
This operation doesn't consume or produce any artifacts.
Endpoint Selection
This operation will select all available endpoints associated to the Target which have a resource type of WLS Admin Server. Since the admin server only runs on one server, it is expected that for a given domain, there will only be one endpoint with a resource type set to WLS Admin Server.
Endpoint Execution
This operation will execute on the Admin Server endpoint selected using the WLS Admin Server resource type.
- style