Self Service processes for the next-generation platform

You can run the processes in Self Service for various tasks.

For detailed instructions on how to start a process, see Viewing and running processes.

Note: MQ is not available in the master configuration environments. Therefore, MQ operations are not available in the master configuration environments.

Table 1. Self Service processes that can be run by users with the Developer role
Process	Description
Import third party certificates	Imports any third-party certificates that are required for integration of IBM Sterling® Order Management System agent, integration, and application server JVMs with the third-party system.
Trigger agent server	Triggers an agent server. Specify the agent criteria ID of the agent server that you want to trigger.
Import configuration	Imports the specified version of the configuration XML. Select the version of the configuration files that you want to import. Enter the snippet in the CDT preferences XML. Triggers a rolling restart after a CDT import. Note: Do not use this process to import the CDT XML files from a lower environment to a higher environment, except when MC environment is on a lower version and QA environment is on a higher version.
Export configuration	Generates and exports a version of the configuration files. The version is named by using the date and time when it is created.
Export MQ logs	Exports MQ logs and the logs are available for download on the local machine.
Upload external configuration XMLs	Uploads the external CDT files in a compressed .zip format.
Download exported CDT	Downloads the exported CDT files to your local machine.
Import overridden property settings to database	Imports Sterling™ Order Management System properties that are overridden in the customer_overrides.properties file to the database. Note: Run this process each time a modified content of customer_overrides.properties file is deployed to the <OMS_Runtime> as part of a new customization package. By default, IBM Sterling Order Management System reads the application-provided property values. Therefore, ensure that you run this process to import the property overrides to the database to get the expected product behavior.
Load optional Db2 scripts	Loads the US postal codes and also creates corresponding region configuration for these postal codes in Sterling Order Management System. Select the following options to insert postal and region codes: OOB Db2 scripts - Inserts the default US postal codes and region records. Custom Db2 scripts - Inserts custom postal codes and region records. For more information about custom optional SQL data, see Updating additional SQL data .
Reset transaction database	Resets the transactional database by truncating the transaction type tables in the Sterling Order Management System preproduction, development, and testing environments. To truncate a table, enter `TABLE.<table_name>`. For example, `TABLE.INTEROP_ERROR_DISPATCH`. To truncate a group of tables, enter `GROUP.<group_name>`. Here, `group_name` is the name that is assigned to a logical group of tables. For example, `GROUP.ASYNC_REQ`. To truncate multiple tables or groups, or a combination of tables and groups, separate their names with commas. For example, if you want to truncate the `INBOX` and `ASYNC_REQ` groups, and the `YFS_INVENTORY_SUPPLY_TEMP` table together, enter the value as `GROUP.ASYNC_REQ`, `GROUP.INBOX`, `TABLE.YFS_INVENTORY_SUPPLY_TEMP`. To truncate all custom transactions tables, enter `EXTN.TABLES.TRAN` in the Group Name field. To truncate particular custom transaction table, enter `EXTN.TABLE.<CUSTOM_TRANSACTION_TABLE>` in the Group Name field. For more information about the tables and groups that can be truncated, see Table reference.

Table 2. Self Service processes that can be run by users with the Developer role and the IBM® Support role
Process	Description
Rolling restart of application servers	Restarts the Sterling Order Management System application server in Pre-production and Production environments. When you select this process for a Production environment, you must select a reason for the rolling restart of the application server. The reason is saved and is displayed when you view the process report.
Start servers	Starts one or more agent or integration servers. Before you start the process, you can select one or more servers that you need to start. Optionally, you can enable verbose logs. If the servers are started, the status of the process changes to success. If a server fails to start, you can view the report to troubleshoot. Note: If you want to start two instances of the same server, this process must be run twice.
Stop servers	Stops one or more agent or integration servers. Before you start the process, you can select one or more servers that you need to stop. Optionally, you can enable verbose logs. If the servers are stopped, the status of the process changes to success. If a server fails to stop, you can view the report to troubleshoot.
Export application logs	Exports the application logs. You can export the logs for all components or a specific component such as agent server, integration server, or application server. The application logs are uploaded into the IBM Cloud Object Storage as multiple compressed (tar) files, that is, one tar file per server. Users with the Developer role can download the logs using the provided URL. For more information, see Server specific logging-related mappings in next-generation environments.