Xstore POS and Xstore Office - Build Server Setup

Oracle® Retail Xstore POS
and Xstore Office

Build Server Setup
January 2018
Note: The following is intended to outline our general
product direction. It is intended for information purposes
only, and may not be incorporated into any contract. It is not
a commitment to deliver any material, code, or functionality,
and should not be relied upon in making purchasing
decisions. The development, release, and timing of any
features or functionality described for Oracle’s products
remains at the sole discretion of Oracle.
Contents
Preface ............................................................................................................................... 1
Acknowledgements ................................................................................................................ 1
Intended Audience ................................................................................................................. 1
Scope ......................................................................................................................................... 1
Conventions ............................................................................................................................. 1
Overview ............................................................................................................................ 2
Build Processes Overview...................................................................................................... 2
Lifecycle ............................................................................................................................ 2
Continuous Integration ................................................................................................... 2
Builds ................................................................................................................................. 3
Application Installation .................................................................................................. 4
Automated Testing .......................................................................................................... 4
1
Component Installation .................................................................................................... 6
Prerequisites ............................................................................................................................ 6
Required 3rd Party Components ............................................................................................ 6
Configuration of Components .............................................................................................. 6
Required Xstore Components ............................................................................................... 6
Components Installation ........................................................................................................ 7
Java JDK - Install and Configure.................................................................................... 7
ANT - Install and Configure......................................................................................... 13
OpenSSL - Install and Configure ................................................................................. 15
Apache HTTP Server - Install and Configure ............................................................ 15
Hudson - Install and Configure ................................................................................... 16
Subversion – Install and Configure ............................................................................. 27
Connecting Subversion with Hudson ......................................................................... 33
2
Component Configuration ............................................................................................. 35
SVN Repository Project Setup ............................................................................................. 35
Hudson Build Job Setup ....................................................................................................... 36
Create a New Build Job ................................................................................................. 36
Run the new Build Job, Build Now ............................................................................. 37
4
Developer Setup .............................................................................................................. 39
Eclipse IDE Setup .................................................................................................................. 39
5
Security and Maintenance .............................................................................................. 40
Network Access and Securing Build Systems ................................................................... 40
System Maintenance and Backup Procedures .................................................................. 40
References ....................................................................................................................... 41
Books and Articles ................................................................................................................ 41
Websites ................................................................................................................................. 41
Trademarks ............................................................................................................................ 41
iii
Preface
Acknowledgements
Portions of this document are a compilation of information originally produced for
training and reference for the purpose of supporting the Oracle Retail Xstore Point of
Service (POS) and Oracle Retail Xstore Office application build processes.
Intended Audience
This document is intended for the technical staff responsible for setting up and
maintaining build processes for “System Integrators” software implementations. Users
should have a working knowledge of the Xstore POS and Xstore Office applications and
source code.
Note: Retailers who wish to make changes to the product,

which require the source code, should contact their Oracle
representative. All source code distribution requests must be
approved, following Oracle’s standard Source Code
distribution policy.
Scope
The Scope of this document is to describe and support the build processes necessary to
compile the Oracle Retail Xstore POS and Oracle Retail Xstore Office applications. This
document does not cover the prerequisite software modifications required to meet
implementation needs and does not cover the installation of the resulting software
application artifacts. Additional training and documentation may be required to support
those activities outside the scope of this document.
Conventions
This document will cover the installation and configuration of the Xstore suite build
processes and related systems. All examples and details provided will reference a
Microsoft Windows Platform which you may translate to a Linux platform as needed.
Preface 1
Build Processes Overview
Overview
The Oracle Retail Xstore POS and Oracle Retail Xstore Office suite of products are
compiled as part of an interrelated process supported by a variety of software
applications and utilities.

Lifecycle
Change
Notifica 2
tion
Check in
Check
out
3
n
1 ck i Version Control System
Developers Che
(SVN)
Build Servers
(Hudson)
Publi
Developers 4
sh to
A Q
us
at
St
CI
5
CI Status
Notifications
Published Builds
CI Feedback
Notifications
Team Leads, testers,
clients, management,
developers, etc.
For example, Developers and Implementation Consultants make their changes to source
code and configurations and commit that work to a particular SVN repository. Then a
build is executed using one of several methods; on-demand, daily, or a continuous
integration pattern. Regardless of the method, this process produces a resulting set of
build artifacts for the application that can be used to install or update the software in
quality assurance (QA) and/or in production in the field.
Continuous Integration
Martin Fowler and Kent Beck are largely credited with the first use of the term
"Continuous Integration" as applied to software development with Beck’s seminal 1999
book Extreme Programming Explained
Beck, Kent (1999). Extreme Programming Explained. ISBN 0-201-61641-6.
The idea, put simply, is that software development efforts are much easier to manage
when test failures and other bugs can be identified closer to the time they were
introduced into a complex system.
2 Oracle Retail Xstore POS and Xstore Office

Builds
Types of Builds
On-Demand builds may be run on-demand
directly from the Hudson build server
webpage.
Daily builds may be scheduled to run daily at
regular times each day, or to react to commits
to the SVN server.
Continuous Integration (CI) builds are run
multiple times in a given day to ensure a
successful result at the end of the day.
A basic CI build cycle might start with an afternoon “trial” build to validate the state of
the applications in the build. An email can be sent automatically by the build server
(Hudson) to the development team (including developers, Implementation Consultants,
team leads and managers) announcing the state of the current codebase. A subsequent
build would run later (for example, at midnight) as a QA delivery candidate build. In the
event that the afternoon build fails, it provides the team with the opportunity to fix the
build before the more significant nightly build runs.
Build Tools
Apache ANT is a Java library and command-line toolset used for the purpose of
automating the application build process. The use of Build files, Targets and extensions
facilitates the compilation and organization of the build artifacts. ANT is essentially
MAKE for Java.
SVN Subversion is a revision control system for use by Developers and Implementation
Consultants. The SVN SCM tool, released as free software under the Apache License,
controls the source code change management process. SVN is also integrated with the
Eclipse IDE that is referenced in this document.
Since SVN is a free and open platform, a vast amount of information is available online
regarding the setup and use of this tool.
For more details on SVN visit the Apache Subversion website
(https://subversion.apache.org/).
Hudson is a powerful and widely used open source Continuous Integration server (CI)
used for software application development. Hudson supports the SVN SCM tool and it
provides development teams with a reliable way to monitor changes in source control
and trigger a variety of builds.
For more details on Hudson configuration and job setup please refer to the document
HudsonIntro (http://hudson-ci.org/docs/HudsonIntro.pdf).
You may also read the Hudson Book here (http://wiki.eclipse.org/The_Hudson_Book).
Overview 3
Application Installation
InstallX is used to build and install builds of the Xstore POS application and some
associated server-based components. This installation application is used to package,
install and configure the Xstore POS application, associated server-based components,
and utilities. InstallX is customer, operating system, and database platform independent;
however the artifacts are specifically targeted.
Each InstallX Installer is packaged as an executable jar file and can be run from the
command line. It may optionally be run with a GUI Wizard to prompt the user for
installation parameters.
The distribution file name will indicate the version, customer, component, and
installation type contained in the installer.
Automated Testing
Xunit is an automated testing engine used to
perform end user testing of the Xstore
application without requiring user interaction.
Test scripts contained in XML configuration
files are loaded into the test harness, which
then pushes “events” to Xstore, simulating
user input. Test results are determined by the
validity of test events based on the current
system state and data assertions evaluated
against the Xstore database, memory, and file
system.
Note: It is not permitted to enable Xunit on production

systems.
Benefits of Automated Testing

 Efficiency – Xunit can execute in a matter of seconds a regression suite that would
take hours to key in manually. QA analysts spend more time analyzing results and
less time typing in data.
 Accuracy – Actions and data assertions performed by an automation engine reduce
the possibility of human error when testing the application.
 Consistency – Automated suites help ensure that identical test scenarios are
executed from one release to the next, regardless of the QA analyst testing the
system. Automation can assist in reproducing issues between separate lab
environments.
Xunit Advantages
Since Xunit is integrated with the Xstore application, it holds several advantages over
traditional, third-party automation packages:
 Lightweight – Xunit requires minimal runtime overhead or system resources.
 Stable and fast – Test events are fired the instant the application is ready for input;
running on the main application thread mitigates the risk of Xunit falling out sync
with Xstore during execution.
 Internationalized – Test scripts process consistently regardless of the display
language of the application.
 Data validation – Xunit provides the lowest possible level of data validation because
it has direct access to Xstore’s memory, database, and file system.

 Script maintenance – Test cases are factored into libraries of reusable components.
When a change is made to the application, a single corresponding change to the test
script library can accommodate all test cases relevant to the Xstore functional area.
 Cost – Xunit is currently provided as part of the core Xstore deliverable; no
additional product or license needs to be purchased.
Overview 5
Prerequisites
1
Component Installation
Prerequisites
This document will reference and assume that you are using either the documented or
latest versions of the 3rd Party Tools and Xstore components listed below.
Required 3rd Party Components

These 3rd Party components will be required for the successful setup and configuration of
your build server and are not provided.
1. Java
a. JDK (versioned based on Xstore release)
b. JCEPolicy files
2. ApacheANT 1.9.4 or higher
3. Apache
a. HTTP Server
b. Visual C++ redistributable components for our Apache install -
Vcredist_x86 (2013 sp1)
4. Hudson (CI) Build Software
5. Subversion (SVN) 1.8.11 or higher
Configuration of Components
1. SVN
2. Hudson
3. Eclipse 4.4.2 or latest for development purposes
Required Xstore Components

Some components will not be required based on specific implementation details. For
example either Jetty or Tomcat is required but not both.
1. Base Xstore (POS and Office)
2. Apache Installer
3. Genkeys
4. Jetty Installer
5. Tomcat Installer
6. dtv-xunit JAR file (optional)
7. JRE Packager
8. InstallX

Components Installation
The installation order of the following components is important because some
installations are dependent on others. In addition, some configurations will require that
other components exists.
Java JDK - Install and Configure

How to get the JDK
Download the JDK; the version is dependent on the
Xstore release. Check the Xstore release
documentation for the proper Java version.
How to Install the JDK

1. Follow the necessary steps to perform a normal install of the JDK:
a. Run the Java JDK platform-specific installer.
b. If you get a security prompt, click the Run Button
Component Installation 7
c. When prompted to begin the install wizard. Click the Next Button.
d. For a standard install accept the default options (you may wish to make
adjustments). Click the Next Button.

e. Accept the default when prompted for the installation location (you may
change this). Click the Next button.
f. When you get the message stating that you have successfully Installed the
Java SDK, click the Close Button.
Note: If you do not receive the final message indicating a

successful install, either start over and try again or contact
your Oracle Support.
2. Setup the JAVA_HOME entry in the Windows OS System Properties at the system
level:
a. Add JAVA_HOME/bin to the system path.

b. From the Windows System Properties configuration screen, click the
Environment Variables button.
c. Look for the JAVA_HOME variable:

i. If it does not exist under System Variables, add it by clicking the
New… button.
ii. If it does exist, ensure that it points to the proper folder for your Java
JDK. You may edit and change this value by Clicking the Edit…
Button.

How to Install the JCE Policy Files

1. Download and Install appropriate JCE policy files for your newly installed Java JDK:
a. Download the “Java Cryptography Extension (JCE) Unlimited Strength
Jurisdiction Policy Files.” Remember that these are JDK- version- specific
files and must match the major release version.
b. Uncompress and extract the downloaded file.

This will create a subdirectory called jce.
This directory contains the following files:
README.txt
local_policy.jar Unlimited strength local policy file
US_export_policy.jar Unlimited strength US export policy file
c. Install the unlimited strength policy JAR files.

In case you later decide to revert to the original "strong" but limited
policy versions, first make a copy of the original JCE policy files
(US_export_policy.jar and local_policy.jar). Then replace the strong
policy files with the unlimited strength versions extracted in the

previous step.
The standard place for JCE jurisdiction policy JAR files is:
<java-home>/lib/security [Unix]
<java-home>\lib\security [Windows]
d. For more information view the README.txt file provided with the JCE
download.

ANT - Install and Configure

How to get Apache ANT
Download the ANT Install from the Apache ANT Website (http://ant.apache.org/)
How to Install Apache ANT

1. Install Apache ANT on your server computer. For additional details on downloading
and installing ANT, please refer to the Apache ANT Documentation
(http://ant.apache.org/manual/index.html).
2. From the folder location where you downloaded the Apache ANT install software,
unzip the apache-ant-1.X.X-bin.zip file to your C-Drive (for example, C:\). You can
open a zip file directory from Windows File Explorer or use a utility like WinZip or
7-Zip.
3. Next you must add the ANT_HOME (Apache ANT folder reference) that was
created above to your Windows System Path.
a. Set up an ANT_HOME reference in the Windows OS System Properties at
the system level:
i. Add ANT_HOME/bin to the system path.
ii. From the Windows System Properties configuration screen. Click the
Environment Variables button.
iii. The ANT_HOME variable:

1. If it does not exist under System Variables, add it by
Clicking the New… button
2. If it does exist, then ensure that it points to the proper folder
for your Apache ANT install. You may edit and change this
value by Clicking the Edit… Button
4. You may now test your ANT install by executing the command ant –help from a
Command prompt. A detailed command explaination should be displayed as
pictured below if your installation was successful.

OpenSSL - Install and Configure

How to get OpenSSL
Download OpenSSL from the OpenSSL website (https://www.openssl.org/ or directly
from http://indy.fulgan.com/SSL/)
How to Install OpenSSL

Install OpenSSL, follow the documentation provided for installing OpenSSL based on
your specific downloaded version.
Apache HTTP Server - Install and Configure

How to get Apache HTTP Server
Use the Apache HTTP Server installer bundled with the Oracle Retail Xstore Office
download from the Oracle OSDC website.
How to Install the Apache HTTP Server

Follow the instructions in the Xstore Implementation Guide for how to install the Apache
server, including the public/private keys and certificates.
Hudson - Install and Configure

How to get Hudson
Download the latest Hudson WAR file for installation. Hudson can be downloaded
from either eclipse.org (http://www.eclipse.org/hudson/download.php) or
hudson-ci.org (http://hudson-ci.org/). More information about the available
distributions can be found here (http://wiki.eclipse.org/Hudson-
ci/development/releaseartifacts). Additional information on installing Hudson may
be found here (http://wiki.eclipse.org/Hudson-ci/Installing_Hudson).

How to Install the Hudson CI Build Server

1. Move the Hudson WAR file to the desired, final HUDSON folder (for example,
C:\hudson).
2. From a Command Prompt, execute the command java –jar hudson-3.X.X.war

to begin the installation process.
You should see the following screen when it is finished.
3. Perform the following configuration steps from your web browser. Navigate to
http://localhost:8080 to access the Hudson setup console.
4. Add the Hudson subversion plugin from the first page of the setup screen. Check the
box next to the “Hudson Subversion Plug-in” option.

5. Scroll to the bottom of the webpage and click the Install button to continue.
6. Click Finish on the Install page.
7. Please wait on screen while Hudson expands to the above folder.
This is the screen you should see when Hudson has completed this process

8. This is now a basic Hudson install that will require additional setup. Start by
selecting the Manage Hudson menu option on the left side of the screen (for
example, http://Localhost:8080/manage)
a. Configure Security:
i. Enable Security
ii. Use Hudson’s own database (by default unless otherwise desired).
iii. Optional authorization if desired. Matrix-based in most secure; it

provides a matrix to select security options
1. Anonymous is available by default, with no privileges. It is
the recommended option for the highest security
2. After selecting an authorization option, Click Save.
iv. Save changes by clicking Save.
v. At the login screen:

1. Create/Sign up a new user (desired name for example,
‘HUDSON’). This user will be an admin by default.
2. Click Sign up button to Continue.

3. Add all privileges to the HUDSON user e.g. make this user
an Administrator
4. On Security Realm, you may wish to disable the options to

allow users to be created on the login screen. This is not
required.
b. Click Configure System.
i. Many optional parameters exist here that you may change as

necessary.
Note: The number of executors is based on the hardware; the

default of 2 will likely be low.
ii. Mandatory setup

1. Setup JDK (JDK Section), which does not acknowledge the
JAVA_HOME system settings.
2. Point to your existing JAVA installation. Otherwise, Hudson

will direct you to install another, which is unnecessary.
a. Deselect the Install automatically option
b. Enter the path to your JAVA_HOME in the input
field.
3. Install ANT (selected by default)
4. Click the Add Ant Button.

a. Provide the Name. For example, “ANT 1.9.4”.

Hudson will install ANT from the Internet. This gets
installed on demand, so you will not be prompted
for information at this point.
iii. Click the Save Button at the bottom of the Settings web page
c. Click Install as a Windows Service from the Manage Hudson web page.
i. Enter the Installation Directory for HUDSON; a folder named

hudson is recommended.
This is where the Hudson WAR file will be extracted, and it
becomes the permanently installed location for Hudson.
Click the Install button to continue; this may take a minute to

complete.
ii. Click Yes to stop HUDSON and start as a service.
d. Set up HUDSON to run with SSL using the Java Keytool:

i. Generate a .keystore file for Hudson to use.
Example:
keytool –genkey –keyalg RSA – keystore
Hudson.keystore –alias Hudson –validity 3950
Note: See the Xstore implementation guide for additional

information.
ii. Place the .keystore file in the Hudson folder created in step 8.c.i.
e. Edit the Hudson.xml file to tell Hudson to use the new key:
i. Edit the arguments tags to set the following;
–httpskeystore=c:/Hudson/Hudson.keystore
–httpskeystorepassowrd=allgoodthings
(must match password entered earlier)
ii. Edit the arguments tags to set the following;

--httpport =-1
–httpsport=8443
Please refer to the Hudson article for more information on these

details.
1. Starting and Accessing Hudson on the Hudson Wiki
( http://wiki.eclipse.org/Hudson-ci)
2. Cheat sheet at the bottom has exact section changes
referenced above.
f. Restart the Hudson service.

Subversion – Install and Configure

How to get Subversion
Download the Subversion installer from the
Apache Subversion Website (https://subversion.apache.org/packages.html or directly
from the Win32SVN website http://sourceforge.net/projects/win32svn/).
You will have options to choose from, although we do not specifically recommend one
over another, you will need to select one that offers the server component such as
Win32SVN or VisualSVN. The Win32SVN server uses the Apache http server on either
Linux or Windows and for example the VisualSVN server does not require Apache and is
available for the Windows platform only.
How to Install Subversion

1. Run Subversion installer.
2. If you get a security prompt, click on the Run button.
3. When prompted to begin the install, click the Next button.
4. When prompted for information, review the information and click the Next button.

5. When prompted to choose an Apache version, xelect Modules for Apache 2.4.x and
click the Next button.
6. When prompted for the Destination Folder, click the Next button.
7. When prompted Ready To Install Subversion, click the Install button.
8. When the installation is complete, Click the Finish button.

How to Setup a Subversion Repository

1. Setup Subversion server:
a. Using the command C:\>svnadmin create svnrepo {is your repository name}
A folder with the name of the repository provided will be created
b. Change directories to your new repository folder for example:

cd xyzxstorerepo

Connecting Subversion with Hudson

This will allow the Hudson build server to access your source code repositories in
Subversion. This is mandatory and is how the build artifacts are produced by Hudson.
1. Copy the following files from C:\Program Files…\subversion\bin\ to the
Apache modules directory C:\Program Files…\apaches…\modules
Mod_authz_svn.so
Mod_dav_svn.so
2. Configure changes to your Apache instance:

a. Navigate to the folder where Apache was installed on your machine.
For example, C:\program files(x86)\apache-{version}\conf
b. Edit Httpd.conf to add the Subversion reference to the end of the
loadmodules section at the top:
i. Add LoadModule lines for:
LoadModule authz_svn_modules/mod_authz_svn.so
LoadModule dav_svn modules/mod_dav_svn.so
ii. At the end of the file add an extra location for the subversion
repository location, more can be added if needed. Be sure that your
SVNPath matches what you selected for your actual repository
location above.
<Location /svn>
DAV svn
SVNPath C:/svnrepo
AuthType Basic
AuthName “Subversion Repository”
AuthUserFile “htdocs/.htpasswd”
AuthzSVNAccessFile C:/svnrepo/conf/svn-acl-conf
Require valid-user
</Location>
Note: On Windows 8.1 systems, the case is important on

lines containing “C:/” (that is, lines containing file or
directory locations).
3. Create subversion users:

For example, create the following users from the command-line svnuser and
svnadmin:
a. htpasswd ..\htdocs\.htpasswd svnuser
{Enter/Create a Password}
b. htpasswd ..\htdocs\.htpasswd svnadmin
{Enter/Create a Password}
4. Create an SVN ACL file for the users created above.
a. Go to the c:\svnrepo\conf folder.
b. Create the “svn-acl-conf” file and add/edit the following lines:
[groups]
dev = svnuser
admin – svnadmin
#repo root
[/]
* = #e.g. everyone by default has no access
@dev = r #read access
@dev = rw #read/write access
#overlay is a subdirectory of the repo we created

[/overlay]
@dev=rw #dev gets read/write in the overlay
5. Stop/restart Apache service:

a. Navigate web browser to https://localhost.
b. After properly logging in you will see the “IT Works” page displayed.
6. Navigate to the SVN repository:
a. Navigate web browser to https://localhost/svn/.
b. Login with Admin user.
c. Successful Result “svn – Revision 0:/” page.

SVN Repository Project Setup
2
Component Configuration
SVN Repository Project Setup
Load the necessary source code files to the repository that you setup during the SVN
install.
Using the provided files from Oracle Retail for POS, Mobile and Office:
1. The BASE FOLDER contains an export of the Base projects in the
Base\tags\{version} \
2. C:\{BASE FOLDER}>svn import . https://localhost/svn --message “Initial
Import”
a. Result will be something like “error validating server certificate…”
b. (R)eject, accept (t)emporarily or accept (p)ermenently
c. Select P for permanent
d. Username svnadmin
e. Enter password
f. This step will take several minutes since it is importing (“Adding”) many
files
3. Check SVN repo
a. https://localhost/svn
b. Check for REPO
Component Configuration 35
Hudson Build Job Setup

Log into Hudson with user-created user ID and password (https://localhost:8443/).
Ensure that the SVN plugin was installed.
Note: This may not happen properly if the installation did

not exactly follow this document.
Create a New Build Job

1. From the Hudson Main Menu
Create a new job Click on the
New Job link…
2. You will have many
configuration options
available; we will only cover
the basic of the required
pieces here.
3. Name the Job.
This is typically for client and
version of software.
For example: XYZ-Xtore-7.1.
4. The source code is in SVN

a. URL https://{servername:port}/svn/overlay/tags/7.1
b. You will be prompted for uid/pwd credentials
c. Check out strategy
d. Select; emulate clean checkout…
5. ANT
a. The job needs to reference the proper ANT install by name
b. In the ANT section the combo box should list your ANT install, select it
6. Build
a. Target; distribution
b. Build File; projects/Jenkins-build.xml
7. Post-build actions
a. Check; archive the artifacts

b. Files to archive; distro-full/**

8. SAVE
Run the new Build Job, Build Now

Build jobs may be run multiple ways: scheduled, reactive to source code management
activity (such as commits), or manually launched. We will cover the manual process here.
All access to be able to schedule, run and manage jobs in Hudson is based on the user’s
login credentials.
Alternatively, if you click on the Job Name (for example, myClient-Xstore-7.1.-1.0.0) you
have the Build Now link to run a job also. Both options queue the job to be run when
resources become available on the server, this is based on other jobs that may be queued.
This build will fail on the first run, because the artifacts must be created and configured.
It may also fail on the ANT install. The normal Build Failure message statement explains
that it cannot find the directory c:\hudson\releases\X.X.X.X (where X.X.X.X is your
specific version of Hudson).
1. Create the missing folder from the Build Failure message.
For example, c:\hudson\releases\X.X.X.X where X.X.X.X is your specific version
of Hudson.
2. Move the provided archive files to the c:\hudson\release\X.X.X.X folder.
Note: See the Oracle® Retail Xstore Point of Service and

Xstore Office Development Environment Setup white
paper for the procedure for moving and extracting archive
files.
Component Configuration 37
3. Run the build process again.

4. Check the build results.
The resulting .zip file is what is delivered to the customer. No initial data is
provided. You will need to add the setup data before the build so that it gets
included with the delivery.
The build is now complete.

Eclipse IDE Setup
4
Developer Setup
Eclipse IDE Setup
The development process is managed locally using the Eclipse IDE. This IDE has support
for Java software development with integrated run and debugging capabilities. Eclipse
also supports specific editors for various file types, such as XML documents and Java
files. It provides integration with SVN and ANT. Additionally, many plugins exist for the
Eclipse IDE. Although other IDE’s may be used, Xstore development is standardized on
the Eclipse platform.
Note: See the Oracle® Retail Xstore Point of Service and

Xstore Office Development Environment Setup white
paper for the procedure for setting up the Eclipse IDE.
For more information on the Eclipse IDE visit the Eclipse Website (https://eclipse.org/).
Developer Setup 39
Network Access and Securing Build Systems
5
Security and Maintenance
Your organization should establish and maintain good security and maintenance
procedures for these mission critical systems.
Network Access and Securing Build Systems

Good policies and practices should be put into place to restrict the availability and access
to your source control and build servers. Only the people that have a business need for
access should be granted privileges to these systems.
System Maintenance and Backup Procedures

The use of good standards for system maintenance and backup process should be put in
place to protect client source code and build artifacts.
Important data stored on the source and build servers may be copied and archived
securely as a precautionary measure where, in the event of failure, the data and systems
may be reconstructed. When major maintenance such as software updates and patches
are applied, a backup is recommended as the first step in case the update fails and you
need to revert to the backup.

Books and Articles
References
Books and Articles
Beck, Kent. Extreme Programming Explained: Embrace Change. Boston: Addison-
Wesley, 2000.
Xstore Implementation Guide: A guide outlining Xstore product architecture and
instructions necessary to install or upgrade Xstore components: Xstore Release 7.1:
Copyright © 2015 Oracle, Inc.
Xstore Technical Guide Release 7.1, Doc Ver 06: Copyright © 2015 Oracle, Inc.
Xunit Customer Training: Document Version 2.0: Copyright © 2015 Oracle, Inc.
Websites
apache.org
ant.apache.org
subversion.apache.org
tomcat.apache.org
eclipse.org
eclipse.org/Hudson
www.micros-retail.com/category/Products/POS-
Software/Xstore/pc/833/sc/851/860.uts
www.oracle.com
Trademarks
"Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners."
Apache ANT, Apache Subversion SVN, Eclipse, Tomcat, Jetty and the logos are all Registered
Trademarks of their respective organizations.
Apache®, Apache Hadoop, Hadoop®, and the yellow elephant logo are either registered
trademarks or trademarks of the Apache Software Foundation in the United States and/or other
countries.
"‘Eclipse’, ‘Built on Eclipse’ and ‘Eclipse Ready’, ‘BIRT’, ‘Higgins’ are trademarks of Eclipse
Foundation, Inc."
Microsoft Visual C++is either registered trademarks or trademarks of Microsoft Corporation in
the United States and/or other countries.
References 41
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
oracle.com
Copyright © 2018, Oracle. All rights reserved.

All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to
be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by
this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written
permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of
SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group.

Xstore POS and Xstore Office - Build Server Setup

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Xstore POS and Xstore Office - Build Server Setup

Hochgeladen von

Copyright:

Verfügbare Formate

Oracle® Retail Xstore POS

and Xstore Office

Note: Retailers who wish to make changes to the product,

Build Processes Overview

Beck, Kent (1999). Extreme Programming Explained. ISBN 0-201-61641-6.

2 Oracle Retail Xstore POS and Xstore Office

Note: It is not permitted to enable Xunit on production

Benefits of Automated Testing

4 Oracle Retail Xstore POS and Xstore Office

Required 3rd Party Components

Required Xstore Components

6 Oracle Retail Xstore POS and Xstore Office

Java JDK - Install and Configure

How to Install the JDK

b. If you get a security prompt, click the Run Button

8 Oracle Retail Xstore POS and Xstore Office

Note: If you do not receive the final message indicating a

a. Add JAVA_HOME/bin to the system path.

c. Look for the JAVA_HOME variable:

10 Oracle Retail Xstore POS and Xstore Office

How to Install the JCE Policy Files

b. Uncompress and extract the downloaded file.

c. Install the unlimited strength policy JAR files.

policy files with the unlimited strength versions extracted in the

12 Oracle Retail Xstore POS and Xstore Office

ANT - Install and Configure

How to Install Apache ANT

iii. The ANT_HOME variable:

14 Oracle Retail Xstore POS and Xstore Office

OpenSSL - Install and Configure

How to Install OpenSSL

Apache HTTP Server - Install and Configure

How to Install the Apache HTTP Server

Hudson - Install and Configure

16 Oracle Retail Xstore POS and Xstore Office

How to Install the Hudson CI Build Server

2. From a Command Prompt, execute the command java –jar hudson-3.X.X.war

You should see the following screen when it is finished.

18 Oracle Retail Xstore POS and Xstore Office

6. Click Finish on the Install page.

7. Please wait on screen while Hudson expands to the above folder.

20 Oracle Retail Xstore POS and Xstore Office

iii. Optional authorization if desired. Matrix-based in most secure; it

iv. Save changes by clicking Save.

v. At the login screen:

2. Click Sign up button to Continue.

22 Oracle Retail Xstore POS and Xstore Office

4. On Security Realm, you may wish to disable the options to

b. Click Configure System.

i. Many optional parameters exist here that you may change as

Note: The number of executors is based on the hardware; the

ii. Mandatory setup

2. Point to your existing JAVA installation. Otherwise, Hudson

3. Install ANT (selected by default)

4. Click the Add Ant Button.

24 Oracle Retail Xstore POS and Xstore Office

a. Provide the Name. For example, “ANT 1.9.4”.

i. Enter the Installation Directory for HUDSON; a folder named

Click the Install button to continue; this may take a minute to

d. Set up HUDSON to run with SSL using the Java Keytool:

Note: See the Xstore implementation guide for additional

ii. Edit the arguments tags to set the following;

Please refer to the Hudson article for more information on these

26 Oracle Retail Xstore POS and Xstore Office