When you use a SQL Data Insights (SQL DI) shell command to configure the application in silent mode, administer its server settings, or manage its connections and object models, you must create and specify a command input file. The input file contains the properties and values that you set or accept for the action that the command invokes. You can create a command input file by customizing a template that SQL DI provides.
- In a batch session, change to the $SQLDI_INSTALL_DIR/templates directory.
- Select an input file template based on the shell command you want to issue.
SQL DI provides the following input file templates, each of which contains the configuration properties and environment variables for a specific command action:
- install_file.template
- Provides input to the create command for SQL DI configuration in silent mode.
- settings_scripts.template
- Provides input to the set_settings, list_settings, and list_default_settings commands for SQL DI administration.
- connection_scripts.template
- Provides input to the create_connection, update_connection, list_connection, and remove_connection commands for connection management.
- aiobject_scripts.template
- Provides input to the create_object, deploy, list_all_objects, list_column_config, list_object, retrain, remove_model, and remove_object commands for object model management.
- Copy and customize the selected template based on the command action that you want to specify and the environment of your SQL DI installation.
The template files are USS text entities, and you can edit them with a text editor, such as OEDIT or vi. Some of the configuration properties in the template are required, while others are optional. For a required property, specify a value based on your need or accept the default, if available.
Do not include any additional shell commands or environment variable expansions when you customize the settings_scripts.template, connection_scripts.template, or aiobject_scripts.template files. SQL DI does not treat the resulting input files as executables.
- Save the customized template as your input file and optionally, rename the new input file.
You can rename the customized template file. For the new file name, consider using alphanumeric characters, underscores, and periods, which helps avoid potential character conversion errors if you invoke the sqldi.sh shell script with JCL. In addition, consider encoding and tagging the renamed file as an EBCDIC IBM-1047, ASCII ISO8859-1, or Unicode UTF-8 file.