+ | and a single path for all application files including the database server files |
+ | during deployment to avoid waiting for data loading and database server |
+ | initialization. |
+ | Most deployment utility functionality can be invoked by using either |
+ | |
+ | (.conf) file to accommodate your working preference. The .conf file also facilitates |
+ | easier reuse of an instance setup because you can save your settings in a copy of |
+ | the file. |
To operate the deployment utility, run the ifxdeploy executable from a command | |
+ | line or from a script as part of an application installation. (The full file name of the |
+ | executable is ifxdeploy.exe in the Windows version of IDS, but it will be referred |
+ | to as simply ifxdeploy throughout the documentation.) The utility can be run |
without user interaction, in silent mode. | |
| |
|
+Rapid IDS Embeddability with the Deployment Utility
+ | A snapshot of an instance can be reconfigured and initialized by running the |
+ | deployment utility with a combination of command line options or by setting |
+ | values in the ifxdeploy.conf file. |
+ | You can preinitialize the instance by indicating the location of the IBM Informix |
+ | Dynamic Server chunk paths on the target computer. |
+ | The ifxdeploy.conf file allows for more dynamic customization than the |
+ | |
+ | parameter values, set key environment variables, and create multiple database |
+ | server aliases. |
+ | To apply configuration settings of the ifxdeploy.conf file to an instance you are |
+ | deploying, enter the file name as an argument to the |
+ | the ifxdeploy command. |
+ | If you set different values for the same instance in the ifxdeploy.conf file and as an |
+ | option to the ifxdeploy command option, the deployment utility uses the value |
+ | specified on the command line. For example, if you specify |
+ | command line but set the INFORMIXPASSWORD parameter to mypassword2 in the |
+ | ifxdeploy.conf file, the deployed instance requires mypassword1 for authentication. |
+ | Initialized dbspaces |
+ | If you create a snapshot with initialized dbspaces, you can deploy the snapshot as |
+ | an initialized instance without having to wait for disk space initialization on the |
+ | target system. |
+ | To deploy the dbspaces to different locations from where they were when the |
+ | snapshot was taken, use the |
+ | one or more parent directories for the chunks of the deployed instance. |
+ | If you want to relocate the chunk parent directories, verify the following before |
+ | you run the utility: |
+ | v The chunk files on the target computer exist in path locations that correspond |
+ | with your chunk parent directory relocation settings. |