The first step to setting up the Personify Mobile for your organization is to execute specific files in order to prepare your Personify Database for the mobile application. The steps below apply to associations running on Personify 7.3.1 and above. Make sure you have installed all three service packs for 7.3.1 before proceeding.
If
you currently run on a Personify version from 7.1.2 - 7.3.1, make sure
you also follow the steps in Preparing
Databases on Personify 7.1.2 - 7.3.1 after completing the steps
below.
To prepare the Personify database:
1. Open SQL Server Management Studio 2008.
2. Navigate to the location where you copied the Personify Mobile Web Service Installation package.
3. Ensure the logged-in user has Sys Admin rights.
4. Open the Runner.cmd file in a text editor, such as Notepad.
5. Enter the valid SQL Server Connection information.
6. Close and save the Runner.cmd file.
7. Double-click Runner.cmd to execute the script.
8. After the script completes, confirm the following was created:
· 32 new Stored Procedures (all names starting with “MOBILE”)
· One new Full Text Catalog named FTC_FTS_CUSTOMER_INFO
· Two new tables:
o FTS_Controller (controls the Data Population and Image Service processes)
o FTS_Customer_Info (contains the customer information with search tags)
9. Navigate to the “MobileDeploymentPackage\DatabaseScripts\OneTimeScripts” folder and execute the UpdateCustomer_IncludeInDirectory script.
· This
one-time script updates the following for all customer records:
Customer.Include_In_Directory_Flag = True
This enables all customer records for viewing in the Directory module.
Your customers
will have the option to change the Include_In_Directory_Flag value to
“False” from the mobile device, if desired.
The “Include in Directory” flag is not currently visible from the CusCentral
screen. In order for your association to update this flag for customers
from the back-office, you need to make it visible using the Personify
Application Designer. Please refer to Installing
the Personify Mobile Web Service.
10. Navigate to the “MobileDeploymentPackage\DatabaseScripts\SqlJobs” folder and run the Catalog Population on FTC_FTS_CUSTOMER_INFO file.
· This
script replaces the YOUR_SQL_SERVER_NAME and YOUR_DATABASE_NAME tags with
actual values from customer records.
After the Data Population job is run, there should be data in FTS_CUSTOMER_INFO
table.
· This
script also creates an SQL JOB for optimizing catalog population for the
FTC_FTS_CUSTOMER_INFO full text catalog.
By default this job is configured to run every 4 hours, but it can be changed
as per client requirements.
11. Within the “MobileDeploymentPackage\DatabaseScripts\SqlJobs” folder, run the FTS_Customer_Info_Population file.
· This will create a. SQL JOB for populating the table FTS_CUSTOMER_INFO and keeping it current.
· It is recommended that you run this job once every day. By default the job runs at 11.40 PM every day, but it can be changes as per client requirements.
See Also: Manually Running FTS_CONTROLLER Processes