Micropower/MiClub Membership Integration Install Guide

Date: Jan 2015

Scope:Setup instructions for thenew membership integration service between Micropower’s club management and MiClub’s club website.

Details: Will still be One way integration (MP to MiClub) which replacing current ODBC query and replacement process. Micorpower must setup and enable the club for MIS (membership integrated services) at the club infrastructure end before we can activate.

These are the items that Micropower needs to do to enable customers: you’ll need to liaise with a MP support person for this.

1.License MiClub and Club combination

2.Install our secure communication components on the club’s server

3.Configure the club router to accept requests from our server

4.Disable the ODBC driver

These are the task that need to be done on the MiClub product:

  1. Call MP to arrange the change over as per above
  2. we need to enable the integration via configuration settings and enter the ClubID in MiClub product
  3. Initial testing done
  4. Turn off task schedular on Club server that runs current ODBC batch file query

1.

Properties enabled are membership.ws.enabled = true

Enable module Micropower Integration which will set ws.membership.integration.enabled = true

Ensure correct micropower.client.id is set (provided from MP)

Set ws.accounts.locationurl as

Set micropower.member.search.keyto the value that the club is using as their key.

Fields NOT integrated are Private/silent option for each contact details, Security Code , Storage Locker, parent membership number, web user account status, representing country/state ,Middle name, Post title, handicap

Micropower Member Field / MiClub Member field
GolfLinkNo / Golflink_number requires integration.golflink.numbers.update set to true only when MiClub is not the Tier 3 supplier.
Categories (under Categories tab) / Level
Primary / Member_number (when micropower.member.search.key set to Primary)
BPay reference / Not used
AlphaCode / Member_number (when micropower.member.search.key set to AlphaCode)
MemberNo / Member_number (when micropower.member.search.key set to MemberNo)
AlternateMemberNo / Member_number (when micropower.member.search.key set to AltMemberNo)
ExternalMemberID / Not used
Surname / LastName
Title / title
FirstName / FirstName
PreferredName / Preferred_Name
FullName / Not used
Gender / gender
DOB / DateofBirth
JoinDate / JoinDate
ReinstateDate / Not used
Phone / Home Phone
Business Phone / Work Phone
Mobile / Mobile
Email1 / Home email
Email 2 / Work email
Address1 / Address line 1
Address2 / Address line 2
Address3 / Address line 3
Suburb / LocalityName
State / AdministrativeAreaName
Postcode / PostCode
Country / Country
FinancialToDate / Not used
MemberStatus (waitlist|Active|Resigned ) / Current Status (waitlist not used, resigned = inactive)
Web / Not used
WWW_Username / Username
WWW_password / Password security.authentication.alwaysUpdatePasswordFromIntegration = true
Fax / fax
Occupation / Not used
Employer / Not used
MailOptout
EmergencyName / Not used
EmergencyPhone / Not used
Account Delivery (mail | email1 | email2 ) / Email 1 = home , email 2 = work
MemberType (none| member | Debtor| Mem/Debtor) / Not used

Test Service

Access the Micropower Interface from the Admin Members Directory / Utilities menu

Select the View Member Fields button, if you get the interface returned back with the list of fields like below then we can confirm that communication between the systems is actively working. At this point you may deactivate the Task Scheduler on the club server so that the batch file for querying the ODBC doesn’t run anymore. Get Daniel K to do this as he has the list of access to the servers.

Notes:

How it works: We poll the MP membership service for any updates every hour. If you need to update change prior to the automatic update between the hourly intervals simply find the member in question and request an update or set the time/date and refresh the list of transaction changes and press process all button. There is a property to change the default update scheduled time which is membership.scheduled.job.interval

Request for changes from the past 10 days is not available (restricted by MP)

Note 2: When a member is made inactive (either un-financial or resigned) and the club uses MiClub as the Tier 3 provider, it will update the GolfLink/hcap status to invalid as well. When the member is financial and status is active it shall reactivate the hcap status as well.

There is no delay or grace day settings at the moment on our end to keep a resigned member still active on the website which is different from the last method. This setting will be available by Dec 2014.

New site setup

When we get a new MP site, the process to load up the initial database will be to request MP to “run the routine to allow the generation of “insert” records for all members and resigned members.”

These records can be generated by the Micropower Installer as part of the installation process if requested by MiClub for a particular site but must be scheduled for the evening so that it doesn’t affect server load performance at the club during operation hours.

1

MiClub / MP Member

Integration Guide