Uploading Configurations

Technical Administrators may need to upload configuration packages, which in most cases, must be provided by your implementation partner.

For example, a configuration package may need to be uploaded in the following scenarios:

  • To apply custom features.
  • To update build configuration files that cannot be modified via the Nakisa AdminConsole. You can edit the necessary files, create a new ZIP package and upload the package.
  • To migrate configuration to new environments (e.g., from a QA environment to a production environment).
    • If your two environments require different build configuration, you must download and send your build configuration packages to your implementation partner, who will be able to exclude the configuration files that should not be overridden in the new environment (e.g., connection information).
    • If you have identical configuration between environments, you can simply download your build configuration changes and upload them in the new environment.

    Note: To do a full system copy (including data) administrators can back up the system, and restore it on the other system.

Note: Nakisa recommends that you do not export and upload the master data configuration in the Build Management module (by selecting the "Export Configuration Data" checkbox). It is better to export the application configuration and each system configuration to Excel in the Master Data Configuration module, and import these files in the new build.

Warning: If you upload the foundation build configuration package instead of a customized configuration package, you will be essentially reverting your build to its original out of the box build configuration. Note that uploading the foundation build configuration package does not override the master data configuration. If required, you can load the original default master data configuration in the Data Management module.

Once the customization package has been uploaded and published, the "Last Uploaded" and "Last Published" information is updated in the Status section. This section also provides information about the Used Space and Free Space for the space available to the application itself on the server.

To apply a customized configuration package to the current build:

  1. Click Application Menu > Build Management.
  2. Make sure you have the correct customized configuration package from your implementation partner.
  3. Click Upload Changes and select the correct file.
  4. Click Publish Changes.
  5. If changes were made to the database schema, click Application Menu > Data Management:
    1. Click Update Database Structure.
    2. Click Recreate Index.
  6. If required, go to Application Menu > Master Data Configuration to configure any new fields or tables:
    1. Sync the application with SAP to retrieve any new data.
    2. Complete any required configuration either manually, or via updated application or system Excel files. (Ensure that the Excel files exported from the previous build have been updated with new fields or tables.)

To modify configuration files in the current build:

  1. Download the delta build configuration package for modified build configuration for the current running build.
  2. Modify the files that cannot be edited in the Nakisa AdminConsole and re-zip the files.

    Warning: Make sure to zip the contents of the folder (and not the folder itself) to ensure that you do not add an extra folder level in the ZIP package.

  3. Click Upload Changes and select the ZIP package.
  4. Click Publish Changes.

To migrate customizations to a new build in a different environment:

  1. Download the delta build configuration package for modified build configuration for the current running build.
  2. If required, unzip the package and remove the files that are not needed (if you are aware of the exact files to exclude), and re-zip the package.
    • If you cannot make the required changes yourself, send the downloaded package as well as the foundation build configuration package to your implementation partner, and wait to receive the updated merged package.

    Warning: Make sure to zip the contents of the folder (and not the folder itself) to ensure that you do not add an extra folder level in the ZIP package.

  3. If required, in the Master Data Configuration module in the current running build, export the application configuration and/or system configuration to Excel. These files can be used as reference.
  4. Ensure that the build version in the new environment is the same as the build version in the current environment.
  5. In the new environment, go to Application Menu > Build Management.
  6. Click Upload Changes and select the correct file.
  7. Click Publish Changes.
  8. If changes were made to the database schema, click Application Menu > Data Management:
    1. Click Update Database Structure.
    2. Click Recreate Index.
  9. Go to Application Menu > Master Data Configuration.
    • If this is the first time the build is deployed in the new environment, build and configure the Master Data Configuration.
    • If this is not the first deployment in the environment, update the Master Data Configuration accordingly.

See also:  

Nakisa Lease Administration 2022.R2-SP © 2024

 

 

Nakisa Inc. All rights reserved worldwide.