Make Offline Configuration Changes

All offline configuration changes must be made on the primary host, except those relating to node managers, and all Oracle Analytics Server processes must be stopped first.

To consume offline changes you must start the Administration Server, Managed Servers, and then system components (in that order). This is the general requirement for any configuration change as the command to start the Managed Server is the only process that replicates the configuration, from a running Administration Server.

Assumptions and pre-requisites:

You must have file system (offline) or Weblogic Administrator (online) permissions
When you start component(s) offline, the Administration server and node managers must be started first, see Start Component Processes in a Domain

Running WLST Offline

You run WLST scripts commands from the following location:

ORACLE_HOME/oracle_common/common/bin/wlst.sh

Before issuing offline commands you must select a domain using the readDomain(DOMAIN_HOME) command.

For example:
```
readDomain('/u01/bi')
```
After you have issued your offline commands you must commit the changes using the updateDomain() command.

For example:
```
updateDomain('/u01/bi')
```
De-select the domain using the closeDomain() command.

For example:
```
closeDomain('/u01/bi')
```

If you make a mistake or decide to abandon changes, you should use the closeDomain() command without using the updateDomain() command.