Table of Contents

Search

  1. Preface
  2. Product Overview
  3. Security
  4. Applications
  5. Partner and Account Information
  6. Events
  7. Event Archiving
  8. User Policies
  9. Schedules
  10. B2B Data Exchange Administrative Tasks
  11. On-boarding Checklist Template
  12. System Properties
  13. Repository Management
  14. Document Management
  15. B2B Data Exchange Utilities
  16. DX Toggle Server REST API
  17. Dashboard and Reports Management

Administrator Guide

Administrator Guide

Enable and Disable Schedules Command Syntax

Enable and Disable Schedules Command Syntax

Use the enable and disable schedules utility command syntax to enable all schedules, in the
B2B Data Exchange
repository. You do not need a specification file to enable or disable all objects.
You can find the batch scripts in the following directory:
<
DX
InstallationDir>\dx-tools\
The enable and disable schedules utility uses the following syntax:
enabledisableschedules <-f, <enable/disable> <-u, --user <userID> <-U, <Environment variable> <-p, --password <password> <-P, <Environment variable> <--server, --server <"hostname:port">
The following is an example of a sample batch script to enable the endpoints:
enabledisableschedules.bat -u <username> -p <password> -f enable
The following list describes parameters and arguments for the enable and disable schedules utility commands.
-f
Argument: enable/disable
Required. The command to run. Specify one of the following commands:
  • enable. Enables the schedules from the list file in the
    B2B Data Exchange
    repository.
  • disable. Disables the schedules from the list file in the
    B2B Data Exchange
    repository.
-u or --user
Argument: UserID
Optional. User ID of an Operation Console user account with the Edit Schedule privilege to perform the enable or disable all command. The user account must have the Edit Data privilege to run this command. If you use Informatica platform authentication, the user ID must specify the Informatica security domain, separated by the @ symbol.
For example:
Administrator@SecurityDomain
You must specify at least one of the user name options, -u or -U, to determine the UserID required to execute this command.
-U
Argument: Environment variable
Optional. Environment variable that contains the UserID value.
UserID of an Operation Console user account with Edit Schedule privileges to perform the enable or disable all command. The user account must have the Edit Data privilege to run this command. If you use Informatica platform authentication, the user ID must specify the Informatica security domain, separated by the @ symbol.
For example:
Administrator@SecurityDomain
You must specify at least one of the user name options, -u or -U to determine the UserID required to execute this command.
-p or --password
Argument: password
Optional. Password of the Operation Console user that executes the enable or disable all command. This option contains the clear text password.
You must specify at least one of the password options, -p or -P to determine the UserID required to execute this command.
-P
Argument: Environment variable
Optional. Environment variable that contains the password value.
Password for the Operation Console user that executes the enable or disable all command. The password must be encrypted.
You must specify at least one of the password options, -p or -P to determine the user's password required to execute this command.
--server
Argument: "hostname:port"
Optional. Environment variable that contains the password value.
Optional. Host name and port number of the B2B Data Exchange server. If you do not enter an argument, the utility connects to the localhost server with the default port 18095. The argument must be enclosed in quotation marks.
For example:
archive --server “localhost:18095”

0 COMMENTS

We’d like to hear from you!