Activating or deactivating local changes
You can activate or deactivate applying local changes.
To activate or deactivate applying of local changes
-
In the API Server installation directory, open the bin\appsettings.json file.
NOTE: If the file is encrypted, decrypt it first.
-
Perform one of the following actions:
-
To activate applying local changes, insert the following code:
{ |
"Settings": { |
"IsStandAlone": "True" |
} |
} |
-
To deactivate applying local changes, insert the following code:
{ |
"Settings": { |
"IsStandAlone": "False" |
} |
} |
NOTE: If this code section already exists, change the value of the IsStandAlone property accordingly.
-
Save your changes to the file.
NOTE: If the file was encrypted beforehand, encrypt it again.
Converting local changes into global changes
To distribute changes to all API servers that were previously applied only locally to one API Server, you can convert local changes to global changes. This saves the changes in the global configuration file.
To convert local changes into global changes
-
Log in to the Administration Portal (see Logging in to the Administration Portal).
-
In the navigation, click Configuration.
-
On the Configuration page, in the Show configuration for the following API project drop-down, select the API project that has the local changes you want to convert to global changes.
-
Click Actions > Convert locally customized settings to global settings.
-
In the Convert Locally Customized Settings to Global Settings side panel, click Convert.
Displaying API Server packages
You can display the API Server packages that have been received.
To display all the API Server packages
-
Log in to the Administration Portal (see Logging in to the Administration Portal).
-
In the navigation, click Packages.
Displaying API Server plug-ins
You can display all the API Server plug-ins that are used.
To display all the API Server plug-ins
-
Log in to the Administration Portal (see Logging in to the Administration Portal).
-
In the navigation, click Plugins.