The preceding steps described how to configure the server side Store.Mobile.DCS-CSR module of Assisted Selling. It is important that Assisted Selling’s iOS client is configured and built through Xcode so that the configuration matches the server side setup.

To get started, open the AgentWorkspace Xcode Workspace located in the directory where you unzipped the files, at:

<home>/OCAssistedSellingiOS/AgentWorkspace.xcworkspace
Configuration

To get Assisted Selling up and running in your environment, configure the following Agent-Info.plist entries:

Additionally, for a release build intended for production ATG_USE_HTTPS should be set to “YES” in order to enable SSL. This is strongly recommended and requires additional supporting configuration within your infrastructure to fully enable SSL.

Use this method of configuration when distributing an app, since the values of the Agent-Info.plist are used by default until they are manually overridden in the settings bundle.

If you install the optional ORMPOS Integration plugin

The file POSPlugin.plist, which is referred to in the Agent-Info.plist file has entries for:

Settings Bundle

The iOS client includes a settings bundle located at <home>/OCAssistedSellingiOS/Agent/Agent/Settings.bundle, where <home> is the directory where you extracted the distribution. This bundle manages server settings, such as ports, host, and Site ID, from the Settings app. This bundle is included in Assisted Selling for demonstration purposes. Once Assisted Selling is installed on the iOS device, touch Assisted Selling in Settings and configure the Host and Port server settings to point to your dedicated server.

Use the Settings bundle for configuration when demonstrating the application since you can quickly change server settings without rebuilding the app and reinstalling. You may want to remove the settings bundle when releasing an app and use the values defined in Agent-Info.plist.

Build Settings and Related Warnings

ASA was developed for iOS 7.1, in Xcode 5.1. In Xcode 5.1 Apple added arm64 to the default Standard Architecture build setting. However, 64-bit versions of the libraries required for the optional Sled hardware integration for swiping a card were not available at the time of implementation and as a result the build settings for the Agent project were changed from the default (which builds 64-bit binaries) to the setting that builds 32-bit binaries. In Xcode, you will see many warnings related to this, such as Validate Project Settings and Update to recommended settings.

If you do not require the Sled integration code, you can remove it and change your build settings back to the default, standard architecture setting to resolve these warnings.

Third party libraries required for Sled integration

The ASA integration with Sled hardware lets a store associate swipe a credit or debit card using a payment Sled connected to the iPad device to take payment for an order.

This Sled integration was implemented and tested with AJB software. For information about Oracle’s integration with the AJB Framework, see the Oracle Retail Point-of-Service Installation Guide.

Note: The third-party AJB libraries are not included as part of ASA. Once you have acquired the AJB libraries:

ASA should now successfully build with these libraries.


Copyright © 1997, 2015 Oracle and/or its affiliates. All rights reserved. Legal Notices