I-Server 1.6 and Connectors Installation Instructions. Newmarket International, Inc. For Internal Use Only. Document Version 1.

Transcription

1 I-Server 1.6 and Connectors Installation Instructions Newmarket International, Inc. For Internal Use Only 12/20/05

2 Copyright 2005 Newmarket International, Inc. All rights reserved. The information in this document is confidential and proprietary to Newmarket International, Inc., and may not be disclosed, copied, reproduced, published, translated or reduced to electronic medium or machine readable form, in whole or in part, without the prior written consent of Newmarket International, Inc. Newmarket is a registered trademark and Delphi.Net. is a service mark of Newmarket International, Inc. Additional company and product names may be the registered trademarks or trademarks of their respective companies.

3 Table of Contents I-Server 1.6 and Connector Installation Appendix A Appendix B Installation Checklists Verify Prerequisites Installing I-Server Install Microsoft Software Create I-Server DB Run I-Server Setup Create a maintenance job to backup the NI_ISDB Rename the Nightly Scheduled Task Installing DSI Install Microsoft Software Create a System DSN pointing to the NSS_Database Run DSI Setup eproposal Fidelio PBSI Connector FMS Connector Galaxy LightSpeed Connector New Installs Galaxy LightSpeed Connector Upgrades Hilton OnQ Connector Marriott Siebel for I-Server MB Micros OXI Micros OXI New Installs Micros OXI Upgrades Opus TLP Connector Passkey Connector Property to Property v Serenata NetHotel Connector Starwood Meetings On Demand (SMD) Starwood Meetings in a Moment (SMM) SMS Host Appendix A Simulated Testing of Reservation Connectors A-1 Appendix B Services for Each Connector B-1 iii

4 Installation Checklists I-Server 1.6 and Connector Installation 1 Installation Checklists Follow the steps in the appropriate sections below to install the I-Server components. New I-Server Install Verify Prerequisites, page 1-2 Installing I-Server, page 1-2 Installing DSI, page 1-7 Complete manual steps for installing and testing the appropriate connector(s) eproposal, page 1-11 Fidelio PBSI, page 1-16 FMS, page 1-18 Galaxy, page 1-20 Hilton OnQ, page 1-25 Marriott Siebel, page 1-28 MB3, page 1-32 Micros OXI 1.0, page 1-35 Micros OXI 1.1 New Installs, page 1-37 Micros OXI 1.1 Upgrades, page 1-40 Opus TLP, page 1-43 Passkey, page 1-46 P2P v2.0, page 1-48 Serenata, page 1-54 SMD, page 1-55 SMM, page 1-57 SMS Host 1.0, page

5 Verify Prerequisites Verify Prerequisites The following software must be installed on each Delphi property server: Delphi or 9.2 Connectors to install: You need to know which connectors and connections are to be installed, and what properties are to be configured for each. Refer to the SOW (Statement of Work) for this information. The following software must be installed on the I-Server: Windows 2000 Server with the latest service packs, or 2003 Server SQL 2000 with SP3a Note Before installing SQL Server on the I-Server it is important to have the regional settings of the server set to English United States. If this is done prior to installing SQL Server the installation can use all default settings. The following media is required to install I-Server: Windows2000 or Windows2003 CD (or i386 folder) for IIS and MSMQ I-Server 1.6 CD Access to the Internet to install IE 6.0 SP1 (if necessary) Vendor Specific Prerequisites Passkey Connector - if a proxy server exists, you need the proxy information. Refer to the SOW. Access Administrate access for I-Server and DSI server(s) Installing I-Server The I-Server core software may be installed on the Delphi server, or on a separate server dedicated to I-Server depending on the customer s planned configuration. Consult the SOW for information on what server I-Server is to be installed on. Procedure 1 Install Microsoft Software The procedures for installing Microsoft software differ depending on the version of Windows (2000 or 2003) on the server. Please refer to the appropriate section below. Windows 2000 SQL Server 2000 SP3a If not already installed, install SQL 2000 and apply SP3a. See PSG document on how to install SQL

6 Installing I-Server IIS Install IIS from Control Panel, Add/Remove Programs, Add/Remove Windows Components. Select Front Page Extensions and accept all other installation defaults. Message Queuing Services Install Message Queuing Services from Control Panel, Add/Remove Programs, Add/Remove Windows Components. Accept all installation defaults except as noted below. If Terminal Services is installed, when prompted, select: Mode: Remote Administrative Mode Message Queuing Type: Message Queuing Server [do NOT select enable routing or AD checkboxes]* If Terminal Services is not installed, when prompted, select: Message Queuing Type: Independent Client [do NOT select AD checkbox]* Directory Service: Message Queuing will not access a directory service* * May not be needed if I-Server is standalone..net Runtime 1.1 Install.NET by running dotnetfx.exe from the dotnetredist folder on the I-Server 1.6 Installation CD. Accept all installation defaults. SOAP toolkit 3.0 (click support info to verify version if already installed: ) Install SOAP by running soapsdk.exe from the SOAP ToolKit 3.0 folder from the I-Server 1.6 Installation CD. Accept all installation defaults. When the Custom Setup window appears, click the Install button. MSMQ Triggers Install MSMQ Triggers by running msmqtriggers.exe from the MSMQ_Triggers folder from the I-Server 1.6 Installation CD. Accept all installation defaults. MSXML 4.0 (click support info to verify version if already installed: ) Install MSXML by running msxml.msi from the MSXML 4.0sp1 folder from the I-Server 1.6 Installation CD. Accept all installation defaults. When the Choose Setup Type window appears, click the Install Now button. IE 6.0 SP Server If IE is already installed, verify version is 6.0 SP1. Open Internet Explorer browser. From Help, click About Internet Explorer. If IE 6.0 SP1 is not installed, you must have access to the Internet to install it. Install IE by running ie6setup.exe from the IE6_SP1 folder from the I-Server 1.6 Installation CD, or you can download it from Microsoft s website. Accept all installation defaults. Note After you have installed IIE 6.0 SP1, you must reboot. SQL Server 2000 SP3a If not already installed, install SQL 2000 and apply SP3a. See PSG document on how to install SQL ASP.NET, IIS with Active Server pages, and Message Queuing. 1-3

7 Installing I-Server From the Control Panel, point to Add/Remove Programs, and click Add/Remove Windows Components. Highlight the Application Server option and click the Details button. In the Application Server window, verify ASP.NET, Message Queuing, and Internet Information Services (IIS) option are selected. In the Application server window, highlight Message Queuing and click the Details button. In the Message Queuing window, select Triggers, and click OK. In the Application server window, highlight Internet Information Services (IIS) and click the Details button. In the IIS window, select verify the Front Page Extensions, Internet Information Services Manager with Active Server pages and WWW Service options are selected. Click OK. In the Windows Configuration window, click Next. SOAP toolkit 3.0 (click support info to verify version if already installed: ) Install SOAP by running soapsdk.exe from the SOAP ToolKit 3.0 folder from the I-Server 1.6 Installation CD. Accept all installation defaults. When the Custom Setup window appears, click the Install button. MSXML 4.0 (click support info to verify version if already installed: ) Install MSXML by running msxml.msi from the MSXML 4.0sp1 folder from the I-Server 1.6 Installation CD. Accept all installation defaults. When the Choose Setup Type window appears, click the Install Now button. Enable active scripting in IE6.0 SP1. From Tools, point to Internet Options, and click the Security tab. Highlight the Internet icon and click the Custom Level button. Scroll to the Scripting area, and select Enable (default is Disable). Click OK to close. Procedure 2 Create I-Server DB 1. On the appropriate drive, create a folder named NI_ISDB where you want to place the database. If I-Server is being installed on the Delphi server, the folder is typically created on the same drive as the Delphi database. 2. Open query analyzer, login as SA, and select the Master database on the I-Server. 3. On the I-Server CD, open /NIIS_Setup/DatabaseScripts/Step1_Structure_CreateDatabase_v16.sql 1-4

8 Installing I-Server 4. Scroll down to the section outlined below. 5. Edit Path entry - Enter the folder where the NI_ISDB database will be installed (C:\NI_ISDB\ in the above example). Do not edit the other path entries. 6. Execute the script against the Master database. 7. Open and run the following scripts against the NI_ISDB database, in the order shown: a. Step2_Stored_Procedures_v16.sql b. Step3_Views_v16.sql c. Step4_Default_Data_v16.sql Procedure 3 Run I-Server Setup 1. Install I-Server by running Setup.exe from the NIIS_Setup folder on the I-Server 1.6 Installation CD. Accept all installation defaults except as noted below. 2. If you previously tried installing I-Server and the installation did not complete successfully, you may receive the Create Queue error message below. If this occurs click Ok and continue. 3. Choose Destination Location (for I-Server components) window Enter the location where the I-Server programs will be installed (keep NIIS as the folder name). 4. Choose Destination Location (for DSI components) window Enter the location where the DSI programs will be installed (keep DSI as the folder name). 5. Setup Type window Select Custom 6. Select Components window. See Important Notes below. Important Notes: 7. Note If you are installing the Fidelio PBSI Connector, select the Serenata NetHotel Interface. Note If you are installing the Siebel connector, do NOT select Siebel in the Select Components window. Select Integration Server Core Components only. You will install the connector components using a new Siebel Connector Installation CD when you run the manual steps. Note If you are installing a connector that is not listed in the Select Components window, select Integration Server Core Components only. You will install the connector components when you run the manual steps. 1-5

9 Installing I-Server Note To install P2P with I-Server 1.6, do not select P2P when installing I-Server or DSI. Select Integration Server Core Components only. Select the connectors to be installed 8. Integration Server IP Address window Enter the IP address of the local server (where I-Server is being installed onto) 9. Delphi Server Information window Enter the IP address of the Delphi database server (where the DSI is installed) Enter the Delphi database name (typically NSS_Database) 10. Add Another Delphi Server window Select Yes if you want to add another Delphi server. Select No if no other Delphi servers are being configured (other servers can be added later) 11. Install Admin Panel window(s) Select Yes to install Do not change Virtual directory (NIIS/AdminPanel) or Port (80) entries Procedure 4 Create a maintenance job to backup the NI_ISDB You must create a job to backup the NI_ISDB database daily. Schedule the job for 11PM unless there are valid reasons to use another time. For information on backing up databases, refer to the How to Backup a NI Database and Verify Scheduled Jobs document located on the intranet under Hardware/Scalability in the section. In the Systems Engineering (SE) recap, you must instruct the site to back up the file created by the NI_ISDB backup job. Procedure 5 Rename the Nightly Scheduled Task When I-Server is installed, property and user information from the Delphi database is placed in the NI_ISDB database. However, because Delphi user information may change at any time, or new properties may be added to the Delphi database, the RegisterDBServer.exe utility allows you to update the I-Server database with these changes. The utility is scheduled to run once a day, and by default is scheduled to run at 11:00pm. 1. From Start, point to Programs, Accessories, System Tools, and click Scheduled Tasks. Note The installation program has no control over what the scheduled task is named. The name is assigned by the script and starts with AT followed by a number, i.e. AT1. 2. Rename the scheduled task. a. To determine which task is the registerdbserver.exe task, right-click each task and click Properties. In the Task tab, you should see the RegisterDBServer.exe command line in the Run box, similar to the following: C:\NIIS\Bin\RegisterDBserver.exe /ALL b. Right-click on the RegisterDBServer task, and select Rename. c. Rename the scheduled task to RegisterDBServer. d. Click Apply to save. 1-6

10 Installing DSI Installing DSI The DSI is installed on the Delphi database server(s). If installing the Serenata or FMS connector in a linked environment, the DSI must also be installed on the Delphi Global server. Procedure 1 Install Microsoft Software Note If the I-Server software was installed on the Delphi database server, you may skip this procedure and proceed to Procedure 2 Create a System DSN pointing to the NSS_Database, page 1-8. The procedures for installing Microsoft software differ depending on the version of Windows (2000 or 2003) on the server. Please refer to the appropriate section below. Windows 2000 IIS Install IIS from Control Panel, Add/Remove Programs, Add/Remove Windows Components. Select Front Page Extensions and accept all other installation defaults. Message Queuing Services Install Message Queuing Services from Control Panel, Add/Remove Programs, Add/Remove Windows Components. Accept all installation defaults except as noted below. If Terminal Services is installed, when prompted, select: Mode: Remote Administrative Mode Message Queuing Type: Message Queuing Server [do NOT select enable routing or AD checkboxes]* If Terminal Services is not installed, when prompted, select: Message Queuing Type: Independent Client [do NOT select AD checkbox]* Directory Service: Message Queuing will not access a directory service* * May not be needed if I-Server is standalone. SOAP toolkit 3.0 (click support info to verify version if already installed: ) Install SOAP by running soapsdk.exe from the SOAP ToolKit 3.0 folder from the I-Server 1.6 Installation CD. Accept all installation defaults. When the Custom Setup window appears, click the Install button. MSXML 4.0 (click support info to verify version if already installed: ) Install MSXML by running msxml.msi from the MSXML 4.0sp1 folder from the I-Server 1.6 Installation CD. Accept all installation defaults. When the Choose Setup Type window appears, click the Install Now button. IE 6.0 SP1 If IE is already installed, verify version is 6.0 SP1. Open Internet Explorer browser. From Help, click About Internet Explorer. If IE 6.0 SP1 is not installed, you must have access to the Internet to install it. Install IE by running ie6setup.exe from the IE6_SP1 folder from the I-Server 1.6 Installation CD, or you can download it from Microsoft s website. Accept all installation defaults. Note After you have installed IIE 6.0 SP1, you must reboot. 1-7

11 Installing DSI 2003 Server ASP.NET, IIS with Active Server pages, and Message Queuing. From the Control Panel, point to Add/Remove Programs, and click Add/Remove Windows Components. Highlight the Application Server option and click the Details button. In the Application Server window, verify ASP.NET, Message Queuing, and Internet Information Services (IIS) option are selected. In the Application server window, highlight Message Queuing and click the Details button. In the Message Queuing window, select Triggers, and click OK. In the Application server window, highlight Internet Information Services (IIS) and click the Details button. In the IIS window, select verify the Front Page Extensions, Internet Information Services Manager with Active Server pages and WWW Service options are selected. Click OK. In the Windows Configuration window, click Next. SOAP toolkit 3.0 (click support info to verify version if already installed: ) Install SOAP by running soapsdk.exe from the SOAP ToolKit 3.0 folder from the I-Server 1.6 Installation CD. Accept all installation defaults. When the Custom Setup window appears, click the Install button. MSXML 4.0 (click support info to verify version if already installed: ) Install MSXML by running msxml.msi from the MSXML 4.0sp1 folder from the I-Server 1.6 Installation CD. Accept all installation defaults. When the Choose Setup Type window appears, click the Install Now button. Enable active scripting in IE6.0 SP1. From Tools, point to Internet Options, and click the Security tab. Highlight the Internet icon and click the Custom Level button. Scroll to the Scripting area, and select Enable (default is Disable). Click OK to close. Procedure 2 Create a System DSN pointing to the NSS_Database 1. Open Control Panel, Administrative Tools, ODBC Data Sources. 2. On the System DSN tab, click add and accept all installation defaults except as noted below. 3. Create New Data Source window - select the following: 1-8

12 Installing DSI Select SQL Server driver 4. Create a New Data Source to SQL Server window - enter the following: Name: NSS-MSSQL (all caps) Server: Enter the name of the local (Delphi) server 5. Create a New Data Source to SQL Server window - enter the following: Verify Authenticity: SQL Server authentication Login ID: ni_report Password: reportuser 6. Client Configuration (Edit Network Library Config) window - enter the following: Network Libraries: TCP/IP Server Alias: Local computer name Computer Name: Local computer name Dynamically Determine Port: Select the check box 7. Create New Data Source to SQL Server window - enter the following: Default database: nss_database Use ANSI quoted identifiers: Select this check box Use ANSI nulls: Select this check box 8. Test the connection and complete the installation. Procedure 3 Run DSI Setup Note Users do not need to be logged out of the Delphi servers in order to install the DSI. 1. Install DSI by running Setup.exe from the DSI_Setup folder on the I-Server 1.6 Installation CD. Accept all installation defaults except as noted below. 2. Choose Destination Location window - enter the following: Enter the location where the DSI programs will be installed (keep DSI as the folder name). 3. Setup Type window - select the following: Select Custom 4. Select Components window - See Important Notes below. Important Notes: 5. Note If you are installing the Fidelio PBSI Connector, select the Serenata NetHotel Interface. Note If you are installing the Siebel connector, do NOT select Siebel in the Select Components window. Select Integration Server Core Components only. You will install the connector components using a new Siebel Connector Installation CD when you run the manual steps. Note If you are installing a connector that is not listed in the Select Components window, select Integration Server Core Components only. You will install the connector components when you run the manual steps. Note To install P2P with I-Server 1.6, do not select P2P when installing I-Server or DSI. Select Integration Server Core Components only. 1-9

13 Installing DSI Note If installing LVCVA and LVCVA does not appear as an option, select P2P. 6. Delphi Server IP Address window - enter the following: Enter the IP address of the local server (DSI is always installed on the Delphi server) 7. Delphi Server Database Name window - enter the following: Enter the name of the Delphi database, typically NSS_Database 8. Delphi Property DSN window - enter the following: DSN: Enter NSS-MSSQL (all caps) 9. Integration Server IP Address window - enter the following: Enter the IP address of the I-Server server (where I-Server was installed) 10. Choose your Delphi Server NGS Folder window - enter the following: Some of the connectors will prompt you to identify where the Delphi NGS folder resides. 11. After the Setup Status window appears, if you are prompted for the Setup Rule to use with Account Production, select the setting as noted below. Note If you are installing a connector that was not on the Select Components window (in step 4), this window will appear when you install the connector using the unique connector installation CD. All connectors except for Hilton (FMS, OnQ): Account Production Defaults Hilton connectors (FMS, OnQ): Pick Up Only Note This window appears for reservation connectors that use the Account Production service. This web service updates and creates bookings based on actual nightly production from a third party system, (most likely reservations). 1-10

14 eproposal eproposal Note If both eproposal and MB3 are requested by the property, the eproposal connector must be installed before the MB3 connector. Prerequisite Prerequisite - Cendyn must be loaded prior to installing the eproposal connector. Manual Installation Steps 1. If both eproposal and MB3 connectors are requested by the property, check to see if the MB3 connector is installed. If it is, you must uninstall the MB3 connector before you install the eproposal connector. Once the eproposal connector is installed, you must re-install the MB3 connector and reconfigure connections. 2. Run the Cendyn eproposal installer. Note The Cendyn eproposal connector only needs to be installed on the NIIS (I-Server). You do not need to install it on the DSI server. Install the Cendyn eproposal connector from the Cendyn eproposal Installation CD by running Setup.exe. Accept all installation defaults. 3. Install appropriate hotfixes. Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed. Activation of eproposal Overview When activating and testing eproposal, the Property ID and address you use is determined by whether or not Cendyn has completed their database setup. Their setup is considered complete if they have assigned a Cendyn Property ID to the property AND entered the Cendyn user addresses into their database. Note Refer to the Technical Statement of Work (SOW) in NI s Property Information Database to determine whether the Cendyn setup is complete. Procedures if Cendyn Setup Complete If the Cendyn setup is complete, you must have the Cendyn Property ID and at least one valid Cendyn user address. 1. Perform Procedure 1, Activating eproposal, page 1-12, using the Cendyn Property ID. 1-11

15 eproposal 2. Perform Procedure 2, Verify Addresses for Cendyn Property Authorized Users, page 1-14 to make sure the addresses are consistent between the Delphi and Cendyn databases. 3. Perform Procedure 3, Testing, page Procedures if Cendyn Setup is Not Complete If the Cendyn setup is not complete, use a Test Property ID (to access Newmarket s test property on the Cendyn Server), and the test address, eproposaluser@newmarketinc.com. 1. Perform Procedure 1, Activating eproposal, page 1-12, using a Test Property ID. 2. Perform Procedure 3, Testing, page Procedure 1, Activating eproposal 1. Open the Internet Explorer Browser. 2. Enter the following address: Address of I-Server>/NIIS/adminpanel for example: The Admin Panel Welcome window appears. 3. Log on with a Delphi User Name and Password. Note The breezeop user does not open the Admin Panel. 4. Click the Login button. 1-12

16 eproposal The Admin Panel should open and appear similar to the following: 5. Click Connection Manager. A list of all Cendyn eproposal default connections appears. Note A default connection exists for each property. 6. Click the connection you wish to activate. 1-13

17 eproposal The Connection Details window appears. 7. Do one of the following: a. If Cendyn s setup is complete, enter the following: * Change Target Address to Cendyn s URL: webservices.cendyn.com Note Always use Cendyn s URL. Do not enter the Property s URL. * Change Others to the Cendyn Property ID. Note A unique Cendyn Property ID is created by Cendyn for each property. Please refer to the Technical Statement of Work (SOW) in NI s Property Information Database. b. If Cendyn s setup is not complete, enter the following: * Change Target Address to Cendyn s URL: webservices.cendyn.com Note Always use Cendyn s URL. Do not enter the Property s URL. * Change Others to one of the test property IDs: 8. Click Save Changes. Any Starwood property: 1242 (Starwood Test Property) Any property other than Starwood: 2162 (Newmarket Test Property) Note Once the Cendyn setup is complete, the test property ID needs to be replaced with the Cendyn Property ID. You are prompted to restart I-Server services manually. 9. Click OK. Note You do not need to manually restart I-Server services for Cendyn. 10. Click the Connection List link to select another connection to activate. Procedure 2, Verify Addresses for Cendyn Property Authorized Users 1-14

18 eproposal Note This procedure must be performed only if the Cendyn setup is complete. Cendyn provides Newmarket with a list of Cendyn Property Authorized Users for each property along with a Cendyn Property ID. This information is available in the Technical Statement of Work found on the Property Information Database. If the addresses between the Delphi and Cendyn databases do not match exactly, an error similar to the following occurs when the user tries to view an online proposal in Delphi: For example, if the user s address in Delphi is scarr123@newmarketinc.com, and in Cendyn it is different (i.e. scarr@newmarketinc.com), this error occurs. 1. From File, click Setup, and double-click Sales Reps. 2. Double-click the Sales Rep whose address you want to verify. Refer to the list of Cendyn Property Authorized Users found in the Technical Statement of Work on the Property Information Database. 3. Verify that each user s address matches those provided by Cendyn. Procedure 3, Testing Perform the appropriate procedure below to test eproposal. If Cendyn setup is complete, proceed to If Cendyn Setup is Complete, page If Cendyn setup is not complete, proceed to If Cendyn Setup is not Complete, page If Cendyn Setup is Complete If Cendyn has assigned a Cendyn Property ID for the property, you can verify launching of the Cendyn web page using a Delphi User who is an authorized eproposal user (their address is registered at that Cendyn Property ID). Note The Cendyn Property ID was entered in Step 7a on page Open the Delphi application and login as a Delphi user who is an authorized eproposal user. Refer to the list of Cendyn Property Authorized Users found in the Technical Statement of Work on the Property Information Database 2. Open an existing booking. 3. In the Booking Manager, select a booking contact that has an address. 1-15

19 Fidelio PBSI Connector Note If the booking contact does not have an address, the eproposal does not launch and you receive an error. 4. From the View menu, click Online Proposal. 5. If successful, the Cendyn web page opens. Note If an error occurs, verify the user s address in Delphi matches the address in Cendyn s database, and verify the booking contact has an address. 6. Close the window. If Cendyn Setup is not Complete If the Cendyn setup is not complete, you can test eproposal by using the generic address found in NI s test property databases. 1. Open the Delphi application. 2. In Setup, create a Sales Manager with the following generic test address: eproposaluser@newmarketinc.com 3. Open an existing booking. 4. In the Booking Manager, select a booking contact that has an address. Note If the booking contact does not have an address, the eproposal does not launch and you receive an error. 5. From the View menu, click Online eproposal. 6. If successful, the Cendyn test web page opens. Note If an error occurs, verify the generic user address was entered correctly (see Step 2), and verify the booking contact has an address. 7. Close the window. 8. Do one of the following: Fidelio PBSI Connector Manual Steps If the future Cendyn Property ID is not listed in the Technical SOW, escalate to the Client Services Project Manager, who will be responsible for entering the Cendyn Property ID when it becomes available. If the future Cendyn Property ID is listed in the technical SOW, you must enter the Admin Panel s Connection Manager and change the Other setting to the Cendyn Property ID. See Procedure 1, Activating eproposal, page 1-12 for instructions on opening the Connection Manager. a. From the Connection Details window, click the connection whose Cendyn Property ID you wish to change. b. Change Others to the Cendyn Property ID. Note Always use Cendyn s URL. Do not enter the Property s URL. 1-16

20 Fidelio PBSI Connector Note The Fidelio PBSI connector is the same as the Serenata NetHotel Interface, which was selected when you installed NIIS and DSI. Note If the connector is being installed in a linked environment, you must install on the Delphi and Global servers. Delphi Server 1. Using Notepad, edit the NGS/Delphi.ini file; change PostedRevenue=on 2. To the Delphi Server, add Serenata Triggers (to NSS_Database) Note Add triggers to the Delphi server only. Do NOT add to the Global server. a. On the I-Server server, open SQL query analyzer b. Connect to the Delphi server, and login as SA. c. Backup nss_database. d. Run the following scripts against the nss_database database: /NIIS/DatabaseScripts/AllAccountTriggers_v912.sql /NIIS/DatabaseScripts/Add_Business_Roomnite_Triggers_Script.sql 3. On each Delphi workstation where Delphi is running, you must instruct the local IT contact to run runonce.bat when logged onto the workstation as an administrator. Runonce.bat is located on the drive that is mapped to the NGS directory (usually N:) in the \EXE\ folder. Note This enables the ability to launch a Real-Time Availability update. 4. Run the Update_PMSINI_Table.sql query against nss_database to activate the Real Time Availability button in the Delphi application at a property. The query is located in the NIIS/DatabaseScripts folder. a. In the = xxxxx line, replace xxxxx with the property s PID. b. Run the query and repeat for each property that is enabled. 5. Open Delphi and click the PMS Guestroom Availability button in the GRC to confirm the Real Time Availability report opens. Note If the button is grayed out, click the GRC tab again. If this doesn t make the button active, click the To Do List tab, and then the GRC tab. This is a known issue which has been reported. 6. Open ProcessScript.xml in the DSI\MapFiles folder on the Delphi DB server and change the following entry as shown below: <priority value="1" filename="accountexport.js" recordstoprocess="100" /> 1-17

21 FMS Connector to <priority value="1" filename="accountexport.sql" recordstoprocess="200" /> 7. Open Connectors.xml in the DSI\Configuration folder and change the <scripts> section with the following: <scripts> <script name= AccountExport.js priority= 1 recordstoprocess= 100 /> to <scripts> <script name= AccountExport.sql priority= 1 recordstoprocess= 200 /> Global Server 1. Disable the ProptoIS service on Delphi Global Server. Note If running in a linked environment, the ProptoIS service is disabled on the Global sever ONLY. a. Open Control Panel, Administrative Tools, Services b. Change the ProptoIS start-up type to Disable. c. Stop the ProptoIS service. 2. Open ProcessScript.xml in the DSI\MapFiles folder on the Delphi Global DB server and change the following entry as shown below: <priority value="1" filename="accountexport.js" recordstoprocess="100" /> to <priority value="1" filename="accountexport.sql" recordstoprocess="200" /> 3. Open Connectors.xml in the DSI\Configuration folder and change the <scripts> section with the following: <scripts> <script name= AccountExport.js priority= 1 recordstoprocess= 100 /> to Testing <scripts> <script name= AccountExport.sql priority= 1 recordstoprocess= 200 /> Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed. FMS Connector 1. Complete Appendix A Simulated Testing of Reservation Connectors, page A-1, for the NetHotel connector. Manual Steps 1-18

22 FMS Connector 1. Using Notepad, edit the NGS/Delphi.ini file; change PostedRevenue=on Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed. Testing To test the changes to the Delphi.ini file: 1. Log on to Delphi. 2. Open an existing Group Booking (not transient). 3. Click the Revenue button. 4. Verify there is a new column in the grid called Posted Revenue. 1-19

23 Galaxy LightSpeed Connector New Installs Galaxy LightSpeed Connector New Installs Note This section is for new installations of Galaxy version 1.1 only. If you are upgrading to 1.1, see Galaxy LightSpeed Connector Upgrades, page Manual Steps Note If the connector is being installed in a linked environment, you must install on the Delphi and Global servers. Delphi Server 1. Run the Reservations Connector to Galaxy LightSpeed installer. Note If NIIS and DSI were installed on the same server, you only have to run the Galaxy LightSpeed installer once. If NIIS and DSI are on separate servers, you must run the Galaxy LightSpeed installer on each server. Install the Galaxy LightSpeed connector from the Galaxy LightSpeed Installation CD by running Setup.exe. Accept all installation defaults except as noted below. a. Select the appropriate rule for each of the following options. Please refer to the SOW for correct setting: Select rule for Account Production window- select all rates (default) Note The Pickup only option is to be used exclusively for Hilton OnQ sites. Select rule for Guest Room rates window- select Do not override Delphi rates (default) Note If required, this setting will be adjusted per property by the on-site installer.** Select rule for Account validation window- select Do not validate the account key (default) Note Do NOT select the Validate the account key option. **Note There is now a procedure in the Galaxy v1.1 Connector Configuration document, which explains how to change this setting for each individual property: to use Delphi rates or Vendor rates only. The trainer runs one of the new scripts the installation program places in \\DSI\DatabaseScripts: ApplyRateFromVendor.sql or ApplyDefaultRates.sql query 2. Choose your Delphi Server NGS folder? 3. Using Notepad, edit the NGS/Delphi.ini file; change PostedRevenue=on 4. On the Delphi server only, add Triggers (to NSS_Database). Note Add triggers to the Delphi server only. Do NOT add to the Global server. a. On the I-Server server, open SQL query analyzer b. Connect to the Delphi server, and login as SA. 1-20

24 Galaxy LightSpeed Connector New Installs c. Backup nss_database. d. Run the following scripts against the nss_database database: /NIIS/DatabaseScripts/AllAccountTriggers_v912.sql /NIIS/DatabaseScripts/Add_Business_Roomnite_Triggers_Script.sql 5. On each Delphi workstation where Delphi is running, you must instruct the local IT contact to run runonce.bat when logged onto the workstation as an administrator. Runonce.bat is located on the drive that is mapped to the NGS directory (usually N:) in the \EXE\ folder. Note This enables the ability to launch a Real-Time Availability update. 6. Run the Update_PMSINI_Table.sql query against nss_database to activate the Real Time Availability button in the Delphi application at a property. The query is located in the NIIS/DatabaseScripts folder. a. In the = xxxxx line, replace xxxxx with the property s PID. b. Run the query and repeat for each property that is enabled. 7. Open Delphi and click the PMS Guestroom Availability button in the GRC to confirm the Real Time Availability report opens. Note If the button is grayed out, click the GRC tab again. If this doesn t make the button active, click the To Do List tab, and then the GRC tab. This is a known issue which has been reported 8. Open ProcessScript.xml in the DSI\MapFiles folder on the Delphi DB server and change the following entry as shown below: <priority value="1" filename="accountexport.js" recordstoprocess="100" /> to <priority value="1" filename="accountexport.sql" recordstoprocess="200" /> 9. Open Connectors.xml in the DSI\Configuration folder and change the <scripts> section with the following: <scripts> <script name= AccountExport.js priority= 1 recordstoprocess= 100 /> to <scripts> <script name= AccountExport.sql priority= 1 recordstoprocess= 200 /> Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed. Global Server 1. Repeat step 1 on the Global server. 2. Disable the ProptoIS service on Delphi Global Server. Note If running in a linked environment, the ProptoIS service is disabled on the Global sever ONLY. a. Open Control Panel, Administrative Tools, Services b. Change the ProptoIS start-up type to Disable. c. Stop the ProptoIS service. 1-21

25 Galaxy LightSpeed Connector New Installs 3. Open ProcessScript.xml in the DSI\MapFiles folder on the Delphi Global DB server and change the following entry as shown below: <priority value="1" filename="accountexport.js" recordstoprocess="100" /> to <priority value="1" filename="accountexport.sql" recordstoprocess="200" /> 4. Open Connectors.xml in the DSI\Configuration folder and change the <scripts> section with the following: <scripts> <script name= AccountExport.js priority= 1 recordstoprocess= 100 /> to Testing <scripts> <script name= AccountExport.sql priority= 1 recordstoprocess= 200 /> Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed. 1. To test the changes to the Delphi.ini file: a. Log on to Delphi. b. Open an existing Group Booking (not transient). c. Click the Revenue button. d. Verify there is a new column in the grid called Posted Revenue. 2. To test the connection, complete Appendix A Simulated Testing of Reservation Connectors, page A

26 Galaxy LightSpeed Connector Upgrades Galaxy LightSpeed Connector Upgrades This section is for Upgrades to Galaxy version 1.1 only. If you performing a new installation of v1.1, see Galaxy LightSpeed Connector New Installs, page Important. Do NOT uninstall v1.0 after you have installed 1.1. Manual Steps Note If the connector is being installed in a linked environment, you must install on the Delphi and Global servers. Delphi Server 1. Run the Reservations Connector to Galaxy LightSpeed v1.1 installer. Note If NIIS and DSI were installed on the same server, you only have to run the Galaxy LightSpeed installer once. If NIIS and DSI are on separate servers, you must run the Galaxy LightSpeed installer on each server. a. Select the appropriate rule for each of the following options. Please refer to the SOW for correct setting: Select rule for Account Production window- select all rates (default) Note The Pickup only option is to be used exclusively for Hilton OnQ sites. Select rule for Guest Room rates window- select Do not override Delphi rates (default) Note If required, this setting will be adjusted per property by the on-site installer.** Select rule for Account validation window- select Do not validate the account key (default) Note Do NOT select the Validate the account key option. 2. Choose your Delphi Server NGS folder. 3. Using Notepad, verify PostedRevenue=ON in the NGS/Delphi.ini file. 4. On the Delphi server only, add Triggers (to NSS_Database). Note Add triggers to the Delphi server only. Do NOT add to the Global server. a. On the I-Server server, open SQL query analyzer b. Connect to the Delphi server, and login as SA. c. Backup nss_database. d. Run the following scripts against the nss_database database: /NIIS/DatabaseScripts/AllAccountTriggers_v912.sql /NIIS/DatabaseScripts/Add_Business_Roomnite_Triggers_Script.sql 5. Open ProcessScript.xml in the DSI\MapFiles folder on the Delphi DB server and verify the following entry is as shown below: <priority value="1" filename="accountexport.sql" recordstoprocess="200" /> 6. Open Connectors.xml in the DSI\Configuration folder and verify the <scripts> section is as shown below: <scripts> <script name= AccountExport.sql priority= 1 recordstoprocess= 200 /> 1-23

27 Galaxy LightSpeed Connector Upgrades 7. During installation guestroom rates are set to the Do not override Delphi rates (default) option for all properties. If any of the properties want to use Galaxy rates instead, you must run the following script, located in \\DSI\DatabaseScripts. a. Open the following script in Query Analyzer. ApplyRateFromVendor.sql b. In the select@pid= enter the PID of the property you are configuring and execute the query against nss_database. c. Save the file as ApplyRateFromVendor_<SiteName>.sql where <SiteName> is the name of the property you are configuring. 8. If you need to change any property back to using Delphi rates only, run the following script: a. To configure the property to use Delphi rates only, open the following script in Query Analyzer. ApplyDefaultRates.sql b. In the select@pid= enter the PID of the property you are configuring and execute the query against nss_database. c. Save the file as ApplyDefaultRates_<SiteName>.sql where <SiteName> is the name of the property you are configuring. Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed. Global Server 1. Repeat step 1 on the Global server. 2. Disable the ProptoIS service on Delphi Global Server. Note If running in a linked environment, the ProptoIS service is disabled on the Global sever ONLY. a. Open Control Panel, Administrative Tools, Services b. Change the ProptoIS start-up type to Disable. c. Stop the ProptoIS service. 3. Open ProcessScript.xml in the DSI\MapFiles folder on the Delphi DB server and verify the following entry is as shown below: <priority value="1" filename="accountexport.sql" recordstoprocess="200" /> 4. Open Connectors.xml in the DSI\Configuration folder and verify the <scripts> section is as shown below: Testing <scripts> <script name= AccountExport.sql priority= 1 recordstoprocess= 200 /> Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed. 1-24

28 Hilton OnQ Connector Hilton OnQ Connector 1. To test the changes to the Delphi.ini file: a. Log on to Delphi. b. Open an existing Group Booking (not transient). c. Click the Revenue button. d. Verify there is a new column in the grid called Posted Revenue. 2. To test the connection, complete Appendix A Simulated Testing of Reservation Connectors, page A-1. Manual Steps - 1. Run the Reservations Connector to Hilton OnQ installer. Note If NIIS and DSI were installed on the same server, you only have to run the Hilton OnQ installer once. If NIIS and DSI are on separate servers, you must run the Hilton OnQ installer on each server. Install the Hilton OnQ connector from the Hilton OnQ Installation CD by running Setup.exe. Accept all installation defaults except as noted below. a. When the Account Production window appears, select Pick Up Only. 2. Using Notepad, edit the NGS/Delphi.ini file; change PostedRevenue=on 3. Disable the ProptoIS service on Delphi Global Server. If running in a linked environment, the ProptoIS service is disabled on the Global sever ONLY. a. Open Control Panel, Administrative Tools, Services b. Change the ProptoIS start-up type to Disable. c. Stop the ProptoIS service. 4. Deploy the OnQ Connector Future Bookings Report. Move the file to NGS a. Under the central NGS folder, create a folder called Reports. b. Copy the OnQ Connector Future Bookings Report.xls file from the Hilton OnQ Installation CD to the \NGS\Reports folder. c. Create a shortcut to the report for users who need access to the report. Opening reports in Excel a. If you created a shortcut, then simply double-click the shortcut to open the report, or follow step b-step c. 1-25

29 Hilton OnQ Connector b. Click the Excel icon. c. On the File menu, point to Open, and then click Browse for the Reports Folder under the NGS share (usually N:\Reports). Note If you receive any runtime errors upon opening the Excel reports, see Procedure 3 Manual Steps for Installing and Testing Connectors, page Terminal Server Considerations The following information is provided for Terminal Server administrators. You can disable Macro Security and enter registry information for current users when you log in by modifying Terminal Server login scripts. If Citrix is used, you can launch the report by publishing it as a Citrix Published Application. The following information is provided for reference only. Depending on the version of Office you are running, the value needed may be different. Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Excel\Security]"L evel"=dword: You must enter the following information for each user logging in to run the OnQ bookings report. This information can be entered at login time to HKCU. You should change the 'servername' value to reflect the NETBIOS name of the Delphi database server. Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\VB and VBA Program Settings\NI_Reports\Future_Booking_Report]"RanSetup"="True""Server"="server name""database"="nss_database""seconds"="10""fontsize"="9" Troubleshooting Enabling Macros to Run in Excel Macros must be enabled and trusted in order to run the OnQ Booking Report. 1. Open Excel. Note If any report files are open, please close them. 2. On the Tools menu, point to Macro, and then click Security. 1-26

30 Hilton OnQ Connector 3. Select Low. 4. Click the Trusted Sources tab and then select Trust access to Visual Basic Project. Testing Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed. To test the changes to the Delphi.ini file: 1. Log on to Delphi. 2. Open an existing Group Booking (not transient). 3. Click the Revenue button. 4. Verify there is a new column in the grid called Posted Revenue. 1-27

31 Marriott Siebel for I-Server 1.6 Marriott Siebel for I-Server 1.6 Important: Before testing Siebel, make sure the SToDServer is disabled or I-Server is uninstalled from the old server. On any future installs/upgrades/server swaps please make sure either you or the site disables the Siebel Service on the old server. Even if I-Server has not previously been installed it is possible the Siebel interface is running (the legacy version). In this case the service name is 'Siebel To Delphi Interface' not 'stodservice' as it is in the I-Server. If you are not able to get to the old server please have the site verify that Siebel is disabled on the old server. Manual Steps Procedure 1, Install the Siebel Connector Note Since NIIS and DSI are installed on the same server for Siebel, you only have to run the Siebel connector installer once. 1. Install the Siebel connector from the Siebel Connector Installation CD by running Setup.exe. Procedure 2, Change Application Protection Note This procedure only needs to be performed if using IIS 5.0. Change the Application Protection on the NIIS Virtual Directory as follows. 1. Open the Internet Information Services Manager. 2. Right-click the NIIS virtual directory, and select Properties. 3. On the General tab, change Application Protection to Low, and click Apply. Procedure 3, Run the Configuration Utility New Installation The Configuration Utility allows you to enter the following required registry parameters: the MARSHA code, Delphi PID, the property name, and website login name and password. If you need to change the parameters for a property or delete a property from the I-Server database, see Using the Configuration Utility, page B-24. Note The parameters entered in the following configuration utility are case sensitive. 1. On the I-Server, browse to NIIS/Utility. 2. Double-click SToDReg.exe. The Siebel Interface Configuration Utility window appears. 3. Under Web Server Details, click the Edit button. 1-28

32 Marriott Siebel for I-Server In the User Name box, enter SFADelphi. 5. In the Password box, enter I8dasbox. 6. In the HTTP URL box, enter the following: 7. In the Polling Interval box, enter 120. Note The 120 represents seconds. 8. If the parameters are correct click the Save button to save the parameters. Note If a mistake has been made click the Cancel button. 9. Under Property Details, click the New button. (The Siebel SFA Interface supports DMPE for multiple properties.) 10. In the Delphi PID box, enter the property s PID number. 11. In the Property Name box, enter the name of the property for which the interface will be installed. The name must be entered exactly as it appears in the Delphi database (to determine the exact name, run the following query: SELECT * FROM PROPERTYVIEW, the field name is ORG_NAME). 12. In the MARSHA Passcode box, enter and confirm the passcode obtained from Marriott International s corporate office. If this information was not provided in the SOW, contact Marriott at to get this information. Note The MARSHA Passcode is unique for each property. 13. In the InProcess box, enter the value 0. Note The value must be 0 or 1. 0 indicated the property is ready for any further opportunities processing. 1 indicated that opportunities for this property are currently in process) 14. If the parameters are correct click the Save button to save the parameters. Note If a mistake has been made click the Cancel button. 15. Click OK on the alert box stating the property settings saved successfully. 16. Click the Exit button to close the utility. Adding an Additional Property at a Later Date If you need to install Siebel at another property, use the Configuration utility to add the property, and run the registerdb.exe utility to add the property and associated users to the I-Server database. Add a Property Note The parameters entered in the following configuration utility are case sensitive. 1. On the I-Server, browse to NIIS/Utility. 2. Double-click SToDReg.exe. The Siebel Interface Configuration Utility window appears. 3. Under Property Details, click the New button. (The Siebel SFA Interface supports DMPE for multiple properties.) 1-29

33 Marriott Siebel for I-Server In the Delphi PID box, enter the property s PID number. 5. In the Property Name box, enter the name of the property for which the interface will be installed. 6. In the MARSHA Passcode box, enter and confirm the passcode obtained from Marriott International s corporate office. Note The MARSHA Passcode is unique for each property. 7. In the InProcess box, enter the value 0. Note The value must be 0 or 1. 0 indicated the property is ready for any further opportunities processing. 1 indicated that opportunities for this property are currently in process) 8. If the parameters are correct click the Save button to save the parameters. Note If a mistake has been made click the Cancel button. 9. Click OK on the alert box stating the property settings saved successfully. 10. Click the Exit button to close the utility. Procedure 4, Change COM+ Package IDs and Run Autopatch 1. Change the identity on the following COM+ packages to use the NIAdmin account: DSI, NIIS_Export, NIIS_Import, NIIS_Status 2. Apply hotfixes by running the autopatch located on the ftp server in the \psg\download\iserver16 folder. Procedure 5, Start SToDService The service must be started after installation and anytime the computer is restarted. 1. From Start, point to Settings, and click Control Panel. 2. Double-click Administrative Tools and open Services. 3. Scroll to the SToDService. 4. If the service is not already started, right-click the SToDService and click Start. 5. Right-click the SToDService and click Properties. 6. Click the General tab, and select Automatic from the Startup Type list. 7. Click the Logon tab, and select This Account and add the NIAdmin user. 8. Click OK. Testing Verify data passes between Delphi & Siebel 1-30

34 Marriott Siebel for I-Server Call the Marriott Help Desk ( ) and request that a test opportunity (lead) be sent to the property. The Help Desk should already be aware of this request, as they should have been notified during the Scope of Work process. 2. Verify an XML log file in the log directory exists. This indicates the test lead has been sent and received. 3. Login to Delphi as Breezeop and verify the test booking has been created. 4. Delete the test booking. 5. Create a scheduled task to delete log files older than 30 days. 6. Repeat steps step 1 - step 4 to verify another test lead. 1-31

35 MB3 MB3 Prerequisites Running the Delphi/MeetingBroker Integration (9.2.1 with MB3) on a Windows 2003 Terminal server requires the following pre-requisites: If Terminal Server is Windows 2003 and Metaframe XP 1.0 Windows 2003 SP1 must be installed Metaframe XP 1.0 SP4 must be installed Metaframe HotFix CTX must be installed Note If both MB3 and eproposal are requested by the property, the eproposal connector must be installed before the MB3 connector. Uninstall Note If the MB3 Connector is uninstalled you must stop the NIIS_Export package. Then remove the MeetingBroker.dll from the \\NIIS\bin directory. Manual Installation Steps see CR MBPollingService is set to Manual after Connector Installation Procedure 1, How to Proceed if eproposal Connector is also to be Installed If both eproposal and MB3 connectors are requested by the property, make sure you install the eproposal connector befre installing the MB3 connector. See eproposal, page 1-11 for instructions on installing the eproposal connector. Procedure 2, Installing the Connector 1. Install the MB3 connector from the MB3 Installation CD by running Setup.exe. Note If NIIS and DSI were installed on the same server, you only have to run the MB3 installer once. If NIIS and DSI are on separate servers, you must run the MB3 installer on each server. MeetingBroker Polling Cycle - Refer to the SOW, which indicates whether the site is using Passive or Active mode. If using Passive, the site must specify whether to set the polling at 5, 10, 15, 30, 60, or 240 minutes. MeetingBroker Server IP Address - enter the following URL for the MeetingBroker server: my.meetingbroker.com Note Do not enter or before the URL. 2. Install appropriate hotfixes. Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed. 3. Add HTTP/HTTPS calls through Proxy server. 1-32

36 MB3 Note You do not need to add the HTTP/HTTPS calls unless the site is using a proxy server or requires authentication. If not needed, proceed to the next section, Procedure 3, Activating Connections, page a. On the I-Server server, open SQL query analyzer b. Open the following script against the I-Server database (NI_ISDB). /NIIS/DatabaseScripts/ProxyConfiguration.sql c. Scroll to the following entries, and enter the appropriate information. Refer to the SOW: = ' ' = ' ' = ' ' = ' ' This is the username to use to authenticate against the proxy server This is the password for the username used to authenticate against the proxy server Specify one or more proxy server names or IPAddresses. Separate each name with a comma (,) Specify one or more bypass server names or IpAddresses. Separate each name with a comma (,) d. Execute the query. Procedure 3, Activating Connections When the MB3 connector is installed, the install program automatically creates the following service connections for each property: Setup Values, Create Meeting, Update Proposal, Error Service, and MB Polling. If the connector is installed at a standalone SPE site, five connections are created, one for each service. If installed at a DMPE site, the five connections are created for each property in the DMPE regardless of whether or not MeetingBroker has been installed at all properties. For example, if the DMPE is a 4 property DMPE, 20 connections are created (4 properties * 5 services = 20 connections). Note Refer to the Technical Statement of Work (SOW) in NI s Property Information Database to determine whether the MeetingBroker application has been installed at the property. 1. Open the Admin Panel. 2. Click Connection Manager. A list of all MB3 default connections appears. 3. Do one of the following: a. If the MeetingBroker application installation is complete at a property, click one of the five connections for that property, and enter the following in the exact order shown below: * Change Target Address to the MeetingBroker server s URL: my.meetingbroker.com Note Do not enter or before the URL. * Enter the password for the MB location. Please refer to the Technical Statement of Work (SOW) in NI s Property Information Database. * Change Setup Mode to No. b. If the MeetingBroker application installation is not complete at the property, leave the connection entries at their default values. 1-33

37 MB3 Note Once the MeetingBroker application setup is complete at the property, the default test Target Address needs to be replaced with the MeetingBroker server address for the property. 4. Click Save Changes. You are prompted to restart I-Server services manually. 5. Click OK. 6. Click the Connection List link to select another connection to activate for the property. Repeat for each of the property s five MB connections. 7. Repeat step 3 - step 6 for each property. Procedure 4, Stop and Start Services 1. On the I-Server, from Start, point to Programs, Administrative Tools, and click Services. 2. Scroll down to the Multi-Threaded Export Service. 3. Right-click the service and click Stop. 4. Click Yes to the stop message. Stopping the multi-threaded export service, shuts down the prestaging, multi-threaded export, and delegator services. 5. Once the services have stopped, scroll to the Prestaging Service, right-click, and click Start. Starting the Prestaging Service starts all three services that were stopped. 6. If the property is configured for Passive mode, set the MBPollingService to Automatic on the I-Server and start the service. Testing You can verify launching of the MeetingBroker web page using a Delphi User who is an authorized MeetingBroker user. 1. Open the Delphi application and login as a Delphi user who is an authorized MeetingBroker user. 2. Open an existing booking. 3. In the Booking Manager, click the Create Mtg button. 4. One of the following occurs: If the MeetingBroker application installation is complete, the MeetingBroker web Login page opens if the installation was successful. Note If an error occurs, verify the user s address in Delphi matches the address in MeetingBroker s database. And verity the password is entered correctly in the Connection Manager. If the MeetingBroker application installation is not complete, the default target address for the connections (the IP Address of I-Server), calls the following test page: If the MeetingBroker setup is not complete, you can test MeetingBroker by using the generic address found in NI s test property databases. Note If an error occurs, open the Connection Manager and confirm the URL in the Target Address is correct. 1-34

38 Micros OXI 1.0 Micros OXI Close the window. Note This section is for Micros OXI version 1.0 only. If you are installing version 1.1, see Micros OXI New Installs, page If you are upgrading to 1.1, see Micros OXI Upgrades, page Manual Steps Note If the connector is being installed in a linked environment, you must install on the Delphi and Global servers. Delphi Server 1. Run the Micros OXI installer. Note If NIIS and DSI were installed on the same server, you only have to run the Micros OXI installer once. If NIIS and DSI are on separate servers, you must run the Micros OXI installer on each server. Install Micros OXI from the Micros OXI Installation CD/Setup.exe. Accept all installation defaults except as noted below. DSI Specific Installation Windows a. When the Account Production window appears, select Account Production Defaults. Note The Account Production window appears only when installing the connector on the DSI server. NIIS Specific Installation Window a. Install Account Link Utility window(s) Select Next to install Do not change Virtual directory (NIIS/OXI/AccountLink) or Port (80) entries b. Install Enhanced Configuration Setup window Select Next to install Do not change Virtual directory (NIIS/OXI/EnhancedConfiguration) or Port (80) entries 2. Using Notepad, edit the Delphi.ini file located in NGS/INI; change PostedRevenue=on 3. Backup the nss_database. 4. On the Delphi server only, add Triggers (to NSS_Database). Note Add triggers to the Delphi server only. Do NOT add to the Global server. 1-35

39 Micros OXI 1.0 a. Open and run the following scripts, located on the Micros OXI 1.0 CD in DatabaseScripts, against the Delphi database. /DatabaseScripts/AllAccountTriggers_v912.sql /DatabaseScripts/Add_Business_Roomnite_Triggers_Script.sql /DatabaseScripts/Add_Micros_OXI_Business_trigger.sql 5. Create tables and stored procs for use by OXI, in the I-Server database. a. Open and run the following scripts, located on the Micros OXI 1.0 CD in DatabaseScripts, against the NIIS database: /DatabaseScripts/OXI_CreateTable.sql /DatabaseScripts/OXI_CreateStoredProc.sql b. Open and run the following script, located in \\niftp\psg\download\iserver16\hotfixes\, against the NIIS database: OXI_CreateNightlyProcs.sql 6. Set permissions on \niis\mapfiles\micros_messagemapping.xml to Everyone change. 7. Change the PollingServiceCycle and InventoryServiceCycle to 60 in the Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Newmarket\Integration Server\InventoryServiceCycle The InventoryService will sleep 60 minutes between each cycle. HKEY_LOCAL_MACHINE\SOFTWARE\Newmarket\DelphiServiceInterface\PollingServiceCycle The PollingService will fetch a transaction from I-Server every 60 seconds. 8. Verify the PropToISIserviceCycle is set to 60 in the Registry HKEY_LOCAL_MACHINE\SOFTWARE\Newmarket\DelphiServiceInterface\PropToISServiceCycle The PropToISService will sleep 60 seconds between each cycle. 9. Change the Exceptions Report purge cycle from 20 hours to 10 hours. Note If these registry settings do not exist, add them manually (on the computer housing the I-Server) HKEY_LOCAL_MACHINE\SOFTWARE\Newmarket\Integration Server\propertyDataPurgeTime (=10) HKEY_LOCAL_MACHINE\SOFTWARE\Newmarket\Integration Server\vendorDataPurgeTime (=10) 10. Open ProcessScript.xml in the DSI\MapFiles folder on the Delphi DB server and change the following entry as shown below: <priority value="1" filename="accountexport.js" recordstoprocess="100" /> to <priority value="1" filename="accountexport.sql" recordstoprocess="200" /> 11. Open Connectors.xml in the DSI\Configuration folder and change the <scripts> section with the following: <scripts> <script name= AccountExport.js priority= 1 recordstoprocess= 100 /> to <scripts> <script name= AccountExport.sql priority= 1 recordstoprocess= 200 /> Global Server 1. Repeat step 1 on the Global server. 1-36

40 Micros OXI New Installs 2. Disable the ProptoIS service on Delphi Global Server. Note If running in a linked environment, the ProptoIS service is disabled on the Global sever ONLY. a. Open Control Panel, Administrative Tools, Services b. Change the ProptoIS start-up type to Disable. c. Stop the ProptoIS service. 3. Open ProcessScript.xml in the DSI\MapFiles folder on the Delphi Global DB server and change the following entry as shown below: <priority value="1" filename="accountexport.js" recordstoprocess="100" /> to <priority value="1" filename="accountexport.sql" recordstoprocess="200" /> 4. Open Connectors.xml in the DSI\Configuration folder and change the <scripts> section with the following: <scripts> <script name= AccountExport.js priority= 1 recordstoprocess= 100 /> to Testing <scripts> <script name= AccountExport.sql priority= 1 recordstoprocess= 200 /> Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed.. 1. Test URLs: Micros OXI New Installs Address of I-Server>/NIIS/adminpanel - Verify the admin panel opens. name>/niis/oxi/accountlink/accountlinkpage.aspx - Verify the Account Link utility opens. name>/niis/oxi/service/messagereceptor.aspx - Verify you receive a Successful message, which ensures niis is installed properly. name>/niis/oxi/enhancedconfiguration/enhancedconfigurationpage.aspx - Verify the configuration utility opens. Note This section is for new installations of Micros OXI version 1.1 only. If you are installing version 1.0, see Micros OXI 1.0, page If you are upgrading to 1.1, see Micros OXI Upgrades, page Manual Steps Note If the connector is being installed in a linked environment, you must install on the Delphi and Global servers. Delphi Server 1. Backup the nss_database. 2. Run the Micros OXI 1.1 installer. Note If NIIS and DSI were installed on the same server, you only have to run the Micros OXI installer once. If NIIS and DSI are on separate servers, you must run the Micros OXI installer on each server. 1-37

41 Micros OXI New Installs Install Micros OXI from the Micros OXI Installation CD/Setup.exe. Accept all installation defaults except as noted below. 1-38

42 Micros OXI New Installs DSI Specific Installation Windows a. DB Server Login Info - enter the SQL administrator name, password, and the name of the Delphi database. b. Select the appropriate rule for each of the following options. Please refer to the SOW for correct setting: Select rule for Account Production window- select all rates (default) Note The Pickup only option is to be used exclusively for Hilton OnQ sites. Select rule for Guest Room rates window- select Do not override Delphi rates (default) Note If required, this setting will be adjusted per property by the on-site installer.** Select rule for Account validation window- select Do not validate the account key (default) Note Do NOT select the Validate the account key option. **Note If the on-site installer changed this option from the default, and the Micros OXI connector has to be reinstalled at a later date, this option will be reset to the default by the installation program. The connector will not work as expected, so it is recommended that the connections be disabled by the person who is reinstalling the connector. This person will then need to run the OXI_RES_IDS_CONFIGURATION.sql script and change this option at all properties that were affected. NIIS Specific Installation Window a. Install Account Link Utility window(s) Select Next to install Do not change Virtual directory (NIIS/OXI/AccountLink) or Port (80) entries b. Install Enhanced Configuration Setup window Select Next to install Do not change Virtual directory (NIIS/OXI/EnhancedConfiguration) or Port (80) entries 3. Using Notepad, edit the Delphi.ini file located in NGS/INI; change PostedRevenue=on 4. Set permissions on \niis\mapfiles\micros_messagemapping.xml to Everyone change. 5. Open ProcessScript.xml in the DSI\MapFiles folder on the Delphi DB server and change the following entry as shown below: <priority value="1" filename="accountexport.js" recordstoprocess="100" /> to <priority value="1" filename="accountexport.sql" recordstoprocess="200" /> 6. Open Connectors.xml in the DSI\Configuration folder and change the <scripts> section with the following: 1-39

43 Micros OXI Upgrades <scripts> <script name= AccountExport.js priority= 1 recordstoprocess= 100 /> to <scripts> 7. <script name= AccountExport.sql priority= 1 recordstoprocess= 200 /> Global Server 1. Repeat step 1 on the Global server. 2. Disable the ProptoIS service on Delphi Global Server. Note If running in a linked environment, the ProptoIS service is disabled on the Global sever ONLY. a. Open Control Panel, Administrative Tools, Services b. Change the ProptoIS start-up type to Disable. c. Stop the ProptoIS service. 3. Open ProcessScript.xml in the DSI\MapFiles folder on the Delphi Global DB server and change the following entry as shown below: <priority value="1" filename="accountexport.js" recordstoprocess="100" /> to <priority value="1" filename="accountexport.sql" recordstoprocess="200" /> 4. Open Connectors.xml in the DSI\Configuration folder and change the <scripts> section with the following: <scripts> <script name= AccountExport.js priority= 1 recordstoprocess= 100 /> to Testing <scripts> <script name= AccountExport.sql priority= 1 recordstoprocess= 200 /> Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed. 1. Test URLs: Micros OXI Upgrades Address of I-Server>/NIIS/adminpanel - Verify the admin panel opens. name>/niis/oxi/accountlink/accountlinkpage.aspx - Verify the Account Link utility opens. name>/niis/oxi/service/messagereceptor.aspx - Verify you receive a Successful message, which ensures niis is installed properly. name>/niis/oxi/enhancedconfiguration/enhancedconfigurationpage.aspx - Verify the configuration utility opens. Note This section is for upgrading to Micros OXI version 1.1 only. If you are performing a new 1.1 installation, see Micros OXI New Installs, page

44 Micros OXI Upgrades Manual Steps Note If the connector is being installed in a linked environment, you must install on the Delphi and Global servers. Delphi Server 1. Stop the Polling and PropToIs services on the DSI server. 2. Stop the Multi-Threaded Export, and Same Inventory services on the I-Server. 3. Backup the delphi database: nss_database. 4. Backup the I-Server database: ni_isdb. 5. Run the Micros OXI 1.1 installer. Note If NIIS and DSI were installed on the same server, you only have to run the Micros OXI installer once. If NIIS and DSI are on separate servers, you must run the Micros OXI installer on each server. Install Micros OXI from the Micros OXI Installation CD/Setup.exe. Accept all installation defaults except as noted below. DSI Specific Installation Windows a. DB Server Login Info - enter the SQL administrator name, password, and the name of the Delphi database. b. Select the appropriate rule for each of the following. Please refer to the SOW for correct setting: Select rule for Account Production window- select all rates (default) Note The Pickup only option is to be used exclusively for Hilton OnQ sites. Select rule for Guest Room rates window- select Do not override Delphi rates (default)** Note If required, this setting will be adjusted per property by the on-site installer. Select rule for Account validation window- select Do not validate the account key (default) Note Do NOT select the Validate the account key option. Note **If the on-site installer changed this option from the default, and the Micros OXI connector has to be reinstalled at a later date, this option will be reset to the default by the installation program. The connector will not work as expected, so it is recommended that the connections be disabled by the person who is reinstalling the connector. This person will then need to run the OXI_RES_IDS_CONFIGURATION.sql script and change this option at all properties that were affected. NIIS Specific Installation Window a. Install Account Link Utility window(s) Select Next to install Do not change Virtual directory (NIIS/OXI/AccountLink) or Port (80) entries b. Install Enhanced Configuration Setup window Select Next to install Do not change Virtual directory (NIIS/OXI/EnhancedConfiguration) or Port (80) entries 6. Set permissions on \niis\mapfiles\micros_messagemapping.xml to Everyone change. 7. Open ProcessScript.xml in the DSI\MapFiles folder on the Delphi Global DB server and change the following entry as shown below: <priority value="1" filename="accountexport.js" recordstoprocess="100" /> to 1-41

45 Micros OXI Upgrades <priority value="1" filename="accountexport.sql" recordstoprocess="200" /> 8. Open Connectors.xml in the DSI\Configuration folder and change the <scripts> section with the following: <scripts> <script name= AccountExport.js priority= 1 recordstoprocess= 100 /> to <scripts> <script name= AccountExport.sql priority= 1 recordstoprocess= 200 /> Global Server 1. Repeat step 1 on the Global server. 2. Disable the ProptoIS service on Delphi Global Server. Note If running in a linked environment, the ProptoIS service is disabled on the Global sever ONLY. a. Open Control Panel, Administrative Tools, Services b. Change the ProptoIS start-up type to Disable. c. Stop the ProptoIS service. 3. Open ProcessScript.xml in the DSI\MapFiles folder on the Delphi Global DB server and change the following entry as shown below: <priority value="1" filename="accountexport.js" recordstoprocess="100" /> to <priority value="1" filename="accountexport.sql" recordstoprocess="200" /> 4. Open Connectors.xml in the DSI\Configuration folder and change the <scripts> section with the following: <scripts> <script name= AccountExport.js priority= 1 recordstoprocess= 100 /> to Testing <scripts> <script name= AccountExport.sql priority= 1 recordstoprocess= 200 /> Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed. 1. Test URLs: Address of I-Server>/NIIS/adminpanel - Verify the admin panel opens. name>/niis/oxi/accountlink/accountlinkpage.aspx - Verify the Account Link utility opens. name>/niis/oxi/service/messagereceptor.aspx - Verify you receive a Successful message, which ensures niis is installed properly. name>/niis/oxi/enhancedconfiguration/enhancedconfigurationpage.aspx - Verify the configuration utility opens. 2. Make sure the following services are running. 1-42

46 Opus TLP Connector DSI Server: ProptoIS & PollingService I-Server: Multi-Threaded Export & Stay Inventory 3. Create a test booking with one or two guestrooms attached. 4. Check the Statusqueue in the Status Msg Viewer of the Admin Panel. 5. Delete the test booking. Opus TLP Connector Manual Steps 1. Edit runonce.bat file. In the NGS/EXE directory, edit runonce.bat using Notepad by adding the following command at the bottom of the file. If runonce.bat doesn t exist, create it with the command identified below: Regedit s ISClientSettings.reg 2. On each terminal server, and Delphi workstation where Delphi is running, you must instruct the local IT contact to run runonce.bat when logged onto the workstation as an administrator. Runonce.bat is located on the drive that is mapped to the NGS directory (usually N:) in the \EXE\ folder. Note This enables the user to perform a revenue analysis. 3. Run booking queries a. Backup nss_database. b. On the Delphi database server, open query analyzer and login as SA. c. Run the following scripts against the nss_database database: //NIIS/DatabaseScripts/Add_Business_Roomnite_Triggers_Script.sql /NIIS/DatabaseScripts/Initial_Business_Roomnite_Dump.sql 4. Run final TLP Script This script creates output that the Opus 2 installer will require to complete the installation. The SQL file, InitialSetupQuery.sql, is located on: \\niftp\psg\download\iserver16\tlp_queries a. Create a folder on the Delphi server in the root of the NIIS directory named TLPSetValues. b. On the Delphi server, open query analyzer and login as SA. c. Under Query, click Results to File. d. Run the following script against the NSS_Database database: Tlp_queries.sql e. When the Save Results windows appears, save the results as /NIIS/TLPSetupValues/TLPSetupValues.TXT (be sure to enter the TXT extension) f. Notify the Newmarket Project Manager with the name of the file and location. Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed. Testing a New Install 1-43

47 Opus TLP Connector 1. Create a test connection a. Open the admin panel: Address of I-Server>/NIIS/adminpanel b. Login as nsa/nsa. c. From the Navigation menu, select Connection Manager. d. Click the New Connection button. e. The following windows appear. Change the information as identified below. f. In the Create New Connection window, enter the following:: Name: TEST TLP SERVICE Vendor: Select Opus 2 TLP Products: Opus 2 Services: TLP Service Properties: Select any property as a test (remember the property name) g. In the Connection Details window, enter the following: IP Address:IP Address of I-Server server h. Click the Test button. i. Click Ok. j. Select Yes for the Setup Mode. k. Select the Enable option. l. Click Next. m. Click Save New Connections. n. Click Ok. 2. Restart I-Server Services a. Open Control Panel, Administrative Tools, Services b. Stop the Multi-Threaded Export service (this stops the multi-threaded export, prestaging, and delegator services). c. Once the services have stopped, Start the Prestaging Service (this starts all three services). 3. Determine the test property PID a. On the Delphi database server, open query analyzer and login as SA. b. Run the following query against the nss_database database: Select pid, org_name from propertyview c. The query results list the properties in the database and their PID. Make note of the PID for the property you are testing with. 4. Run proc to move records to Table_Change a. On the Delphi database server, open query analyzer and login as SA. b. Run the following query against the nss_database database (where <PID#> is the test properties PID). This query can take at least 10 minutes to complete. Proc_initial_bus_rmnite_dump <PID#> 5. Verify records are moving from Delphi a. On the Delphi server, open query analyzer and login as SA. 1-44

48 Opus TLP Connector b. Run the following query against the nss_database database. You should have more than 0 records in the results. select count (*) from table_change where purge_record < 100 Represents the number of records passing from the table_change to TLP c. Run the query periodically. After approximately a minute you should see the number of records decreasing. You can then proceed to the next step. 6. Verify Records are entering TLPCOMM table Records pass from the Table_Change table in Delphi, to the OnDataChange Queue on the I-Server, and finally end up in the TLPCOMM table in NI_ISDB database on the I-Server database. a. On the I-Server server, open query analyzer and login as SA. b. Run the following query against the NI_ISDB database. Select count (*) from tlpcomm Represents the number of records passing from Delphi to the Tlpcomm table in TLP c. Run the query periodically to see the number of records increasing. Once they start increasing, you know the TLP connector is working correctly. 7. Check the status queue for errors a. Open the admin panel: Address of I-Server>/NIIS/adminpanel b. Login as nsa/nsa. c. From the Navigation menu, click Queue Manager, and select Status Queues. d. Click StatusQueue. e. Verify there are no messages in the status queue (only error messages are directed to this queue). If there any messages, click the message to view it. 8. Delete the test connection 1-45

49 Passkey Connector a. From the Navigation menu, select the Connection Manager. b. Click the TLP TEST CONNECTION. The Connection Details window appears. c. Click the Delete Connection button. d. Click OK to confirm. 9. Restart I-Server Services a. Stop the Multi-Threaded Export service. b. Once the services have stopped, Start the Prestaging Service. 10. Delete contents of Tables in NI_ISDB a. On the I-Server server, open query analyzer and login as SA. b. Run the following query against the NI_ISDB database. delete tlpcomm go delete tlpinfo go delete tlprate go delete tlpblock go Passkey Connector Process/Prerequisites During the SOW process the project manager should have provided all necessary Passkey configuration information for the property s production Passkey site. Before continuing with the installation, make sure all information for the configuration is available. If it is not, contact the project manager immediately to get the information. The property s Passkey production site must be available to complete the installation and validate that the connector is working. Manual Steps Note If NIIS and DSI were installed on the same server, you only have to run the Passkey installer once. If NIIS and DSI are on separate servers, you must run the Passkey installer on each server. 1. Install the Passkey connector from the Passkey Connector Installation CD by running Setup.exe. 2. Add HTTP/HTTPS calls through Proxy server. Note You do not need to add the HTTP/HTTPS calls unless the site is using a proxy server or requires authentication. If not needed, proceed to the next section, Configuring the Services for Passkey, page a. On the I-Server server, open SQL query analyzer b. Open the following script against the I-Server database (NI_ISDB). /NIIS/DatabaseScripts/ProxyConfiguration.sql c. Scroll to the following entries, and enter the appropriate information. Refer to the SOW: = ' ' = ' ' = ' ' 1-46

50 Passkey Connector = ' ' d. Execute the query. Configuring the Services for Passkey 1. You must configure the booking service for each property using Passkey. During this part of the install, you will send a test booking and monitor the message through the Admin Panel s export monitor. a. Open the admin panel: Address of I-Server>/NIIS/adminpanel b. Login as any Delphi user ( select * from users against NI_ISDB to get a list). c. From the Navigation menu, select Connection Manager. d. Click the New Connection button. Accept all installation defaults except as noted below. e. In the Create New Connection window, enter the following: Name: Passkey Vendor: Passkey Properties list: select one or more properties as applicable (Press Crtl key to multi-select) f. In the Booking Export Configuration window: Add housing methods descriptions as indicated in the SOW (enter the descriptions rather than the abbreviation). Set all other options as indicated in the SOW. If not specified, accept the defaults. The settings that are selected will be applied as defaults to all properties. Individual property setting can be changed later. g. In the Connection Details window (for first property selected), enter the following: Target Address: api.passkey.com (do not put or this is done automatically by I-Server). Add the above target address as a trusted site in Internet Explorer. Click the Test button. Ensure the test completes successfully. Partner ID: Refer to the SOW for the partner ID provided by Passkey. User Name: Refer to the SOW for the user name provided by Passkey. Password: Refer to the SOW for the password provided by Passkey. Setup Mode: No Enabled: Yes h. Click Configuration Options to change settings for this specific property, per the SOW or project manager. Otherwise click Next. This brings you to the Connection Details page for the next property you selected (if you selected more than one). Repeat the steps above for each property. i. When all properties are done, click Save Connections. j. Reenter the Connection Details page for each property, and retype the password. k. When all properties are done, click Save Connections. 2. Restart the I-Server Services a. Open Control Panel, Administrative Tools, Services b. Stop the Multi-Threaded Export service. c. Start the Prestaging service. Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed. 1-47

51 Property to Property v2.0 Validating/Monitoring Passkey Before completing the recap and giving it to support it is necessary to validate that the connector is installed correctly. This is only possible if the Passkey production site is available and you have completed all Connection Manager information. Once a booking is modified that meets the connection manager criteria a message is sent to Passkey. You can do this by creating a test booking that meets the connection manager criteria. While you create and save the test booking, you monitor the Export Monitor in the admin panel. 1. In the Admin Panel, open the Export Monitor. You will toggle back to the export monitor once your test booking has been saved. 2. Open Delphi and create a booking that meets the Connection Manager s Booking Export Configuration you configured according to the SOW. See step f on page a. For example, in Delphi, create a test booking under the Newmarket account. 1 Agreed room, 0 blocked rooms, 3 nights, status = definite, post as = Passkey Test, rate = $1.00, to next day. Enter a housing method that you specified in the Booking Export Configuration, per the SOW. 3. Save changes to the booking and quickly toggle back to the Export Monitor. Once the booking is saved, a message makes it s way from the Delphi database through I-Server to Passkey. This process can take up to 5 minutes. You should see the number of messages in the booking service connection change to zero as this occurs. The status column can also help you interpret what is happening to the message. If the status is green, it indicates that messages are being sent from I-Server to Passkey. After 10 minutes, if the message is not moving, the status turns yellow, after 2 hours, it turns red. 4. Once you see the message pass through the Export Monitor or after 5 minutes has passed, check to make sure there are no error messages in the Status Queue. a. If you see the following error, it indicates that Passkey security has denied the connection. Message Status: Transfer Type : 'NIDataExport' Priority : '1' Error : 'Could not export data to passkey webservice.' Reason : 'Node:'//*[name()='buildEventRS']//*[name()='Data']//*[name()='processRequest']// *[name()='return']/@code' could not be found in document. Function : CXML::GetAttributeValueFromPath() failed.' Layer : 'NIIS'. Component : 'ExportService_Passkey.Passkey' Detailed Description : 'Error retrieving the value of 'code' attribute.' b. As a first troubleshooting step, ensure the property connection details in the Admin Panel are correct. 5. Delete the test booking from Passkey. Logout of Passkey. Property to Property v2.0 Note If installing the P2P connector in a Terminal Server environment, please review CR30893 for information. Procedure 1, Verify Microsoft Reporting Services is installed If Microsoft Reporting Services is not installed, follow the steps below. Installation requires a reboot. Service accounts may need to be identified 1-48

52 Property to Property v2.0 SMTP server and user must be established 1. Ensure Microsoft Reporting Services has been obtained by the site. 2. Run the setup program. 3. Load the prerequisites (Windows Installer 2.0, MSRS Support files). 4. Visual Studio not installed (required for Report Designer), click Next. 5. On the Welcome screen click next. 6. On the Registration information screen click Next. 7. On the feature selection screen click Next to install the defaults (change the default installation path only if necessary. 8. On the service account screen click Next. 9. On the virtual directories screen click Next. 10. Report Sever database - leave as default and click Next. 11. Configure the SMTP server to point to a valid SMTP server on the network. 12. Select the appropriate licensing model and select the number appropriate for the model. 13. Click Install on the Ready to Install screen. Procedure 2, Install P2P v2.0 Connector You must install the P2P v2.0 connector on the I-Server and DSI server. 1. Using the P2P 2.0 Connector CD, select the Property to Property v 2.0 INSTALL link. Note Once you click OK, P2P is installed. You won t see any prompts as the installation takes place. If the installation web page does not automatically install, click autorun.htm on the CD. Procedure 3, Run the add business roomnite trigger script 1. On the I-Server, open Query Analyzer and run the Add_Business_Roomnite_Triggers_Script.sql file against the Nss_Database for all DSI servers. The query is located in the in the NIIS/DatabaseScripts folder. Procedure 4, P2P Lead Data Store Installation Important You must install I-Server 1.6 on the I-Server and all DSI servers before installing P2P v2.0 (reporting). This installation creates the data store for P2P reporting on the I-Server. 1. Using the P2P 2.0 Connector CD, select the Data Store INSTALL link. 2. In the Installation Type window, select the Production option. Note Do not select the Test Harness option (used by QA only). 1-49

53 Property to Property v In the Database Information window, enter the IP for the I-Server server, the P2P Database (defaults to NI_LDS), enter SA for the User ID, enter the SA password. Note You must leave the database at the default. 4. In the Database File Settings window, enter the location where Data Store should be installed, i.e. Y:\\Database\NI_LDS. Note Use the same drive where the NI_ISDB (core I-Server database) is located. 5. In the Event Log Settings window, enter the Event Log Name and application name, and click Next. Note The event log is created by the installation application and is used by the web service to log information. The entries defaults to NewmarketLDS and NewmarketLDSWS. 6. In the Select Installation Address window, choose the default. 7. In the Confirm Installation window, click Next. 8. In the Installation Complete window, click Close. Procedure 5, P2P LDS Data Reporting Installation This installation creates the reporting user interface. 1. Using the P2P 2.0 Connector CD, select the Reporting Engine INSTALL link. 2. In the Database Information window, enter the IP for the I-Server server, the P2P Database (defaults to NI_LDS), enter SA for the User ID, enter the SA password. Note You must leave the database at the default. 3. In the Application Settings window, enter the URLs for the following: Note Use the defaults and replace local host with the IP address. I-Server Authentication URL - the location of the I-Server server, i.e. Authentication.asmx?wsdl. Lead Data Storage Web Service URL - the location of the P2P database (on the P2P server), i.e. <localhost>/newmarket/ldsws/dataprocessor.asmx. Microsoft Reporting Web Service URL - the location of the P2P Reporting service, i.e. ReportServer. 4. Click Next and in the Confirm Installation window, click Next. 5. In the Installation Complete window, click Close. Procedure 6, Deploying Reports Once reports are created, they can be pushed to appropriate directory on the IIS server. Reports can be deployed by uploading the report s.rdl files. Each report is encapsulated in an RDL file. Deployment can be done manually via the Report Services Manager Web page or through the RSS web services. For this implementation use the manual process and upload the RDL files. Create Folder for deployment 1. From the server where SQL Reporting Services is installed, select Report Manager from the Start->All Programs- >Microsoft SQL Server->Reporting Services->Report Manager. This displays the Report Manager in a web administrator interface. 1-50

54 Property to Property v From the menu, select New Folder. Enter PPLR for the folder name, and provide a description. 3. Click OK. The new folder is now be displayed in the list of folders. Create a data source 1. Click to select the PPLR folder. 2. Ensure that you are in the PPLR directory. You can verify this by making sure the top left corner in the Report Manager displays: SQL Server Reporting Services Home > PPLR. 3. Click New Data Source. The New Data Source page opens. Type LDSWS for the item name. This is the data source name the reports use. You can also type a description to provide users with information about the connection. 4. For Connection Type, select Microsoft SQL Server. Type the following connection string which is used to connect to the SQL Server Newmarket database: data source=<ip Address>;initial catalog=ni_lds where <IP Address> is the SQL Server IP Address of the I-Server. 5. For Connect Using, select Credentials stored securely in the report server. Enter the SA user name and password. 6. Click OK. The shared Data Source is now available for use Uploading the reports 1. From the Report Manager page and PPLR folder, select the Upload File page to copy the.rdl files from the file system into the report server database. Uploaded files are represented as items in the report server folder hierarchy. The folder from which you initiate the upload operation is the folder that will contain the uploaded file. 2. Click Browse, and browse to the following location: C:\internetpub\wwwroot\newmarket\ldsreporter\reports 3. Select one of the following reports, and click Open. Leads Recd Leads Sent Monthly Summary Note Do not change the names of these reports. 4. Click Upload File on the Contents page. Note If the report already exists, overwrite it. 1-51

55 Property to Property v Click OK. 6. Repeat step 3 - step 5 for each report. Procedure 7, Create Leads and LDS Booking Connections 1. In the Admin Panel, create the following connections: 2. Create one Leads connection per data source. a. In the Create New Connection window, select the following: Vendor - Newmarket International Product - Lead Data Store Service - Leads Properties - All properties are grayed out since only one Leads connection is created for all properties in the data source. b. In the Connection Details, in the Target Address box, enter the IP Address of the enter the IP Address of the Report Database location (usually the IP address of the I-Server). Note You don t need to fill in Others, User Name, or Password. 3. Create one LDS Bookings connection per property. a. In the Create New Connection window, select the following: Vendor - Newmarket International Product - Lead Data Store Service - LDS Bookings Properties - Select all properties using Property to Property 2.0. b. In the Connection Details, in the Target Address box, enter the IP Address of the Report Database location (usually the IP address of the I-Server). Note You don t need to fill in Others, User Name, or Password. Procedure 8, Set Services to Automatic 1. Set the Prestaging and Delegator services to automatic Procedure 9, Backup the NI_LDS Database Create a maintenance wizard job to backup the NI_LDS database. In the SE recap, state that this database must be backed up nightly. Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed.. Testing P2P Connection 1-52

56 Property to Property v Log into Delphi and search for the Newmarket Test Account. Create one if it does not exist. In the Account Manager Screen from the View menu, point to Leads and click Send Leads. This opens the Web Lead Client window. 2. Populate the fields with asterisks if not already populated (for example, Meeting Name and Guestroom Rate). 3. Click the Search button at the bottom of the page. 4. When the property search window appears, search for and select a property name that you have identified for testing. 5. Once you have selected the property click Done. The property is now displayed on the Web Lead Client window in the Property selection area. 6. Click Send. The following message appears. 7. Click the Log Out button at the top of the Web Lead Client page. 8. Log back into the Delphi application and login as one of the following users: The user from the test property who is assigned the Direct Book role The sales manager for the Newmarket Test Account (if one exists) The following activity should now appear on the Scheduler. 9. Mark the activity as Done. Then turn down and delete the booking created by the lead. Reports The reports are available on line and can be quickly tested to ensure the reports are pointing properly to the data source. 1. Select each of the reports. Each of the reports can be opened independently via their respective URLs from Address of the I- Server>/Newmarket/LDSReporter The reports are now deployed and ready. 2. At the login screen, login using Delphi credentials. Note The Delphi user must be Sales Manager user or above. 1-53

57 Serenata NetHotel Connector Serenata NetHotel Connector Manual Steps Note If the connector is being installed in a linked environment, you must install on the Delphi and Global servers. Delphi Server 1. Using Notepad, edit the NGS/Delphi.ini file; change PostedRevenue=on 2. Add Serenata Triggers (to NSS_Database) a. On the I-Server server, open SQL query analyzer b. Connect to the Delphi server, and login as SA. c. Backup nss_database. d. Run the following scripts against the nss_database database: /NIIS/DatabaseScripts/AllAccountTriggers_v912.sql /NIIS/DatabaseScripts/Add_Business_Roomnite_Triggers_Script.sql 3. On each Delphi workstation where Delphi is running, you must instruct the local IT contact to run runonce.bat when logged onto the workstation as an administrator. Runonce.bat is located on the drive that is mapped to the NGS directory (usually N:) in the \EXE\ folder. Note This enables the ability to launch a Real-Time Availability update. 4. Run the Update_PMSINI_Table.sql query against nss_database to activate the Real Time Availability button in the Delphi application at a property. The query is located in the NIIS/DatabaseScripts folder. a. In the = xxxxx line, replace xxxxx with the property s PID. b. Run the query and repeat for each property that is enabled. 5. Open Delphi and click the PMS Guestroom Availability button in the GRC to confirm the Real Time Availability report opens. Note If the button is grayed out, click the GRC tab again. If this doesn t make the button active, click the To Do List tab, and then the GRC tab. This is a known issue which has been reported 6. Open ProcessScript.xml in the DSI\MapFiles folder on the Delphi DB server and change the following entry as shown below: <priority value="1" filename="accountexport.js" recordstoprocess="100" /> to 1-54

58 Starwood Meetings On Demand (SMD) <priority value="1" filename="accountexport.sql" recordstoprocess="200" /> 7. Open Connectors.xml in the DSI\Configuration folder and change the <scripts> section with the following: <scripts> <script name= AccountExport.js priority= 1 recordstoprocess= 100 /> to <scripts> <script name= AccountExport.sql priority= 1 recordstoprocess= 200 /> Global Server 8. Disable the ProptoIS service on Delphi Global Server. If running in a linked environment, the ProptoIS service is disabled on the Global sever ONLY. a. Open Control Panel, Administrative Tools, Services b. Change the ProptoIS start-up type to Disable. c. Stop the ProptoIS service. 9. Open ProcessScript.xml in the DSI\MapFiles folder on the Delphi Global DB server and change the following entry as shown below: <priority value="1" filename="accountexport.js" recordstoprocess="100" /> to <priority value="1" filename="accountexport.sql" recordstoprocess="200" /> 10. Open Connectors.xml in the DSI\Configuration folder and change the <scripts> section with the following: <scripts> <script name= AccountExport.js priority= 1 recordstoprocess= 100 /> to <scripts> <script name= AccountExport.sql priority= 1 recordstoprocess= 200 /> Testing Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed.. 1. Complete Appendix A Simulated Testing of Reservation Connectors, page A-1, for the NetHotel connector. Starwood Meetings On Demand (SMD) You must install the SMD Connector on the I-Server and DSI server. Note If NIIS and DSI were installed on the same server, you only have to run the SMD installer once. If NIIS and DSI are on separate servers, you must run the SMD installer on each server. 1. Verify the IP address Starwood wants information sent to: Install the SMD connector from the Meetings on Demand v1.0 Installation CD by running Setup.exe. 1-55

59 Starwood Meetings On Demand (SMD) 3. In the DB Server Login Info window, enter the sa password. Once this is done, records will start being saved in the table_change. These records will not be removed until the connector is successfully installed. 4. On the Delphi Server, open the Enterprise Manager. 5. Under Delphi Database Server/Management/SQL Server Agent/Jobs right-click NIIS_JOB_CREATE_SETUPVALUES_EXTRACT and select Start Job. The job creates a file, NI_SetupValuesExport.xml, located on the Delphi Server under \\DSI\MAPFILES\. This file contains the static setup data, which will be needed by SMD to receive the information. 6. Send the.xml file to Starwood. 7. In the Admin Panel, create the following Starwood SMD connections by property using the IP address verified in step 1. Note It is very important that the connection name reflects the service you are configuring. The text you enter in the Name box of the Create New Connection window gets appended to the properties you select in the Properties list. For example, if you are configuring the SMD Account Export service for NI Seacoast Park Hotel and you enter SMD Accounts in the Name box, when the connection is saved the connection's description is saved as NI Seacoast Park Hotel SMD Accounts. SMD FunctionRoomUsage Export SMD TGTPwMAR Export SMD InterfaceStatistics Export SMD Account Export SMD Booking Export 8. Run the following stored procs found on the Delphi database server: a. Procis_Initial_Account_Push b. Proc_initial_bus_rmnite_dump c. Procis_Initial_Function_Room_Push d. Procis_Initial_TGTPwMAR_Push 9. Access the Export Monitor in the Admin Panel to ensure messages are being sent. 10. Open ProcessScript.xml in the DSI\MapFiles folder on the Delphi DB server and change the following entry as shown below: <priority value="1" filename="accountexport.js" recordstoprocess="100" /> to <priority value="1" filename="accountexport.sql" recordstoprocess="200" /> 11. Open Connectors.xml in the DSI\Configuration folder and change the <scripts> section with the following: <scripts> <script name= AccountExport.js priority= 1 recordstoprocess= 100 /> to <scripts> <script name= AccountExport.sql priority= 1 recordstoprocess= 200 /> Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed

60 Starwood Meetings in a Moment (SMM) Starwood Meetings in a Moment (SMM) You must install the SMM Connector on the I-Server and DSI server. Note If NIIS and DSI were installed on the same server, you only have to run the SMM installer once. If NIIS and DSI are on separate servers, you must run the SMM installer on each server. 1. Install the SMM connector from the SMM v1.0 Installation CD by running Setup.exe. 2. In the DB Server Login Info window, enter the sa password. Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed.. SMS Host 1.0 Manual Steps Note If the connector is being installed in a linked environment, you must install on the Delphi and Global servers. Delphi Server 1. Backup the nss_database, and the NI_ISDB database if applicable. 2. Run the SMS Host 1.0 installer. Note If NIIS and DSI were installed on the same server, you only have to run the SMS Host installer once. If NIIS and DSI are on separate servers, you must run the SMS Host installer on each server. Install SMS Host 1.0 from the SMS Host 1.0 Installation CD/Setup.exe. Accept all installation defaults except as noted below. DSI Specific Installation Window a. DB Server Login Info - enter the SQL administrator name, password, and the name of the Delphi database. b. Select the Account Production Defaults option. Note Do NOT select the Pickup Only option (is for Hilton only). 1-57

61 SMS Host Using Notepad, edit the Delphi.ini file located in NGS/INI; change PostedRevenue=on 4. On the Delphi server only, add triggers (to NSS_Database) Note Add triggers to the Delphi server only. Do NOT add to Global. a. On the I-Server server, open SQL query analyzer b. Connect to the Delphi server, and login as SA. c. Run the following scripts against the nss_database database: DatabaseScripts/AllAccountTriggers_v912.sql DatabaseScripts/Add_Business_Roomnite_Triggers_Script.sql 5. On each Delphi workstation where Delphi is running, you must instruct the local IT contact to run runonce.bat when logged onto the workstation as an administrator. Runonce.bat is located on the drive that is mapped to the NGS directory (usually N:) in the \EXE\ folder. Note This enables the ability to launch a Real-Time Availability update. 6. Run the Update_PMSINI_Table.sql query against nss_database to activate the Real Time Availability button in the Delphi application at a property. The query is located in the NIIS/DatabaseScripts folder. a. In the = xxxxx line, replace xxxxx with the property s PID. b. Run the query and repeat for each property that is enabled. 7. Open Delphi and click the PMS Guestroom Availability button in the GRC to confirm the Real Time Availability report opens. Note If the button is grayed out, click the GRC tab again. If this doesn t make the button active, click the To Do List tab, and then the GRC tab. This is a known issue which has been reported Global Server 1. Repeat steps 1-2 on the Global server. 2. Disable the ProptoIS service on Delphi Global Server. Note If running in a linked environment, the ProptoIS service is disabled on the Global sever ONLY. a. Open Control Panel, Administrative Tools, Services b. Change the ProptoIS start-up type to Disable. c. Stop the ProptoIS service. 1-58

62 SMS Host 1.0 Testing Important. Run the Autopatch located on ftp:\\ \psg\download\iserver16 for the connector being installed.. Note If you install SMS Host on a system that already has the Galaxy connector installed, you must run the Galaxy hotfix for RTA. You must also install the Galaxy hotfix for RTA if you are installing Galaxy after SMS Host has been installed. 1. Test URL: Address of I-Server>/NIIS/adminpanel - Verify the admin panel opens. 1-59

63 Appendix A Appendix A Simulated Testing of Reservation Connectors Appendix A Appendix A Simulated Testing of Reservation Connectors 1. Create Test Connections on I-Server Serenata NetHotel or Galaxy Connections This procedure creates two test connections for a property. The test connections will then be visible form the Admin Panel s Connection manager (i.e. Newmarket Hotel TEST Account Service and Newmarket Hotel TEST Booking Service). a. On the I-Server server, open SQL query analyzer, and login as SA. b. Open /NIIS/DatabaseScripts/and run the following script: If testing Serenata NetHotel: TestServiceScripts.sql. If testing Galaxy: TestServiceScripts_Galaxy.sql c. Scroll down to the section outlined below. d. Edit the script by inputting the IP Address of the I-Server, and inputting the PID from one of the properties. e. Execute the query. 2. Restart Services and Change Recovery Settings on I-Server Server a. Open Control Panel, Administrative Tools, Services b. Stop the Multi-Threaded Export service (this stops the multi-threaded export, prestaging, and delegator services). c. Right-click on the service and select Properties. Select the Recovery tab. d. Change the setting as displayed below: A-1