Gateway Application Setup Oracle FLEXCUBE Universal Banking Release 11.3.0 [May] [2011]
Table of Contents 1. SETTING UP GATEWAY FOR ORACLE FLEXCUBE... 1-1 1.1 INTRODUCTION... 1-1 1.2 SETTING UP GATEWAY EJB APPLICATION... 1-1 1.2.1 Prerequisites... 1-1 1.2.2 Building EAR File... 1-1 1.3 SETTING UP GATEWAY MDB APPLICATION... 1-5 1.3.1 Prerequisites... 1-5 1.3.2 Building EAR File... 1-5 1.4 SETTING UP GATEWAY HTTP APPLICATION... 1-10 1.4.1 Prerequisites... 1-10 1.4.2 Building EAR file... 1-10 1.5 SETTING UP GATEWAY WEB SERVICE APPLICATION... 1-13 1.5.1 Prerequisites... 1-13 1.5.2 Building EAR File... 1-14 2. POST BUILDING ACTIVITY... 2-1 2.1 INTRODUCTION... 2-1 2.1.1 Deployment Using Oracle WebLogic Application Server... 2-1 2.1.2 Deployment Using IBM WebSphere Application Server... 2-1
1. Setting up Gateway for Oracle FLEXCUBE 1.1 Introduction This chapter explains the steps for setting up the Gateway Application for Oracle FLEXCUBE. 1.2 Setting up Gateway EJB Application This section explains the methods of setting up Gateway EJB Application. 1.2.1 Prerequisites You need to create the following gateway EJB property files before building the application: gw_ejb_logger.xml GW_EJB_Prop.xml For details, refer to the section Gateway EJB Application in chapter Setting up Property Files. 1.2.2 Building EAR File In order to build EAR file for Gateway EJB Application, you need to follow the steps given below: 1. Launch Oracle FLEXCUBE Universal Installer. The welcome screen is displayed. 2. Choose the Application Oracle FLEXCUBE Gateway. Click Next. The following screen is displayed: 1-1
3. Choose Build EAR File. Click Next. The following screen is displayed: 4. Choose Oracle FLEXCUBE Gateway EJB. Click Next. 1-2
The following screen is displayed: Specify the following details: Source Directory Specify the location of the source directory. Eg: Source_Dir\Gateway The location of the source directory can be remote or local. Destination Directory Specify the location of the destination directory. The source files from the software will be copied to this location. Application Name Specify the EAR name of the application. The application name should not contain special characters and space. However, you may use _ (usnderscore). Eg: GWEJB EAR File Path Specify the location at which the EAR file should be saved. 1-3
Property File Path Specify the location at which the property files are available. After specifying the property file path, click Load button to load the property file. Click Next. The EJB reference name will be {APPLICATIONAME}_GW_EJB_Bean and the JNDI name will be {APPLICATIONAME}/ejb/GW_EJB_Bean. For example, consider that the application name is GWEJB. In that case EJB and JNDI names will be as follows: EJB reference name: GWEJB_GW_EJB_Bean JNDI name: GWEJB/ejb/GW_EJB_Bean 5. In case of a distributed schema, the following screen is displayed. 6. Specify the Datasource Name and click ADD button to include it. You can also exclude an already added datasource by selecting it and clicking the DELETE button. 1-4
7. Click Next. The following screen is displayed: 8. Choose one of the following options: Continue Installation: If you choose this, the Installer will navigate you to the Oracle FLEXCUBE Welcome screen. Finish Installation: If you choose this, the Oracle FLEXCUBE Installation process will be terminated. The EAR file will be saved to the destination directory. 1.3 Setting up Gateway MDB Application This section explains the methods of setting up Gateway EJB Application. 1.3.1 Prerequisites You need to create the following gateway MDB property files before building the application: gw_mdb_logger.xml GW_MDB_Prop.xml For details, refer to the section Gateway MDB Application in chapter Setting up Property Files (04- PropertyFile_Setup). 1.3.2 Building EAR File In order to build EAR file for Gateway MDB Application, you need to follow the steps given below: 1-5
9. Launch Oracle FLEXCUBE Universal Installer. The welcome screen is displayed. 10. Choose the Application Oracle FLEXCUBE Gateway. Click Next. The following screen is displayed: 11. Choose Build EAR File. Click Next. 1-6
The following screen is displayed: 12. Choose Oracle FLEXCUBE Gateway MDB. Click Next. The following screen is displayed: Specify the following details: Source Directory Specify the location of the source directory. 1-7
Eg: Source_Dir\Gateway The location of the source directory can be remote or local. Destination Directory Specify the location of the destination directory. The source files from the software will be copied to this location. Application Name Specify the EAR name of the application. Eg: GWMDB EAR File Path Specify the location at which the EAR file should be saved. Property File Path Specify the location at which the property files are available. After specifying the property file path, click Load button to load the property file. Is the Destination MQ Series Check this box to indicate that the destination is a MQ series. If you check this, you need to specify the binding file path also. Binding File Path Specify the binding file path. This is applicable only of you have checked the option Is the Destination MQ Series. Eg: file://d:/bindings Once you have specified the above details, click Load button and then click Next. 1-8
13. In case of a distributed schema, the following screen is displayed. 14. Specify the Datasource Name and click ADD button to include it. You can also exclude an already added datasource by selecting it and clicking the DELETE button. 15. Click Next. The following screen is displayed: 16. Choose one of the following options: 1-9
Continue Installation: If you choose this, the Installer will navigate you to the Oracle FLEXCUBE Welcome screen. Finish Installation: If you choose this, the Oracle FLEXCUBE Installation process will be terminated. The EAR file will be saved to the destination directory. 1.4 Setting up Gateway HTTP Application This section explains the methods of setting up Gateway EJB Application. 1.4.1 Prerequisites You need to create the following gateway HTTP property files before building the application: gw_http_logger.xml GW_HTTP_Prop.xml For details, refer to the section Gateway HTTP Application in chapter Setting up Property Files (04- PropertyFile_Setup). 1.4.2 Building EAR file In order to build EAR file for Gateway MDB Application, you need to follow the steps given below: 1. Launch Oracle FLEXCUBE Universal Installer. The welcome screen is displayed. 2. Choose the Application Oracle FLEXCUBE Gateway. Click Next. 1-10
The following screen is displayed: 3. Choose Build EAR File. Click Next. The following screen is displayed: 4. Choose Oracle FLEXCUBE Gateway Servlet. Click Next. 1-11
The following screen is displayed: Specify the following details: Source Directory Specify the location of the source directory. Eg: Source_Dir\Gateway The location of the source directory can be remote or local. Destination Directory Specify the location of the destination directory. The source files from the software will be copied to this location. Application Name Specify the EAR name of the application. Eg: GWHTTP EAR File Path Specify the location at which the EAR file should be saved. 1-12
Property File Path Specify the location at which the property files are available. After specifying the property file path, click Load button to load the property file. 5. Click Next. The following screen is displayed: 6. Choose one of the following options: Continue Installation: If you choose this, the Installer will navigate you to the Oracle FLEXCUBE Welcome screen. Finish Installation: If you choose this, the Oracle FLEXCUBE Installation process will be terminated. The EAR file will be saved to the destination directory. 1.5 Setting up Gateway Web Service Application 1.5.1 Prerequisites You need to create the following gateway HTTP property files before building the application: gw_ws_logger.xml GW_WS_Prop.xml 1-13
For details, refer to the section Gateway Web Services Application in chapter Setting up Property Files 04-PropertyFile_Setup. You must create the environment variables for the corresponding application. For details, refer to the section For Gateway Web Service Application Building in chapter Setting up Oracle FLEXCUBE Installer (02-Installer_Installation). 1.5.2 Building EAR File In order to build EAR file for Gateway MDB Application, you need to follow the steps given below: 1. Launch Oracle FLEXCUBE Universal Installer. The welcome screen is displayed. 1-14
2. Choose the Application Oracle FLEXCUBE Gateway. Click Next. The following screen is displayed: 3. Choose Build EAR File. Click Next. The following screen is displayed. 1-15
4. Choose Oracle FLEXCUBE Gateway WebServices. Click Next. The following screen is displayed. 5. Specify the Application Name for the required Web Services. Check Include to include the selected Web Service. By default, the Oracle FLEXCUBE Universal Installer displays the service name as the application name. However, you can modify this. 6. Click Next. The following screen is displayed: 1-16
7. Specify the following details: Source Directory Specify the location of the source directory. Eg: Software_Source\Gateway The location of the source directory can be remote or local. Destination Directory Specify the location of the destination directory. The source files from the software will be copied to this location. EAR File Path Specify the location at which the EAR file should be saved. Property File Path Specify the location at which the property files are available. 8. After specifying the property file path, click Load button to load the property file. Click Next. 9. Oracle FLEXCUBE Universal Installer completes the build processes for the selected services. 10. In case a service fails during the build process, the following screen is displayed. You can view the list of failed services in the log file as shown below. 1-17
11. Click OK. The following screen is displayed. 12. Choose one of the following options: Continue Installation: If you choose this, the Installer will navigate you to the Oracle FLEXCUBE Welcome screen. Finish Installation: If you choose this, the Oracle FLEXCUBE Installation process will be terminated. The EAR file will be saved to the destination directory. 1-18
2. Post Building Activity 2.1 Introduction This section introduces you to the activities to be carried out after setting up the gateway applications. 2.1.1 Deployment Using Oracle WebLogic Application Server For details on the manual deployment using Oracle WebLogic Application Server, refer to the chapter Gateway Application with WebLogic (GATEWAY_Applications_WL). 2.1.2 Deployment Using IBM WebSphere Application Server For details on the manual deployment using IBM WebSphere Application Server, refer to the chapter Gateway Application with WebSphere (GATEWAY_Applications_WAS.doc). 2-1
Gateway Application Setup [May] [2011] Version 11.3.0 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 www.oracle.com/ financial_services/ Copyright [2011] Oracle Financial Services Software Limited. All rights reserved. No part of this work may be reproduced, stored in a retrieval system, adopted or transmitted in any form or by any means, electronic, mechanical, photographic, graphic, optic recording or otherwise, translated in any language or computer language, without the prior written permission of Oracle Financial Services Software Limited. Due care has been taken to make this document and accompanying software package as accurate as possible. However, Oracle Financial Services Software Limited makes no representation or warranties with respect to the contents hereof and shall not be responsible for any loss or damage caused to the user by the direct or indirect use of this document and the accompanying Software System. Furthermore, Oracle Financial Services Software Limited reserves the right to alter, modify or otherwise change in any manner the content hereof, without obligation of Oracle Financial Services Software Limited to notify any person of such revision or changes. All company and product names are trademarks of the respective companies with which they are associated.