Upgrading Akana API Platform to Version 2019.0.x

Learn how to upgrade the Akana API Platform from an earlier version to version 2019.0.x.

These upgrade instructions cover the process for a manual upgrade, creating new containers. Automation options are also available (Linux only).

This upgrade addresses a simple container scenario of:

  • One container with Policy Manager and Community Manager installed
  • One container running the API Gateway (Network Director)

The documentation includes some notes and additional information that would be applicable if you're creating other container scenarios—for example, if you have multiple PM/CM containers, or a separate Scheduled Jobs container—but the main path is to create these two containers.

Note: If you're upgrading Policy Manager for DataPower, follow the steps in this document that you would use for upgrading Network Director.

This document covers instructions for:

  • Upgrading from any earlier major/minor version to 2019.0.x.
  • Upgrading from any 2019.0.x version to a later 2019.0.x version (minor-version upgrade). For additional notes, see Minor-Version Update Notes.

You can also use automation to standardize the upgrade process (Linux only). Automation might take a little more time to set up, but it has great benefits including standardization and reusability. For information on automation, see Automation Reference. For information about which automation recipes to use for upgrade, see Automating the upgrade.

Note: Previous versions of this document recommended an incremental approach, upgrading from one major version to the next and then to the next. Incremental upgrade is not necessary. You can upgrade from an earlier version to the latest version in one upgrade process.

Using Admin Console Installing Tools Installing Plug-ins Configuration Actions Automation Reference

Supported Platforms: 2019.0.x

Table of Contents

Planning the Upgrade
  1. Upgrade strategy
  2. Overview
  3. Step 1-1: Review release notes
  4. Step 1-2: Plan the upgrade
  5. Step 1-3: Install and configure Elasticsearch (if not already done)
Performing the Upgrade
  1. Overview
  2. Step 2-1: Gather ZIP file or files and download to a temporary folder
  3. Step 2-2: Shut down and back up the previous version
  4. Step 2-3: Extract installation files in the correct sequence
  5. Step 2-4: Verify that Elasticsearch is running
  6. Step 2-5: Create and configure the first container
  7. Step 2-6: Create and configure additional containers
Post-Upgrade Tasks
  1. Step 3-0: Upload PKI keys and certificate
  2. Step 3-1: Check for pending installation tasks
  3. Step 3-2: Perform configuration actions
  4. Step 3-3: Update container properties
  5. Step 3-4: Check system health
  6. Step 3-5: Configure Elasticsearch
  7. Step 3-6: Restart all containers
  8. Step 3-7: Configure API Gateway/Network Director
Upgrade Procedures/Reference:
  1. Launching the Akana Administration Console
  2. Checking that features were installed correctly
  3. Turning the scheduled jobs off
  4. Turning the scheduled jobs back on
  5. Unregistering and re-registering the Windows service
  6. Starting a container
  7. Refreshing the repository
  8. Upgrading by creating a new container and re-using the old container identity: note
  9. Automating the transfer of container properties
  10. Automation recipes for upgrade
  11. Contacting Technical Support

Planning the Upgrade

Upgrade strategy

There are several approaches you can take to upgrading:

  1. Manual upgrade, creating new containers, and then configuring the new containers to suit your requirements. This is essentially a fresh install.
  2. Manual upgrade, creating new containers and then transferring the identity, services, and settings from an existing container in your previous installation, to the new container. This documentation steps through that approach. Essentially you are creating a new container and then using it to replicate an old one.
  3. Automated upgrade, using automation recipes to help make your upgrade faster, more standardized, and more error-free. For information on automation, see Automation Reference. For information about which automation recipes to use for upgrade, see Automating the upgrade.

This documentation takes you through the steps to create new containers and then transfer existing settings to the new container (#2 above). For example, in Step 3-0: Upload PKI keys and certificate you'll upload the same certificate that you used for the old container, from your secure external storage location to the new container.

Some of the steps are the same for all approaches.

back to top

Overview

These instructions address the scenario of creating new containers for your 2019.0.x installation.

There are some steps you might need to take before starting the upgrade process, and some information you'll need to consider that might affect how you proceed, including:

back to top

Step 1-1: Review release notes

Review the release notes so that you are aware of changes to the platform. Check for upgrade notes.

Release notes are available from the Rogue Wave Support Center (https://library.roguewave.com) or the Rogue Wave documentation site (https://docs.roguewave.com/en/akana/release_notes/2019/AAP_2019_Release_Notes.html).

back to top

Step 1-2: Plan the upgrade

Before you start downloading and installing, plan your upgrade. In particular, you'll need to:

  1. Examine your existing installation and make sure you've saved out the following information:
    • Number of containers.
    • A list of the features and add-ons installed in each container.
  2. Conditional: If standalone Elasticsearch is new for your implementation, determine where you'll install Elasticsearch, needed for the search feature. For full information on Elasticsearch, see Installing and Configuring Elasticsearch.
  3. In the Admin Console for each of your containers, review the features and add-ons that are installed, and note that information so that you can replicate it in the new containers.

    Note: If the features installed in your own implementation don't match the examples given in the procedures below, when creating your new containers, install the features that were in the previous implementation.

  4. Take all steps needed to save out container settings so that you can reproduce the configuration on the new container, where applicable. You'll need this information for Step 3-3: Update container properties. Do the following:
    • Save the context root.
    • Save all other container properties that you've customized.

      Note: you can use an automation task to save out the configuration settings (Linux only). See Extracting and Analyzing Recipes.

  5. Update the properties file for each existing container to add a new property, container.key, that specifies the existing container IDs. For example:
    container.key="fcd54dc8-ccd2-439f-a580-436d3ef2"
  6. Make sure you have the certificate that you used to create the original container. You can then upload the certificate when configuring the new container. See Step 3-0: Upload PKI keys and certificate.

back to top

Step 1-3: Install and configure Elasticsearch (if not already done)

Versions 2018.0.0 and later require standalone Elasticsearch.

For instructions, see Installing and Configuring Elasticsearch.

back to top

Performing the Upgrade

Overview

Note: The instructions in this document are for upgrade from Akana API Platform 2018.0.x to Akana API Platform 2019.0.x. If you're upgrading from an earlier version, you'll need to perform additional steps first, to upgrade to version 2018. See Upgrading the Akana API Platform (all versions).

At a high level, to perform the upgrade, you'll complete the following actions:

  1. Shut down the previous version and make a complete backup of the installation folder, and store it in a safe place.
  2. Extract installation files in the correct sequence.
  3. Verify that Elasticsearch is running.
  4. Create containers.
  5. Configure the containers and test the installation

back to top

Step 2-1: Gather ZIP file or files and download to a temporary folder

The first step is to download the required ZIP files to a temporary folder. From there, you'll unzip the files into your installation folder. You'll need to:

  • Create a temporary folder for the downloaded ZIP file.
  • Create a folder for your 2019.0.x installation; for example, aap201900.
  • Download the ZIP file for version 2019.0.0.

For detailed instructions on this step, refer to the installation guide, Gather ZIP file or files and download to a temporary folder.

Note: For notes about limitations and extra steps for specific databases, see Supported databases (installation doc). If you're using a MySQL database with API Platform and the Lifecycle Repository feature, see Database notes: MySQL with Lifecycle Repository.

Depending on the scenario, you might also need one or more of the following files:

  • Plug-ins: The ZIP file, and any updates, for any plug-ins you want to use in your installation.
  • Updates: not applicable to version 2019.0.0 itself, but for future updates.

If you have a specific add-on feature installed, such as the Integration Services option pack, SiteMinder Security Provider, or SAML Web SSO Security Provider feature, it's important that you download the new release version package for the same feature.

back to top

Step 2-2: Shut down and back up the previous version

  1. Shut down all containers in your installation.
  2. Copy the entire installation folder structure to a secure backup location.
  3. Make sure you have a backup of your database also.
  4. Create a new folder for your new installation.

Back to top

Step 2-3: Extract installation files in the correct sequence

The next step is to extract the files, following the exact sequence below.

Note: You'll need a password to unzip the files. If you don't know the password, contact your Akana representative.

To unzip the installation files
  1. In the temporary folder that you created for the downloaded ZIP file in step 2-1, unzip the downloaded ZIP file.
  2. Unzip the Akana Platform 2019.0.0 file to the folder for your installation.
  3. When the previous step is complete, unzip the Akana API Platform 2019.0.0 file to the folder for your installation.

    For example:

    unzip -o /akana/downloads/akana-platform-linux-jre-2019.0.0.5.zip -d /akana/aap201900
    unzip -o /akana/downloads/api-platform-2019.0.0.153.zip -d /akana/aap201900

    For information about the folders and folder contents for the Akana Platform, see Installation folder structure (Akana Platform).

  4. If applicable, unzip and install any updates to the Akana Platform and then the Akana API Platform. Follow the instructions in the installation documentation: Step 2-2: Extract installation files in the correct sequence.
  5. If applicable, unzip any add-on products, such as the SAML Web SSO Security Provider.

Back to top

Step 2-4: Verify that Elasticsearch is running

Elasticsearch is a separate installation. Make sure it's installed successfully and is running.

For example, run this command:

ps -ef

If there is response content, Elasticsearch is running. For example:

/usr/share/elasticsearch/modules/x-pack/x-pack-ml/platform/linux-x86_64/bin/controller

See also:

Back to top

Step 2-5: Create and configure the first container

Create the first Community Manager/Policy Manager container. For features to install, see Community Manager/Policy Manager container features with access to MongoDB. Follow the linked steps in the Installation Guide.

Note: In creating the containers, make sure that you set up at least one container running Policy Manager before you set up the Network Director container.

To create and configure the first container
  1. Run Configurator to create the first container, either via the GUI or using silent install. See Step 3: Run Configurator to create the first container.
  2. Copy the configuration properties file from the old container, which you saved out and updated with a new container.key property in Step 1-2: Plan the upgrade (procedure step #5), to the new container. Then start the new container.
  3. Install Policy Manager/Community Manager. See Step 4: Install Policy Manager/Community Manager features on the container (installation doc).
  4. At the Installation Complete summary, click Configure to complete pending tasks. See Step 6: Complete pending tasks to configure container features. The pending tasks are:
    1. Manage PKI Keys wizard (Generate PKI Keys & X.509 Certificate page).

      See Installation wizard: Manage PKI Keys (Akana Administration Console doc).

    2. Configure Database Options wizard (Select Database Options page): here, choose Use Existing Database and put in the values and credentials for the database from your prior version of the Akana API Platform.

      See Installation wizard: Add Database (installation doc).

      Note: Depending on the database you're using, you might need to put a database driver in place, or take some other steps.

      See Database notes and Database drivers (installation doc).

    3. Manage Schemas wizard (Install Schemas page): Manages the database schemas for the container.

      See Installation wizard: Manage Schemas (installation doc).

    4. Create Policy Manager Admin User (Define Policy Manager Administrator Credentials page): Creates the top-level Policy Manager user.

      See Installation wizard: Define Policy Manager Administrator Credentials (installation doc).

    5. Provisioning: Initializes resources associated with the features installed on the container.

      See Installation wizard: Provisioning (installation doc).

  5. At the Restart prompt, to install the plug-ins before restarting, press Cancel.
  6. If applicable, install plug-ins. See Step 5: (as needed) Install plug-ins on the container.
  7. Restart the container. For instructions, see:

back to top

Step 2-6: Create and configure additional containers

Once you have the first container set up, it's time to create and configure additional containers. Essentially you'll follow the same set of steps as above, for these additional containers:

  1. Optional: Subsequent Community Manager/Policy Manager containers. If you're following the sample deployment scenario, see Community Manager/Policy Manager container features with access to MongoDB.
  2. Network Director container. For features to install, see API Gateway/Internal Gateway (Network Director). For Network Director, pending tasks include:
    1. WS-Metadata Exchange Options: see Installation wizard, ND container: Configure WS-Metadata Exchange Options.
    2. Manage PKI Keys wizard (Select Key Management Option page): see Installation wizard: Manage PKI Keys.
  3. OAuth container. For features to install, see OAuth Provider.
  4. Scheduled Jobs container. For features to install, see Job Scheduler.

Note: In each case, be sure to copy the configuration properties file from the old container, which you saved out and updated with a new container.key property in Step 1-2: Plan the upgrade (procedure step #5), to the new container.

Create containers in this sequence:

  1. First, create all Policy Manager/Community Manager containers.
  2. Then, create all Network Director containers.

    You can create a Network Director container using either GUI or Silent options. For instructions on how to install a Network Director Container (ND1), install and configure the Network Director feature, and register the ND1 container in Policy Manager, refer to Using the Network Director Feature.

For information about the features and plug-ins to install for additional container configurations, see Sample Deployment Scenarios (Install doc).

back to top

Post-Upgrade Tasks

Post-upgrade tasks: overview

Once you've completed the product version update, there are additional post-upgrade tasks you'll need to complete. Some of these steps are conditional depending on platform features you're using. They include:

back to top

Step 3-0: Upload PKI keys and certificate

Upload the container certificate from your secure external location. You'll need to upload a .JKS or .P12 file.

In the Akana Administration Console for the container, go to Configuration > Manage PKI Keys and choose Import Private Key & X.509 Certificate. See Manage PKI Keys.

For general information about container identity in the context of upgrading, see Managing Container Identity Across Upgrades.

back to top

Step 3-1: Check for pending installation tasks

When you've created all containers, check for pending installation tasks in each container.

In the Akana Administration Console, under Installed Features, check at the bottom of the page under Pending Installation Tasks.

If any are listed, click Complete Configuration.

An example is shown below.

Pending installation tasks
  • Manage PKI keys: Specifies key management options.
  • Add Database: Creates the database for the installation.
  • Manage Schemas: Manages the database schemas for the container.
  • Create Policy Manager Admin User: Creates the top-level Policy Manager user.
  • Provisioning: Initializes resources associated with the features installed on the container.

Note: All these configuration actions are also available under Configuration > Configuration Actions. For more information on configuration actions, see Using Configuration Actions.

back to top

Step 3-2: Perform configuration actions

If you're upgrading from a previous version, it's a good idea to run the following configuration actions, even if they were not listed under Pending Installation Tasks:

To perform provisioning
  1. In the Akana Administration Console, click the Configuration tab.
  2. In the Configuration Actions section, choose the Provisioning configuration action, as shown below.

    Running Provisioning manually

  3. On the Provisioning page, make sure Perform Provisioning is checked, as shown below, and then click Finish.

    Note: Make sure the Provisioning task is 100% complete before moving to the next task.

    Provisioning Summary

  4. When provisioning is 100% complete, click Close.
To complete the Upgrade CM Models configuration action
  1. In the Akana Administration Console, click the Configuration tab.
  2. In the Configuration Actions section, choose Upgrade CM Models.
  3. When done, click Close.

The Rebuild CM Styles task makes sure that you have the latest style updates, for all themes and tenants.

To rebuild CM styles
  1. In the Akana Administration Console, click the Configuration tab.
  2. In the Configuration Actions section, choose Rebuild CM Styles.
  3. When done, click Finish.

back to top

Step 3-3: Update container properties

When you've created the new container and installed the features, it's time to set the configuration properties. You'll need to transfer any customized settings that were set on the old container, to the new container.

Use the setting values that you saved out in Step 1-2: Plan the upgrade, procedure step #4, and set them on the new container.

For example, if you customized the Content Root value for the developer portal, you'll need to re-set it.

In the Akana Administration Console for each container with Community Manager installed:

Configuration > com.soa.atmosphere.console > atmosphere.context.root.

For example, /acmepaymentscorp.

For detailed instructions, see Conditional: updating configuration setting for new context root (installation doc).

back to top

Step 3-4: Check system health

Log into the Akana Administration Console for the PM/CM container and check the system health (Health tab).

back to top

Step 3-5: Configure Elasticsearch

The developer portal is now available, but search will not work until you configure Elasticsearch.

Note: These steps assume that Elasticsearch is already installed and configured. See Step 1-3: Install and configure Elasticsearch (if not already done).

Steps:

  1. Configure global settings
  2. Clear the Elasticsearch index
  3. Check Elasticsearch status
  4. Restart the container
  5. Verify that search is working
Configure global settings

As part of installation or upgrade, you'll need to configure a couple of global settings in the Akana Administration Console so that the Elasticsearch feature will work correctly.

In the Akana Administration Console for any one container:

Configuration > Configuration Actions > Configure Elasticsearch Global Configuration.

For instructions, see How do I configure Elasticsearch?

Clear the Elasticsearch index

You'll need to clear out the old Elasticsearch index so it can be refreshed. To do this, complete these two steps, at the same time:

  • Empty the INDEX_STATUS table in the database by running this database command:
    delete from {database_name}.INDEX_STATUS;

    For example:

    Clearing the Elasticsearch index

  • Delete the index folders from their storage location, so that new index folders will be created when the index is regenerated.
Check Elasticsearch status

You can use the Elasticsearch API to check the status of your Elasticsearch, to make sure all is running smoothly. In the below, substitute the node where Elasticsearch is running:

GET {protocol}://{hostname}:{port}/

The response is a JSON object with information about your Elasticsearch. For more information, refer to the Elasticsearch website: Connect to Elasticsearch.

Restart the container

Stop and restart the container.

For instructions, see:

Verify that search is working

Log in to the developer portal user interface and verify that search is now working. For example, search for an API or an app.

This completes the Elasticsearch steps.

back to top

Step 3-6: Restart all containers

After running the configuration actions on all containers, stop and restart all containers.

For instructions, see:

back to top

Step 3-7: Configure Network Director

The next step is to create the API Gateway, in the developer portal.

To set up the API Gateway in the developer portal
  1. Go to the URL you set up for the developer portal, and log in using the default credentials you used to create the developer portal.
  2. Go to Admin > API Gateways and choose Register API Gateway.
  3. On the Register API Gateway page, set up the following values:
    • A short intuitive name. For example: ND1.
    • Metadata Auto-Discovery: Set up the metadata URL for the Network Director container in Step 2-6: Create and configure additional containers, using the URL you set up for the container and appending /metadata. For example: http://localhost:9902/metadata. If the URL is secure, click Specify Credentials and enter username and password.
  4. For more information about the fields on this page, see How do I register an API Gateway? (developer portal help).
  5. Click Save.
  6. In the developer portal user interface, modify the deployment zone to use the new Network Director (Admin > Deployment Zones). For instructions, see How do I make changes to a deployment zone? (developer portal help).
  7. Test to make sure that the new Network Director is working correctly.

back to top

Upgrade Procedures/Reference

Launching the Akana Administration Console

Installation and configuration tasks are performed in the Akana Administration Console for the container. First you create the container, and then you install features into the container and configure them.

To launch the Akana Administration Console
  1. Launch the Akana Administration Console for the container instance:
    http://{hostname}:{port}/admin
  2. Log in to the Akana Administration Console as an Administrator. The Akana Administration Console launches and displays the Available Features tab. See Installation Options: Full List (installation doc).

back to top

Checking that features were installed correctly

When you've installed features in a container, it's a good idea to check to make sure that features have been installed correctly.

  1. In the Akana Administration Console, go to Installed Features.
  2. Look at the Version column to make sure each feature has the correct version number. An example is shown below.

    Features installed tab: 2019.0.0

If there are any issues, check that you followed all steps correctly.

If needed, contact Technical Support.

back to top

Turning the scheduled jobs off

If you turn off the scheduled jobs, turn off these two jobs, for all containers with Policy Manager installed, in this sequence:

  1. com.soa.scheduler.quartz
  2. simple.scheduler.enabled
To turn off scheduled jobs
  1. Log in to the Akana Administration Console using Administrator credentials.
  2. Click the Configuration tab.
  3. In the Configuration Categories section, find com.soa.scheduler.quartz.
  4. Locate the org.quartz.scheduler.enabled property and change it to false.
  5. Click Apply Changes.
  6. In the Configuration Categories section, find com.soa.scheduler.
  7. Locate the simple.scheduler.enabled property and change it to false, as shown below.

    Turning off scheduled jobs

  8. Click Apply Changes.

back to top

Turning the scheduled jobs back on

If you turned the scheduled jobs off, and are ready to turn them back on again, turn them on in this sequence, the reverse of the sequence in which you turned them off, for all containers with Policy Manager installed:

  1. simple.scheduler.enabled
  2. com.soa.scheduler.quartz
To turn scheduled jobs back on
  1. Log in to the Akana Administration Console using Administrator credentials.
  2. Click the Configuration tab.
  3. In the Configuration Categories section, find com.soa.scheduler.
  4. Locate the simple.scheduler.enabled property and change it to true.
  5. Click Apply Changes.
  6. In the Configuration Categories section, find com.soa.scheduler.quartz.
  7. Locate the org.quartz.scheduler.enabled property and change it to true.
  8. Click Apply Changes.

back to top

Unregistering and re-registering the Windows service

If your containers are registered as a Windows service, so that the container will start automatically when Windows starts, you must unregister the old version and register the new version, for each container.

If you're not sure which containers are registered as a Windows service, you can check in the Windows Control Panel (Administrative Tools > Services). To change the services, you must run as Administrator.

To unregister and register the Windows service
  1. Open a command prompt in Administrator mode (If you don't use Administrator mode, Windows prompts for Admin permission before unregistering/registering the service, but doesn't actually start the service).
  2. Unregister the previous version as a windows service:
    .\{install_folder}\bin\unregisterContainerServiceYAJWS.bat {instance_name}
  3. Register the new version as a Windows service:
    .\{install_folder}\bin\registerContainerServiceYAJWS.bat {instance_name}
  4. If you're running in Administrator mode, Windows registers the service and also starts it.
  5. Repeat steps 2 and 3 for each additional container that's registered as a Windows service.

back to top

Starting a container

There are several ways you can start a container: Windows, as Windows service, or Unix. Follow the applicable procedure:

To start the container (Windows)
  1. Navigate to the \{install_folder}\bin\ folder.
  2. Type the following:
    startup {instance_name}
To start the container (as Windows service)
  1. Launch the Program Group (Settings > Control Panel > Administrative Tools > Services).
  2. Select the Akana Container Instance (the instance name is displayed as the Container Key).
  3. From the Actions menu, select Start.
To start the container (Unix)
  1. Navigate to the /{install_folder}/bin/ folder.
  2. Type the following:
    startup.sh {instance_name}
To start the container (Unix, Background)
  1. Navigate to the /bin folder.
  2. Type the following:
    startup.sh {instance_name} -bg

back to top

Refreshing the repository

Verify that the repository is there. Refresh if needed.

To verify/refresh the repository
  1. Click the Repository tab and verify that the Akana Platform Repository and the Akana API Platform Repository are both present, as shown below.

    Repository tab: 2019.0.0

  2. Conditional: if you don't see both these repositories, click Refresh to update.

Further installation steps are conditional:

  • If your container doesn't have Policy Manager features installed (Akana Policy Manager Console and Akana Policy Manager Services), the upgrade is complete.
  • If your container does have Policy Manager features installed (Akana Policy Manager Console and Akana Policy Manager Services), continue.

back to top

Upgrading by creating a new container and re-using the old container identity: note

When you're upgrading by creating new containers, and then using the same identity as the old container, it's important that you delete the existing container from the Policy Manager workbench before creating the new container.

If you don't delete the old container before creating the new one, you might encounter an error on the provisioning step, similar to the one shown below (WSDL binding cannot be disassociated from service):

[425] com.digev.fw.exception.GException: Wsdl binding [uddi:4b0aba1c-8ca7-e61c-5575-25361578c179] 
cannot be disassociated from service [uddi:soa.com:metadataattachment-servicekey]. 
Binding is attached to service endpoint.

If you encounter this message, delete the old container, and then retry the provisioning.

If you're upgrading by creating completely new containers, with a new container identity, this is of course not a problem.

Back to top

Automating the transfer of container properties

When upgrading by creating a new container, you'll need to transfer, or re-create, the configuration settings on the new container.

The configuration settings are stored in the instances/{container_name}/cm subfolder.

Because there are changes between versions, you can't just copy and paste the folder between versions. However, you can use an automation recipe to extract the old settings so that you can use them for the new container (Linux only).

To transfer configuration properties from an old container to a new container
  1. At the beginning of Step 2-5: Create and configure the first container, after shutting down the old container and before creating the new one, run discovery on all of the containers in the previous installation, and save out the old configuration settings for all containers.
  2. At the end of Step 2-5: Create and configure the first container, Step #6, after doing the initial configuration steps, shut down the container. Rather than restarting as in Step #7, save out the new configuration settings at that point.
  3. Compare the new settings with the old settings to arrive at the settings that will need to be configured on the new container.
  4. If available, use automation to update the container configuration.
  5. Now complete Step 2-5: Create and configure the first container by restarting the container, and verify that the configuration properties are set correctly.
  6. Follow steps 2 through 5 for additional containers until they are all configured.
  7. Continue with the post-install steps.

Back to top

Automation recipes for upgrade

The table below lists some of the automation recipes you could use to automate the upgrade process.

Recipes are in the {install_dir}/recipes folder of your installation.

Note: Automation is valid for Linux only (not for Windows).

Use this recipe... To...
cm-upgrade Perform CM upgrade recipe.
pm-cm-new-upgrade Create new PM/CM container on an existing database and perform any upgrade tasks.
pm-cm-upgrade Perform PM/CM upgrade recipe.
pm-upgrade Perform PM upgrade recipe.
register-container.json Register the Network Director container (Step 3-7: Configure API Gateway/Network Director).
Upgrade recipe example: registering the Network Director container

The example below shows using an automation recipe to register the Network Director container (Step 3-7: Configure API Gateway/Network Director).

Command:

./jython.sh -Dorg.slf4j.simpleLogger.logFile=System.out -m akana.container --recipe ../recipes/register-container.json --props register.properties

Recipe:

#*************************************************************
# Register the ND
#*************************************************************
cd /opt/akana/AAP_2019x/bin

echo "ORG_KEY=uddi:soa.com:registryorganization" > register.properties
echo "CONTAINER_NAME=nd" >> register.properties
echo "DEFAULT_PORT=9905" >> register.properties
echo "PM_SCHEME=HTTP" >> register.properties
echo "PM_PORT=9900" >> register.properties
echo "PM_HOST=akana-test.aws.akana.roguewave.com" >> register.properties
echo "INSTALL_DIR=/opt/akana/AAP_2019x" >> register.properties

Back to top

Contacting Technical Support

If you need to contact Technical Support, submit an email to support@akana.com.

When sending a support query, please provide the following information:

  • Your name
  • Email address
  • Subject
  • As much information as possible regarding your question.

You'll receive an acknowledgment email and one of our support staff will contact you.

You can also access the Support site at https://servicedesk.akana.com/servicedesk/customer/user/login.

Back to top