2 Install/Patch Domain

This chapter describes the process to install or patch a domain.

Self Service - Installing the MFP Cloud Service Application from the Bootstrap Domain

This section describes the process of installing MFP Cloud Service from the bootstrap domain with retailer data and generated configuration for the plug-in options. Once RPAS CE and MFP Cloud Service are installed in the Oracle Cloud environment, the Administrator will have the option to overwrite and install the domain with GA data or with retailer data. The Administrator also has the option to generate the configuration for different plug-in options.

Bootstrap Environment

A newly provisioned MFP CS 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 both will be available. This allows the domain to be rebuilt from scratch multiple times if needed.

Installation from the Bootstrap Domain

The following steps take you through the process of building a customer domain for MFP Cloud Service using the bootstrap domain:

After installing MFP Retail Cloud Service or MFP Cost Cloud Service, log in to the bootstrap domain as an Administration user.
In the Tasks list, select Admin Tasks for RPASCE Bootstrap and then Online Admin Tools. Click Submit a New Admin Task.

Figure 2-1 Admin Tasks for RPASCE Bootstrap Task
Select the Build MFP Domain task and click Next.

Figure 2-2 Select Build MFP Cloud Service Domain Task
Set the arguments for the task:

Figure 2-3 Select Build MFP Cloud Service Domain Task Arguments
1. Enter the Task Label and an Offline Mode Message.
2. To generate a configuration from the plug-in, check the Generate Configuration from the Plug-in checkbox and then select the plug-in option to use. In the above figure, the Configuration Options Local Currency and Wholesale Franchise are selected and Actual Load Intersection is selected as Item.
  
  For information on plug-in choices and details, see the Oracle Retail Merchandise Financial Planning Cloud Service Implementation Guide.
3. If the domain was already created and needs to be overwritten, select Overwrite Existing Domain.
4. If Use Default GA Data is not selected, the customer input hierarchy and data files should have already been uploaded. If the sample GA Data needs to be used, select this Boolean.
5. Select Run Post Batch after the Doman Build option, if the initial batch process needs to run after the domain build. This is optional and can be run from the Online Administration Tools as a batch task after building the domain.
6. If Use Extensible Config? is selected, the customer should upload the extensible configuration, created from the GA configuration as
  <app_name>_config.tar.gz to the FTP config directory. The customer can also upload the corresponding input files as <app_name>_input.tar.gz to the FTP input directory and upload the custom batch control files as
  batch_control_cust.tar.gz to the FTP batch_control directory. The process will first validate if the uploaded extensible custom configuration and batch files are valid; only if it is valid, will the domain be built. If the customer uses the Extensible Config option, there is no need to choose any plug-in option as it will use the plug-in options used by uploaded extensible configuration.
7. After choosing all the necessary options, click Next.
Select the time to schedule the task and click Next. Click Run ASAP if the Administrator wants to run the task now or the task can be scheduled by selecting the Run on a Schedule option.

Figure 2-4 Schedule Task
Review the selections and click Finish.

Figure 2-5 Verify and Confirm Selections
After submitting, review the status of that task in the dashboard similar to any other standard administration tasks.
After the task is successfully completed, log out and log in to the application to view the additional tasks specific to the newly built domain.

Note:

Users will not be allowed in the application while building and patching the domain.

Self Service - Patching the MFP Cloud Service Application

This section describes the process of patching the MFP Cloud Service application using the Online Administration Tools. Once the RPAS CE and MFP Cloud Service upgrade patches are installed in the Oracle Cloud environment, the MFP application will be patched by default with the latest configuration with the last used plug-in options or use the last used extensible configuration, if it was uploaded by customer. However, if the customer wants to reapply the patch with changes to the plug-in option or use an updated extensible configuration, the customer can use this task. Before scheduling this task, the Administrator should ensure that no users are logged in to the application while patching the solution.

The following steps walk you through the process to patch the MFP Cloud Service application as an Administration user:

After installing MFP Retail Cloud Service or MFP Cost Cloud Service, log in to the application as an Administration user.
In the Tasks list, select Admin Tasks for MFP CS Retail CS for MFP Retail (or MFP CS Cost CS for MFP Cost) and then Online Admin Tools. Click Submit a New Admin Task.

Figure 2-6 Admin Tasks for MFP CS Retail Task
Select Patch Domain Task and then click Next.

Figure 2-7 Select Patch Domain Task
Set the arguments for the task:

Figure 2-8 Select Patch MFP Cloud Service Domain Task Arguments
1. Enter the Task Label and Offline Mode Message.
2. To generate a configuration from a Plug-in, check the Generate Configuration from Plug-in checkbox and then select the plug-in option to use. In the above figure, the Configuration Option Wholesale Franchise is selected and Actual Load Intersection is selected as Item.
  
  For information on plug-in choices and details, see the Oracle Retail Merchandise Financial Planning Cloud Service Implementation Guide.
3. If Use Extensible Config? is selected, the customer should upload the extensible configuration, created from the GA configuration as
  <app_name>_config.tar.gz to the FTP config directory. The customer can also upload the corresponding input files as <app_name>_input.tar.gz to the FTP input directory and upload the custom batch control files as
  batch_control_cust.tar.gz to the FTP batch_control directory. The process will first validate if the uploaded extensible custom configuration is valid; only if it is valid, will the domain be built. If the customer uses the Extensible Config option, there is no need to choose any plug-in option as it will use the plug-in options used by uploaded extensible configuration.
4. If Do Not Update Styles? is selected, the patching process will not update the styles. The preferred option is to always update styles during patching. The customer can use this if they want to override that default option.
5. After choosing all the necessary options, click Next.
Select the time to schedule the task and click Next. Click Run ASAP if the administrator wants to run the task now or the task can be scheduled by selecting the Run on a Schedule option.

Figure 2-9 Schedule Task
Review the selections and click Finish.

Figure 2-10 Verify and Confirm Selections
After submitting, review the status of that task in the dashboard similar to any other standard administration tasks.