A transaction signifies the process or operation that is performed for the settings and configuration definitions that are included to be provisioned on devices in a deployment plan. A one-to-one mapping exists between the deployment plan and a transaction. A unique identifier for each transaction for easy tracking and filtering is automatically assigned by the Edge Services Director application. A transaction applies only for deploy plans that are in the approved state because only approved plans can be scheduled for provisioning configuration on devices.
The Transactions page displays all of the transactions generated by the system for approved deploy plans. You can perform the following tasks on this page:
Delete a transaction, which causes the transaction to be removed from listing, but does not delete the deployment plan associated with it.
View the XML API format of configurations that exist on the device, that are to be deployed on the device, or the change-set of configurations between the settings on the device and the settings to be deployed.
View a list of all transactions
To view the transactions:
- From the View selector, select Gateway View or Service View. The workspaces that are applicable to this view are displayed. In Gateway view, the devices in the entire network are displayed, organized by the device types and the device models within each device type. In Service View, the different types of services are displayed in the View pane.
- From the Junos Space user interface, click the Deploy icon on the Edge Services Director banner.
The functionalities that you can configure in this mode are displayed in the task pane.
- From the View pane, select the All Network item in Gateway view. Click the plus sign (+) beside the All Network item in the View pane to expand the tree and select the device node you want.
- Select Deploy Service > Transactions from the
task pane. The Transactions page is displayed.
The page is divided into two panes. The top pane displays the transactions that have been generated by the system for the different approved deployment plans. The deployment job ID and services to be transmitted to the devices in each transaction or deploy plan are also displayed. The bottom pane displays extensive information about a particular transaction, such as the devices to which the configuration is to be provisioned and the exact configuration parameters in XML API form.
The following fields are displayed in the top pane of the page:
Unique identifier assigned by the system for a transaction.
Unique identifier assigned by the system for a deployment plan.
The time, day, month, and year at which the deploy plan was created. The timestamp is the UTC time in database that is mapped to the local time zone of client computer.
Names of the deploy plans, which are of the DPnn naming format, that are part of the job ID or transaction. The DP part of the name denotes deployment plan and nn signifies the number allotted to the deploy plan.
Names of the service instances that are to be deployed in the transaction.
Current status of the deployment job that is used to provision configuration on a device.
Information about the status of the deploy plan that you can use to modify or take appropriate steps for ensuring successful deploy of configurations to devices.
- Select the check box next to the transaction for which
you want to view detailed information. The bottom pane displays the
devices and configurations of each of the devices for the selected
The following fields are displayed in the bottom pane of the page:
Name of the service delivery gateway for which deployment of settings is being performed using the particular transaction. The SDG name follows the SDG-nn format, where SDG denotes that the device is a service delivery gateway and nn represents the unique number of the SDG that is automatically generated to differentiate each SDG in a transaction.
Host names of the devices in an SDG high availability pair or the standalone SDG device.
Click the View link to open the dialog box that displays the XML form of configuration parameters and statements that are currently running on the device. Click Close after you complete viewing the settings.
Click the View link to open the dialog box that displays the XML form of configuration parameters and statements that are to be deployed to the device. Click Close after you complete viewing the settings.
Click the View link to open the dialog box that displays the XML form of the previously committed (rollback) configuration parameters and statements on a device. You can revert to the last known good state before the most recent configuration change that was performed on a device. Click Close after you complete viewing the settings.
The operation that is currently running as part of the transaction to propagate configuration settings to devices. You can also view a list of all the events or tasks that were performed using this transaction by clicking the All link.
The Transactions Steps dialog box is displayed. A list of all of the tasks, their statuses, and information about each of the statuses is displayed. Tasks indicate whether the configuration is prepared, the currently active configuration parameters on a device have bene retrieved, differential set of the configuration settings that need to be deployed, and the propagation of the configuration attributes.
Current status of the transaction related to a deploy job that is used to provision configuration on a device.
Information about the status of the transaction that you can use to modify or take appropriate steps for ensuring successful deploy of configurations to devices.