1. Deploying Oracle Banking Trade Finance Application on WebLogic
  2. Deploying Oracle FLEXCUBE on WebLogic
  3. Deploying Application in Oracle WebLogic
  4. Deploying Gateway/Scheduler Applications from WebLogic Administration Console

1.3.4 Deploying Gateway/Scheduler Applications from WebLogic Administration Console

To deploy Oracle FLEXCUBE Gateway/Scheduler Application from Oracle WebLogic administration console, follow the steps given below.

  1. Start the Administrative Console of WebLogic application server. You can start this by entering Oracle WebLogic Admin Console URL in the address bar in an internet browser.
  2. Specify the WebLogic administrator user name and password. Click ‘Log In’.
    The following screen is displayed:
    Description of 1.3.2_s3_login.png follows
    Description of the illustration 1.3.2_s3_login.png

  3. You need to deploy an EAR. For example ‘GWEJB.ear’. Go to ‘Deployment’.
    Click ‘Lock & Edit’ button to enable the buttons. This action enables the buttons.
    Description of 1.3.2_s4_install-1.png follows
    Description of the illustration 1.3.2_s4_install-1.png

  4. Click ‘Install’ button. The following screen is displayed:
    Description of 1.3.1_s4_install.png follows
    Description of the illustration 1.3.1_s4_install.png

  5. In order to specify the path/location of the enterprise archive file, click the link ‘upload your file(s)’.
  6. Click ‘Next’. The following screen is displayed:
    Description of 1.3.3_s27_upload-your-file.png follows
    Description of the illustration 1.3.3_s27_upload-your-file.png

  7. Specify the EAR file path. You can use the ‘Browse’ button to locate the file.
  8. Click ‘Next’. The following screen is displayed.
    Description of 1.3.3_s29_specify-path.png follows
    Description of the illustration 1.3.3_s29_specify-path.png

  9. Select the application from the list.
  10. Click ‘Next’. Following screen is displayed:
  11. Choose the targeting style ‘Install this deployment as an application’.
  12. Click ‘Next’.
  13. Select the target of the application. You can choose the server ‘AdminServer’ or ‘Managed Server(s)’.
  14. Click ‘Next’. The following screen is displayed.
    Description of 1.3.3_s36_summary-deployment.png follows
    Description of the illustration 1.3.3_s36_summary-deployment.png

  15. Check the deployment name.
    The remaining portion of the screen is shown below:
    Description of 1.3.3_s35_summary-deployment-2.png follows
    Description of the illustration 1.3.3_s35_summary-deployment-2.png

  16. Check whether the deployment location is accessible or not. The following screen is displayed.
    Description of 1.3.3_s36_summary-deployment-2.png follows
    Description of the illustration 1.3.3_s36_summary-deployment-2.png

  17. Click ‘Finish’ button. The following screen is displayed.
    Description of 1.3.3_s37_finish.png follows
    Description of the illustration 1.3.3_s37_finish.png

  18. Click Save button. The message ‘Settings updated successfully’ is displayed.
    Description of 1.3.3_s38_save.png follows
    Description of the illustration 1.3.3_s38_save.png

  19. Click ‘Activate Changes’ button on the left pane. The message ‘All the changes have been activated. No restarts are necessary’ is displayed.
    Description of 1.3.3_s39_activate-changes.png follows
    Description of the illustration 1.3.3_s39_activate-changes.png

    Click ‘Deployment’ on the left pane. Switch to Control tab. The following screen is displayed.
    Description of 1.3.3_s39_deployment.png follows
    Description of the illustration 1.3.3_s39_deployment.png

  20. Click ‘Start’ drop-down button and select ‘Servicing all requests’.
  21. The following screen is displayed.
    Description of 1.3.3_s41_start-deployment.png follows
    Description of the illustration 1.3.3_s41_start-deployment.png

  22. Click ‘Yes’. The following screen is displayed.
    Description of 1.3.3_s42-deployment-process.png follows
    Description of the illustration 1.3.3_s42-deployment-process.png

    This completes the deployment process.
    1. Repeat the same steps from 1.3.3 for deploying GWWS (gateway webservices), Gateway MDB & Gateway HTTP servlet.

Parent topic: Deploying Application in Oracle WebLogic