Deploying a BOX into the current site

BOX deployment means merging BOX resources into a site and extending the system site’s configuration.

The Deploy BOX wizard respects the existing file structure of a BOX, deploying files to the levels according to the BOX file level settings.

  • If a BOX contains several level files, then these files are deployed to Root/MasterSite/Site directories respectively.
  • The BOX resource file folder structure saves root/master site level files separately from site level resources.
  • If a BOX contains only site level files, then these files are deployed only to the current site directory.
  • The BOX manifest.xml file keeps the level to which the BOX resource belongs and saves the resource file relative location.
  • For library files, their original folder structure is maintained in the BOX manifest.xml file during BOX creation. The folder structure is re-created and the library files are copied into them during BOX deployment.
  1. Right-click the BOX and select Deploy on the menu.
    If there are any open files in the IDE that must be updated or merged, then a message dialog box opens. This informs you to close all files for the listed tools. Close the listed files and click Deploy again on the BOX Manager right-click menu. This opens the Deploy BOX wizard opens to BOX Summary and Resources.
  2. Review the tab information.
    • The Summary tab shows all information defined in the BOX manifest file.
    • The Resources tab shows a list of resources in the BOX.
    • If the BOX contains a database connection, then an additional Configuration tab displays, showing the current database configuration. If this needs to be edited, then a Confirm Database Configurations page is available after confirming the environment configurations.
  3. Click Next. This opens the Merge BOX Resources into Current Site dialog box.
    This shows any site, master site, and root level file conflicts.
    Note: If there are no conflicts, then the Conflict column is hidden. The BOX tree is still kept for you to see the contents.
    For additional information, go to Resolving conflicts.
    Next is enabled when all conflicts are resolved.
  4. Click Next to open the Confirm Environment Configurations dialog box.
    This tab lists all ports for each thread/destination of NetConfig. There are usually several ports when a thread runs in another host.
  5. You can also specify a file in which to save the configuration during the deployment. Open the Choose Configuration File to select a file, or click Save to open a dialog box for adding a new file. Files are saved in the config folder under the BOX. For example, integrator\box\conn_1_tcpip\config.
  6. The Other Environment Configurations tab shows all system environment-related variables for threads. Verify the information on this tab. These environment-related properties, defined in NetConfig, must be modified to match the new host environment; otherwise, the process/thread might not run.
  7. Click Next. If the BOX contains a database connection, then the next wizard page is Confirm Database Configurations, where you can make changes as required.
    You can reconfigure Database URL, User Name, Password, and Schema. Modifications are saved in dbconfiguration.ini.
    For example, a BOX that was created from a test environment is deployed to a production environment. The database connection might require reconfiguration to the production database.
  8. Click Finish. The wizard checks file locks for all to-be-updated resources of the current site. If some files are locked by other clients, then a Lock Conflict dialog box opens.
    • Clicking Yes breaks all listed file locks. The wizard continues to update or merge BOX resources into the current site and then close itself after the operation is finished. All locks are released after deployment.
    • Clicking No closes the Lock Conflict dialog box. This returns you to the Confirm Other Environment Configurations dialog box. In this dialog box, you can navigate to the other wizard dialog boxes to stop or retry to break the lock.
    Note: For NetConfig, new threads from the deployed BOX are located at the bottom of the dialog box. This avoids overlapping with existing threads on the NetConfig tool.