X

Step Up to Modern Cloud Development

  • February 28, 2018

Three Quick Tips API Platform CS - Gateway Installation (Part 2)

This is Part 2 of the blog series (The first part of the series can be accessed here). The aim of the blog post is to provide useful tips, which will enable the installation of the on premise Gateway for Oracle API Platform Cloud Services. If you want to know more about the product, then you can refer here.

The following tips are based on some of the scenarios, we have observed in production.

Essentially,to get past the entropy problem, you need to do the following (for Linux):

  •    check the current entropy count by executing:

   cat /proc/sys/kernel/random/entropy_avail

  • If the entropy is low you can do any of the following:    
  •    export CONFIG_JVM_ARGS=-Djava.security.egd=file:/dev/./urandom 
  •   Install the rngd tool (if not present) and execute:

   rngd -r /dev/urandom -o /dev/random -b   

  •   You can now proceed with the gateway domain creation or domain startup.

 

  • It is possible to generate the gateway properties from the API Portal UI. Please try to leverage this functionality and download the generated property file on to the on premise machine. This will significantly reduce the effort of hand crafting the properties file which is critical for the gateway installation process. Please refer here for more details.

 

  • If you encounter scenarios where failures in the "configure" action look something like:

64040: Specified template does not exist or is not a file: "/d01/apipcs/app/oracle/gateway/run/build/apiplatform_gateway-services_template.jar".
64040: Provide a valid template location.
at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:56)
at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:2279)
at com.oracle.cie.domain.script.jython.WLScriptContext.addTemplate(WLScriptContext.java:793)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)    

The above is just an example but any file not found kind of error during the "configure" action is an indication that the previous step (which is the "install" action), did not complete successfully. Please refer to the "gatewayInstall.log" and "main.log", as this will point to why the install might have had errors even if the install process might have completed.

So  that is all for today. We will be back with more tips soon. Happy API management with the Oracle API Platform Cloud Services.    

Digital Transformation - Oracle API Platform Cloud Service

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha
Oracle

Integrated Cloud Applications & Platform Services