More4Apps Mobile - Installation and Configuration Guide

Transcription

1 More4Apps Mobile - Installation and Configuration Guide Last updated: 27 June 2018 Table of Contents 1. Overview Mobile Applications - Installation and Configuration Steps - Installation and Configuration Download the Server Installation Files Server Installation Server Install - R12.1 Customers Only Server Install - R12.2 Customers Only Server Install - R11i Customers Only Install the More4Apps Mobile Applications on your Mobile device Configure More4Apps Mobile Applications... 15

2 1. Overview Mobile Applications - Installation and Configuration The More4Apps Mobile Applications for Oracle E-Business Suite use a web-based connection to communicate with the server for all uploads and downloads (not SQL*Net). The server-side installation consists of a Servlet to be installed in the E-Business Suite mid-tier framework. The More4Apps Mobile Android Applications are very secure as they utilize the existing Oracle Applications security and login mechanisms for user authentication and authorization. Users connect using their regular E Business Suite usernames and passwords. Key Features: Full integration with the Oracle Applications login and security functionality Respect for session timeout rules Single Sign On integration Supports non-apps schemas i.e. Oracle On Demand (OOD) All versions of R11i and R12 supported from onwards HTTPS support Components: Mobile Device Apps Each Android or Apple device requires an installation of the individual transaction Applications. You can download the Apps from either the Google Play or itunes Store, just search on More4Apps. Server packages There are no database packages or scripts required. Application Settings When the App logs into an instance for the first time it will automatically create several Profile Options. Many of these are for internal use by the applications (e.g. to store the license key). Some applications have profile options used to enable/disable functionality. These profile options are documented in the product-specific online documentation. Note- On some devices the login will fail at first attempt. To fix this just login again. Mid-Tier Servlet A mid-tier servlet is installed to facilitate communication between the Android Applications and the database. Minimum Software Requirements (anything at or above these versions is fine): Server: o E-Business Suite o J2SE 1.5 o Database 9i Android device:

3 o Android 2.1 (Éclair) XML Communication Technical Description: The communication protocol between the Mobile Applications and the E-Business database server is HTML and XML. The Android App authenticates then communicates with the E-Business web tier in the background, in the same way that an end-user would in an Oracle Self-Service browserbased product such as Internet Time. The Mobile App makes HTML calls to the servlet. Parameters are passed using the POST structure. The servlet verifies the authentication of the calling App. If the calling App has not yet logged in then the E-Business login screen is presented to the user. (If SSO is enabled then the user is automatically forwarded to the SSO login screen). The user then logs in with their usual E- Business username/password. The session will expire if the user logs out or closes the App, or if they are idle for a long period. Licensing: Licensing is done by number of devices per App. Once you purchase a license for the App you will be issued with a License Key. When the license key is entered additional device registrations will be allowed. Support: If you have any questions regarding the installation steps, please contact us via our website. Refer to section: Steps - Installation and Configuration

4 2. Steps - Installation and Configuration To install and configure the More4Apps Mobile Android Applications you need to complete the following steps (click on the links to go to the relevant documentation): 1. Download the Server Installation Files 2. Server Installation These steps are typically undertaken by a DBA a. Server Install - R12.1 Customers Only b. Server Install - R12.2 Customers Only c. Server Install - R11i Customers Only 3. Install the More4Apps Mobile Applications on your Mobile device 4. Configure More4Apps Mobile Applications Support: If you have any questions regarding the installation steps contact us via our website.

5 3. Download the Server Installation Files To download the server installation files please go to this URL: Refer to section: Steps - Installation and Configuration

6 4. Server Installation Follow these steps to install the communication servlet in the mid tier. This servlet is required for both Release 11i and Release 12: 1. Server Install - R12.1 Customers Only 2. Server Install - R12.2 Customers Only 3. Server Install - R11i Customers Only To enable the servlet, we modify the server configuration files by implementing a fully supported Autoconfig customization, as documented in Metalink Note Attention Windows Users: this document uses UNIX syntax when specifying directories and operating system commands. Substitute the appropriate Windows syntax where applicable. If you have multiple mid-tier servers then you must repeat these steps on each server. 4.1 Server Install - R12.1 Customers Only The following steps should be completed for R12.1 customers only. 1. Copy jar files to $JAVA_TOP Copy the jar files to the mid-tier server and place in $JAVA_TOP. cp W1Servlet.jar $JAVA_TOP cp core.jar $JAVA_TOP cp javase.jar $JAVA_TOP If you have unzipped the jar files as per our previous instructions please remove the unzipped files: rm -rf $JAVA_TOP/com/more4apps/mobile rm rf $JAVA_TOP/com/google 2. Edit Autoconfig Templates Navigate to the template directory: cd $FND_TOP/admin/template Create the "custom" directory if it does not already exist. mkdir custom If the files orion_application_xml_1013.tmp and orion_web_xml_1013.tmp do not already exist in the "custom" directory then copy them in. Be careful not to overwrite an existing copy of these files or you may lose pre-existing customizations. cp orion_web_xml_1013.tmp custom cp orion_application_xml_1013.tmp custom Move into the custom directory and edit the custom template files.

7 cd custom vi orion_web_xml_1013.tmp Paste the following lines just before the TCF alias (approximately line 170). <!-- More4Apps Mobile servlet --> <servlet> <servlet-name>w1servlet</servlet-name> <servlet-class>com.more4apps.mobile.w1servlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>w1servlet</servlet-name> <url-pattern>/w1servlet/*</url-pattern> </servlet-mapping> Save the file. Now edit orion_application_xml_1013.tmp. vi orion_application_xml_1013.tmp Paste the following lines just after <library path="%s_javatop%" /> (approximately line 62). <library path="%s_javatop%/w1servlet.jar" /> <library path= %s_javatop%/javase.jar /> <library path= %s_javatop%/core.jar /> Save the file. 3. Run Autoconfig (as described in Note ) cd $ADMIN_SCRIPTS_HOME adautocfg.sh 4. Bounce Apache adapcctl.sh stop adoacorectl.sh stop adoacorectl.sh start adapcctl.sh start 5. Test the Servlet To test whether the servlet has been installed correctly, first get the value of profile option "Apps Servlet Agent". Then enter the following URL in your browser: <<value of profile option>>/w1servlet/hello The full URL will look something like this:

8 If the servlet has been installed correctly a simple information page will render. Refer to section: Install the More4Apps Mobile Applications on your Mobile device 4.2 Server Install - R12.2 Customers Only The following steps should be completed for R12.2 customers only. 1. Ensure that a patch run is not currently taking place. adop -status 2. Copy the below jar files to the $HOME directory on the mid-tier server. W1Servlet.jar core.jar javase.jar If you have unzipped the jar files as per our previous instructions please remove the unzipped files: rm -rf $JAVA_TOP/com/more4apps/mobile rm rf $JAVA_TOP/com/google 3. Connect to Run environment.. EBSapps.env run 4. Start a patch run cycle: adop phase=prepare 5. Connect to patch environment:. EBSapps.env patch 6. Unzip the servlet into $JAVA_TOP cd $JAVA_TOP unzip $HOME/core.jar unzip $HOME/javase.jar unzip $HOME/W1Servlet.jar 7. Generate the customall.jar file (you will be prompted for the APPS password): adcgnjar Check that it has worked by doing the following, you should see the More4Apps servlet files along with any other custom java files: unzip l $JAVA_TOP/customall.jar

9 8. Add Entries to the Custom Synchronization Driver File. Add entries for the custom files to the custom synchronization driver file to ensure that the adop utility synchronizes these files between the run file system and the patch file system the next time you run the prepare phase. vi $APPL_TOP_NE/ad/custom/adop_sync.drv Add the following to this file after #Begin Customization : rsync -zr --delete %s_current_base%/ebsapps/comn/java/classes/com %s_other_base%/ebsapps/comn/java/classes cp %s_current_base%/ebsapps/comn/java/classes/customall.jar %s_other_base%/ebsapps/comn/java/classes rsync -zr --delete %s_current_base%/ebsapps/appl/fnd/12.0.0/admin/template/custom %s_other_base%/ebsapps/appl/fnd/12.0.0/admin/template 9. Edit Autoconfig Templates Navigate to the template directory: cd $FND_TOP/admin/template Create the "custom" directory if it does not already exist. mkdir custom If the file oacore_web_xml_fmw.tmp does not already exist in the "custom" directory then copy it in. Be careful not to overwrite an existing copy of this file or you may lose pre-existing customizations. cp oacore_web_xml_fmw.tmp custom If the file ebs3rdpartymanifest_xml.tmp does not already exist in the "custom" directory then copy it in. Be careful not to overwrite an existing copy of this file or you may lose pre-existing customizations. cp ebs3rdpartymanifest_xml.tmp custom Move into the custom directory. cd custom Edit the custom template files. o vi oacore_web_xml_fmw.tmp

10 Put the following lines in after the FND Servlets servlet entries (approximately line 69): <!-- More4Apps Mobile servlet --> <servlet> <servlet-name>w1servlet</servlet-name> <servlet-class>com.more4apps.mobile.w1servlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>w1servlet</servlet-name> <url-pattern>/w1servlet/*</url-pattern> </servlet-mapping> Save the file. o vi ebs3rdpartymanifest_xml.tmp Add the following section after the last </classpath> entry and just before </classpath-contents> (approximately line 142): <classpath> <absolute-path>%s_current_base%/ebsapps/10.1.2/ord/jlib</absolutepath> <relative-path>../../../../../10.1.2/ord/jlib</relative-path> <windows-path>@bea_home@/../ebsapps/10.1.2/ord/jlib</windowspath> <libraries> <library>ordhttp.jar</library> <library>ordim.jar</library> </libraries> </classpath> Save the file. 10. Enable the More4Apps Servlet. Switch back to the Run edition:. EBSapps.env run Once you are ready to move the More4Apps servlet to the Production system run the adop cutover phase. Note that this will require a brief downtime for the users. adop phase=cutover Switch to the new Run edition:. EBSapps.env run

11 Run Cleanup (optional): adop phase=cleanup 11. If you have enabled the Allowed Resources feature by setting the Profile Option Security: Allowed Resources to Configured then you must do the following: cd $FND_TOP/secure echo "servlet /OA_HTML/W1Servlet" > custom_servlets.conf echo "/OA_HTML/ServletPing" >> custom_servlets.conf java oracle.apps.fnd.security.resource.wldatamigration MODE=custom INPUT_FILE=custom_servlets.conf DBC=$FND_SECURE/$TWO_TASK.dbc 12. Test the Servlet To test whether the servlet has been installed correctly, first get the value of profile option "Apps Servlet Agent". Then enter the following URL in your browser: <<value of profile option>>/w1servlet/hello The full URL will look something like this: If the servlet has been installed correctly a simple information page will render. Update the Servlet if it has already been installed If the servlet is already installed using the above steps, then a new servlet version can be updated directly into the Run environment. It is very quick to do it this way as there is no need to cutover between the Patch and Run environments, but this can only be performed if there is no patch run currently taking place. Connect to the run environment:. EBSapps.env run Ensure there is no current run cycle taking place: adop -status If there is no patch run taking place then copy the servlet jar files to the $HOME directory on the mid-tier server and unzip it. cd $JAVA_TOP unzip $HOME/core.jar unzip $HOME/javase.jar unzip $HOME/W1Servlet.jar

12 Generate the customall.jar file (you will be prompted for the APPS password): adcgnjar Bounce the webserver: cd $ADMIN_SCRIPTS_HOME admanagedsrvctl.sh stopall oacore adapcctl.sh stop adapcctl.sh start admanagedsrvctl.sh startall oacore Refer to section: Install the More4Apps Mobile Applications on your Mobile device 4.3 Server Install - R11i Customers Only The following steps should be completed for customers on R11i only. 1. Copy jar files to $JAVA_TOP Copy the jar files to the mid-tier server and place in $JAVA_TOP. cp W1Servlet.jar $JAVA_TOP cp core.jar $JAVA_TOP cp javase.jar $JAVA_TOP If you have unzipped the jar files as per our previous instructions please remove the unzipped files: rm -rf $JAVA_TOP/com/more4apps/mobile rm rf $JAVA_TOP/com/google 2. Edit Autoconfig Templates Navigate to the template directory: cd $FND_TOP/admin/template Create the custom directory if it does not already exist. mkdir custom If the files jserv_ux_ias1022.properties and zone_ias1022.properties do not already exist in the custom directory then copy them in. Be careful not to overwrite an existing copy of these files or you may lose pre-existing customizations. cp jserv_ux_ias1022.properties custom cp zone_ias1022.properties custom Move into the custom directory and edit the custom template files. cd custom vi jserv_ux_ias1022.properties

13 Paste the following lines just after wrapper.classpath=%s_javatop% classpath entry (approximately line 211). #--- More4Apps --- wrapper.classpath=%s_javatop%/w1servlet.jar wrapper.classpath=%s_javatop%/core.jar wrapper.classpath=%s_javatop%/javase.jar # Save the file. Now edit zone_ias1022.properties vi zone_ias1022.properties Paste the following lines at the very end of the file, after Oracle Web Agent. # More4Apps Mobile Servlet servlet.w1servlet.code=com.more4apps.mobile.w1servlet # Save the file. 4. Run Autoconfig (as described in Note ) cd $APPLCSF/scripts/$CONTEXT_NAME adautocfg.sh 5. Bounce Apache cd $APPLCSF/scripts/$CONTEXT_NAME adapcctl.sh stop adapcctl.sh start 6. Test the Servlet To test whether the servlet has been installed correctly, first get the value of profile option "Apps Servlet Agent". Then enter the following URL in your browser: <<value of profile option>>/w1servlet/hello The full URL will look something like this: If the servlet has been installed correctly a simple information page will render. Refer to section: Install the More4Apps Mobile Applications on your Mobile device

14 5. Install the More4Apps Mobile Applications on your Mobile device Once the server-side installation is complete you need to install the More4Apps Mobile Applications on your mobile device from the Google Play Store for Android or the itunes store for Apple. More4Apps Mobile Product App Installation You can now install the desired product applications. Currently we have three Applications available: More4Apps Mobile Receiving More4Apps Mobile Inventory More4Apps Mobile Work In Process Search for "More4Apps Mobile" or "Oracle ebusiness" in Google Play to find these Apps.

15 6. Configure More4Apps Mobile Applications Once the installation has been completed you need to configure the More4Apps Mobile Application. Please Note: The servlet must have been installed and tested as per the previous section or an error will occur when attempting to connect. 1. Connecting to an E-Business Instance Select one of your More4Apps Mobile applications. You will be presented with a screen for Oracle E-Business connections. Click on the Add Connection button. You will see the connection registration screen. At this point you will need the value of the Apps Servlet Agent profile option from the instance. To get this value login in to Oracle e-business Suite as a System Administrator and find the Apps Servlet Agent profile option at the site level. To enter the required value, you can either type it manually (not straightforward on an Android device) or use your built-in barcode scanner. a) Scanner Method Enter the following URL on your normal computer (not your Android device): <<Apps Servlet Agent>>/W1Servlet?p_action=qr For example: This will display a QR barcode on your screen. You can now long-hold in the servlet URL field on your Android device, which will start the bar code reader. Scan the barcode on your computer and the URL will be scanned to your device. b) Manual Method Enter the URL exactly as show in the Profile Option into the servlet URL field. Once the URL has been entered, press the Register button on your Android device.

16 If the registration is successful then you will see the Instance name in the list of Connections. You can click on the Instance name to proceed. 2. Logging In and Security Click on the Login button to connect to your E-Business instance. You should see your usual E- Business login page appear on the device. Log in using your Oracle username and password. You will be prompted whether you want to remember this username and password. It is a good idea to do this as it makes it easy to log in next time. To clear out the remembered details, click on the Refresh button in the ActionBar at the top of the page. You will be next be prompted for your Responsibility then your Inventory Org. Once these are chosen you will be able to proceed with the More4Apps Mobile App functionality. The next time you log in to this App it will also remember and default your previously chosen Responsibility and Inventory Org. If you want to switch to a different one then press the menu button from the App home screen. 3. Logging Out Click on the back button on your device until the More4Apps Mobile Launcher is shown. (We are working on a better approach to logging out and will issue new App versions shortly to address this).