| Oracle® Retail POS Suite Implementation Guide, Volume 5 – Mobile Point-of-Service Release 14.1 E54478-01 |
|
 Previous |
 Next |
| Oracle® Retail POS Suite Implementation Guide, Volume 5 – Mobile Point-of-Service Release 14.1 E54478-01 |
|
Previous |
Next |
This chapter describes how to set up a single-user development environment for Oracle Retail Mobile Point-of-Service extension and customization. The setup enumerates the files, tools, and resources necessary to build and deploy the Mobile POS server application. When you complete the steps in this chapter, you will have a local development workspace with the ability to build and deploy the Mobile POS application.
This chapter assumes that you are using WebLogic Application Server and the Oracle database; together, they form the officially supported platform for the current release of the Mobile POS server. Your development environment may use different tools, and you may develop variations on this procedure. Specific property file settings, in particular, may need to be modified in your environment. For more information about product versions, see the Oracle Retail Point-of-Service Installation Guide, Volume 1 - Oracle Stack.
The Mobile POS server application uses the Eclipse platform for development. These instructions and screenshots use Eclipse Indigo Java EE IDE. The Eclipse screenshots are shown in Appendix C.
To create the Eclipse project:
Copy the mobilepos.war file to a temporary location, that is, do not use the deployed war file.
Create a new workspace or update an existing workspace.
Go to the Workspace Preferences to ensure you have the WebLogic Runtime. See Figure C-2.
This release of Mobile Point-of-Service was developed using Oracle WebLogic 10.3.6. Verify you have the correct WebLogic release. See Figure C-3.
Import the war file into Eclipse by selecting File and then Import. See Figure C-4.
Select WAR file under the Web folder. See Figure C-5.
Browse to the temporary location and select the WAR. See Figure C-6.
Set the target runtime as appropriate and select Next.
Select the oracle.stores.mobilepos-config.jar as a Web Library to allow for updates to the various Mobile POS configuration files. Additionally, select any language bundle JARs that may need updating. See Figure C-7.
Select Finish. Eclipse generates the projects. For an example, see Figure C-8.
Update the mobilepos project to include the Jersey library dependencies by selecting the project properties, Java Build Path, and then Add Library. See Figure C-9.
Select Next.
Select Browse and then select jsr311.api. See Figure C-10.
Select OK. The project is ready to use.
There are no build scripts provided for Mobile Point-of-Service. Extension projects should use the Eclipse tools to build and deploy the application WAR to the WebLogic server. If command-line build processes are required, use Eclipse's Ant build file export capabilities to generate the necessary Ant scripts.
Once you have set up your Eclipse workspace, you should see a project that looks something like Figure 6-1:
The mobilepos project is where you develop your customizations, and the oracle.stores.mobilepos-config project contains all of the configuration files you generally find with the POS client.
When developing extensions to Mobile POS Server, keep in mind that the JARs delivered with the Mobile Point-of-Service add-on are different from those delivered with POS Suite release 13.4.1. There have been updates made to the POS application, foundation, and domain that the Mobile POS Server relies on. You cannot use base 13.4.1 POS JARs in place of those delivered with the Mobile POS Server. To take advantage of any customizations you have made to the base POS application, you need to provide those customizations in separate JARs and treat them as third-party libraries to the Mobile POS Server.
