How to Correctly Alter Oracle API Gateway Windows Services to Start After Performing Upgrade (Doc ID 2108666.1)

Last updated on FEBRUARY 24, 2016

Applies to:

Oracle API Gateway - Version 11.1.2 and later
Information in this document applies to any platform.

Goal

To upgrade an OAG installation to the 11.1.2.4.0 version, it is necessary to follow the upgrade instructions in the Oracle API Gateway Installation Guide 11g Release 2 (11.1.2.4.0) documentation.

Scenario:

The original installation is on Windows and both the nodemanager and the gateway were being run as Windows services. 

Under the 'Upgrade and migration' >> 'Additional steps for upgrade from 11.1.2.x' section, the following is stated:

"Node Managers and API Gateways as a service – If any of your processes are running as a service, you must manually update the services with the new settings."


To perform this, the following is being run to change the execution path for the Gateway service:


Even after a server re-boot, neither service will start. Both processes started properly when the upgrade process completed (ie, from the .bat files).

What is incorrect in the process being used?
How can the services information be altered to allow for them to start up?
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms