BLUEcloud Commerce Configuration Overview

BLUEcloud Commerce is a service provided by SirsiDynix which allows users to pay bills and purchase items from the library via a third-party online payment service, such as ProPay. Within SirsiDynix e-Library, this functionality allows patrons to pay bills from within their SirsiDynix e-Library account.

This topic covers the configuration to implement the use of the BLUEcloud Commerce functionality for SirsiDynix e-Library. For instructions on how to implement BLUEcloud Commerce functionality within WorkFlows, see the "BLUEcloud Commerce Configuration" help topic of the WorkFlows Online Help.

Before You Begin

Before you begin to configure BLUEcloud Commerce functionality for SirsiDynix e-Library, your library needs the following:

•

At least one merchant account set up with the payment service of your library's choice. This will be where the funds received from patrons making payments using BLUEcloud Commerce will be deposited.

Important: At this time, the only payment service compatible with BLUEcloud Commerce is ProPay. Therefore, to use the SirsiDynix BLUEcloud Commerce functionality, you need to have a merchant account set up with ProPay.

•

A BLUEcloud Commerce server URL. For optimal performance, SirsiDynix recommends using the URL of the BLUEcloud Commerce server geographically closest to your library. If you do not know the URL for your closest BLUEcloud Commerce server, contact SirsiDynix Customer Support.

WorkFlows Configurations for the Implementation BLUEcloud Commerce in SirsiDynix e-Library

Some system and policy configuration is necessary within the WorkFlows client to implement BLUEcloud Commerce within SirsiDynix e-Library.

BLUEcloud Commerce and Cash Management

If your library plans to use both BLUEcloud Commerce and the SirsiDynix Symphony Cash Management functionality, you must modify the LOGIN_USER_ACCESS variable in your SirsiDynix Symphony Payconfig file. Type a station user ID into this pipe-delimited field.

LOGIN_USER_ACCESS|CLERK|

The Payconfig file is located in the Unicorn/Webcat/Config directory of your SirsiDynix Symphony server.

If your library has both BLUEcloud Commerce and Cash Management functionality enabled, Cash Management will keep records of BLUEcloud Commerce transactions. If you would like to keep BLUEcloud Commerce transactions separate from other Cash Management transactions in Cash Management end of day reporting, SirsiDynix recommends creating a valid station user ID exclusively for BLUEcloud Commerce transactions for use in the LOGIN_USER_ACCESS variable. Therefore, transactions associated with that station user ID shown in the Cash Management End of Day report output will reflect only BLUEcloud Commerce transactions.

BLUEcloud Commerce Policies

Two policy types, BLUEcloud Commerce Account and BLUEcloud Commerce Service, control how the SirsiDynix BLUEcloud Commerce functionality interacts with your SirsiDynix Symphony server. To use BLUEcloud Commerce, your library needs to configure at least one BLUEcloud Commerce Account policy and modify the DEFAULT BLUEcloud Commerce Service policy. The following wizards allow you to configure these policies; they are both located in the Circulation Configuration group on the Configuration tab.

•

BLUEcloud Commerce Account Wizard – Use this wizard to create BLUEcloud Commerce Account policies, which define attributes such as which merchant account receives the funds from online payments and which payment service handles the transactions. For information on the BLUEcloud Commerce Account wizard, see the "BLUEcloud Commerce Account Wizard" help topic of the WorkFlows Online Help.

•

BLUEcloud Commerce Service Wizard – Use this wizard to modify the DEFAULT BLUEcloud Commerce Service policy, which defines attributes such as which BLUEcloud Commerce server to use and which BLUEcloud Commerce Account policy should be read when making BLUEcloud Commerce transactions, if a default BLUEcloud Commerce Account policy is set neither in the library nor the library group policy. For information on the BLUEcloud Commerce Service wizard, see the "BLUEcloud Commerce Service Wizard" help topic of the WorkFlows Online Help.

Note: Only one BLUEcloud Commerce Service policy exists and WorkFlows does not allow other BLUEcloud Commerce Service policies to be created. The SirsiDynix BLUEcloud Commerce server always uses the DEFAULT policy.

Library and Library Group policies

You should specify which BLUEcloud Commerce Account policy to associate with your library by default in your library's policy using the Library wizard. You should also specify which BLUEcloud Commerce Account policy SirsiDynix Symphony should use in the absence of a BLUEcloud Commerce Account policy defined for a given library using the Library Group wizard. In both policies, the attribute for defining a default BLUEcloud Commerce Account policy is BLUEcloud Commerce Account.

Language Policies

In order for BLUEcloud Commerce labels and messages to translate properly into the language of the patron, the ISO 639 language code and the ISO 3166 country code attributes must be defined in each Language policy for each possible language in which a patron could interface with BLUEcloud Commerce. Use the Language wizard to modify Language policy attributes.

For more information on the Language policy, see the "Language Wizard" help topic of the WorkFlows Online Help.

Currency Policies

To specify which type of currency the payment service should use to charge the card, the ISO 4217 currency code attribute must be defined in the Currency policy that also has the Native attribute defined. Use the Currency wizard to modify Currency policy attributes.

For more information on the Currency policy, see the "Currency Wizard" help topic of the WorkFlows Online Help.

SirsiDynix e-Library Configuration

Within SirsiDynix e-Library, you will need to enable BLUEcloud Commerce functionality from the Admin console. For the complete steps, see the Configuring BLUEcloud Commerce help topic.

After you complete these configurations, BLUEcloud Commerce will be ready to use within SirsiDynix e-Library.