Bootstrap Environment

A newly provisioned APCS environment is set up with a bootstrap configuration that allows the Administrator to log and access the Online Administration Tools (OAT) interface before the domain has been built. The bootstrap OAT configuration allows only tasks required to construct a domain. Once the domain has been constructed, the domain task and the bootstrap activities will both be available. This allows the domain to be rebuilt from scratch multiple times if needed.

Before building the domain, upload the following files for building/patching to Object Storage using the File Transfer Service. Except for the input hierarchy and data files, the other files are not needed if the customer is planning to use the template GA without any extensibility.

• Configuration file as ascs_config.zip with prefix incoming/config.

• Interface Configuration file interface.cfg with prefix incoming/config

• Dashboard JSON file dashboardSettings.json with prefix incoming/config

• Batch control files as batch_control.zip or individual files with prefix incoming/batch_control

• Input hierarchy and data files with prefix incoming/input

Note:

If it is non-template, the customer is advised to use the same configuration name as GA and the hierarchy and its dimension names aligning with the GA solution for matching dimensions to allow them to move to GA later with minimal changes and to also enable them to integrate with other planning applications in the future. Though the non-template customer is allowed to use their own configuration name and other dimension names, it will not be easy to integrate with other planning applications.