#
Configuring Access to the Open iT Shared Software Assets Directory (SSAD)
#
Activating the Shared Software Assets Directory (SSAD) Feature
Open a command prompt with Administrator level privileges.
Go to the contrib\bin directory, which is by default in
C:\Program Files\OpeniT\Core\contrib\bin
, run the command:Command Syntaxcd $ROOT_DIR\contrib\bin
Examplecd C:\Program Files\OpeniT\Core\contrib\bin
Once in the directory, run the command:
Command Syntaxactivate_ssad.bat true
The following arguments are available when running the
activate_ssad
script.Available Arguments for activate_ssad
You may also use the following options for
activate_ssad
.Available Options for activate_ssad
Open a command prompt with Administrator level privileges.
Go to the contrib\bin directory, which is by default in
/opt/openit/contrib/bin
, run the command:Command Syntaxcd $ROOT_DIR/contrib/bin
Examplecd /opt/openit/contrib/bin
Once in the directory, run the command:
Command Syntax./activate_ssad.pl true
The following arguments are available when running the
activate_ssad
script.Available Arguments for activate_ssad
You may also use the following options for
activate_ssad
.Available Options for activate_ssad
Change the file ownership by running the command:
Command Syntaxchown -R [openit_user]:[openit_group] /var/opt/openit/etc
where:
Arguments to Change File Ownership
Examplechown -R openit:openit /var/opt/openit/etc
Verify that the file ownership of
data_generation_config
is changed. Run the command:Command Syntaxls -l /var/opt/openit/etc | grep data_generation_config
This displays detailed information about the
data_generation_config
file.Example Output-rw-r--r-- 1 openit openit 8954 Apr 29 11:25 data_generation_config
Verify that the file ownership of
core_mapping_ssad.oconf
is changed. Run the command:Command Syntaxls -l /var/opt/openit/etc/scheduler | grep ssad
This should display detailed information about the
core_mapping_ssad.oconf
file.Example Output-rw-r--r-- 1 openit openit 1425 Apr 29 11:25 core_mapping_ssad.oconf
#
Configuring the Shared Software Assets Directory (SSAD) Access Credentials
Coordinate with the Open iT Account Manager or Delivery/Support Team to get your SSAD access credentials.
Open a command prompt with Administrator level privileges.
Go to the bin directory, which is by default in
C:\Program Files\OpeniT\Core\bin
, run the command:Command Syntaxcd $BIN_DIR
Examplecd C:\Program Files\OpeniT\Core\bin
Once in the directory, run one of following the commands:
To encrypt and save the SSAD credentials, use this command:
Command Syntaxopenit_ssad_connector --config --client_id <client_id> --client_secret <client_secret>
To encrypt, save the SSAD credentials, and perform normal processes such as sending data to the SSAD API and fetching maps, use this command:
Command Syntaxopenit_ssad_connector --client_id <client_id> --client_secret <client_secret>
After completing the steps, verify that the SSAD credentials are configured successfully. Go to the Configuration folder, which is by default in
C:\Program Files\OpeniT\Core\Configuration
, and check thecredentials.json
file to ensure the credentials have been updated.The client secret value is already encrypted.
Coordinate with the Open iT Account Manager or Delivery/Support Team to get your SSAD access credentials.
Go to the bin directory, which is by default in
/opt/openit/bin
, run the command:Command Syntaxcd $BIN_DIR
Examplecd /opt/openit/bin
Once in the directory, run one of following the commands:
To encrypt and save the SSAD credentials, use this command:
Command Syntax./openit_ssad_connector --config --client_id <client_id> --client_secret <client_secret>
To encrypt, save the SSAD credentials, and perform normal processes such as sending data to the SSAD API and fetching maps, use this command:
Command Syntax./openit_ssad_connector --client_id <client_id> --client_secret <client_secret>
After completing the steps, verify that the SSAD credentials are configured successfully. Go to the Configuration folder, which is by default in
C:\Program Files\OpeniT\Core\Configuration
, and check thecredentials.json
file to ensure the credentials have been updated.The client secret value is already encrypted.