145
PSE Hospitality Service Center Version 2.6 Service Manual

HSC Connect service manual

  • Upload
    hoangtu

  • View
    235

  • Download
    4

Embed Size (px)

Citation preview

Page 1: HSC Connect service manual

PSE

Hospitality Service Center

Version 2.6

Service Manual

Page 2: HSC Connect service manual

*1PA31003-E1325-S100-3-7620*

1P A31003-E1325-S100-3-7620

Copyright © PSE d.o.o., 05/2014Dolenjska cesta 318, SI-1291 Škofljica

Reference No.: PSE-

The information provided in this brochure contains merely general descriptions or characteristics of performance which in case of actual use do not always apply as described or which may change as a result of further development of the product. An obligation to provide the respective characteristics shall only exist if expressly agreed in the terms of contract. Availability and technical specifications are subject to change without notice.

Hicom, HiPath, OpenScape, Optiset E, optiPoint and OpenStage are registered trademarks of Unify GmbH & Co. KG.

Windows® is a registered trademark of Microsoft Corporation in the United States and other countries.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

Java® is registered trademarks of Oracle and/or its affiliates

All other company, brand, product and service names are trademarks or registered trademarks of their respective holders.

Page 3: HSC Connect service manual

PSE d.o.o. 2014Dolenjska cesta 318, SI-1291 Škofljica, SloveniaReference No.: A31003-E1325-S100-3-7620Subject to availability. Right of modification reserved.

*1PA31003-E1325-S100-3-7620*

1P A31003-E1325-S100-3-7620

Page 4: HSC Connect service manual

s_TOC-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 0-1

Nur für den internen Gebrauch Content

Content 0

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-5

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.1 Target Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.2 Structure of the Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21.3 Notational Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

2 Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.1 Hardware-Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1.1 HSC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.1.2 HSC-Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

2.2 Software-Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22.3 License Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

3 Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13.1 Short Description of Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13.2 Switch Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

3.2.1 HiPath 4000 - Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33.2.2 Multiple HiPath 4000 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53.2.3 HiPath 3000 / OpenScape Office / OpenScape Business. . . . . . . . . . . . . . . . . . . 3-93.2.4 Multiple HiPath 3000 / OpenScape Office / OpenScape Business configuration 3-103.2.5 SIP extensions for HSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

3.2.5.1 HiPath 3000 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-133.2.5.2 OpenScape Office LX/MX configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-173.2.5.3 OpenScape Business configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22

3.3 HSC Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-243.4 HSC Installation on Linux server or Linux HW appliance . . . . . . . . . . . . . . . . . . . . . 3-263.5 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-263.6 Hotel Reward . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28

3.6.1 Configuration of the Hotel Reward Export/Import Interface. . . . . . . . . . . . . . . . . 3-283.6.2 Format of the Hotel Reward Export/Import Interface Files . . . . . . . . . . . . . . . . . 3-28

3.7 Human Resource. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-303.7.1 Configuration of the Human Resource Interface. . . . . . . . . . . . . . . . . . . . . . . . . 3-303.7.2 Format of the Export Interface Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

3.8 E-Mail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-313.9 SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-313.10 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-323.11 Use of Kirk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

4 Upgrade and Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.1 Upgrade of HHSC V2.0 or V2.1 to HHSC V2.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1.1 Upgrade of V2.0, V2.1 Compact/Business . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Page 5: HSC Connect service manual

Content Nur für den internen Gebrauch

A31003-E1325-S100-3-7620, 01-20120-2 HSC V2.6, Service Manual

s_TOC-V26_en.fm

4.1.2 Upgrade procedure for HSC V2.0, V2.1 Professional (Short Description) . . . . . . . 4-14.1.3 Check unique keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.1.4 Run Backup on HHSC V2.0, V2.1 Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.1.5 Uninstall HHSC V2.0, V2.1 Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.1.6 Uninstall CLA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.1.7 Uninstall Crystal Reports Enterprise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.1.8 Upgrade of CAP to CAP SMR 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.1.9 Configure switch for Mute function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34.1.10 Upgrade Xpressions and Xpressions Connector on the Xpressions Server . . . . 4-34.1.11 Install HHSC V2.5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34.1.12 Install HHSC V2.5 License in CLA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34.1.13 Run Restore on HHSC V2.5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34.1.14 Configure HiPath Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44.1.15 Update customer specific interface plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44.1.16 Convert customer specific MIS reports from Crystal Reports to JasperReports . 4-44.1.17 Convert customer specific work order lists from Crystal Reports to JasperReports 4-

44.2 Upgrade of HHSC V2.5 to a new HSC V2.6 version. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

5 Client Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15.1 Installation of JRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.1.1 Disable automatical Java upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35.2 Settings in Case of Several JRE Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35.3 Client Start without Internet Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55.4 Problems at the Client Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

6 Using the HSC Maintenance Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.1 Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.2 User Interface Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6.2.1 Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.2.2 Main Desktop of HSC Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36.2.3 Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.2.4 Message Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

6.3 Showing the Interface Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-76.4 Defining and Activating Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

6.4.1 New Trace Window for Showing Current Trace Data. . . . . . . . . . . . . . . . . . . . . . . 6-96.4.1.1 Configure Trace to be Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

6.4.2 Trace Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-146.4.2.1 Add Trace Topic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-186.4.2.2 Edit Trace Topic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19

6.4.3 Structure of HSC-Specific Trace Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21

7 Mass Data - Import, Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17.1 Import of Mass Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17.2 Export of Mass Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

8 Configuration of NOEMI in HSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Page 6: HSC Connect service manual

s_TOC-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 0-3

Nur für den internen Gebrauch Content

8.1 NOEMI - Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18.1.1 HiPath 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38.1.2 Multiple HiPath 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-68.1.3 HiPath 3000 / OpenScape Office / OpenScape Business. . . . . . . . . . . . . . . . . . . 8-7

8.2 Activate VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12

A Appendix A - HiPath 4000 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1A.1 Example of a Configuration Batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1A.2 Settings for Call Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5A.3 Name Key Configuration for Service Tracking via Cordless Phone . . . . . . . . . . . . . . A-7A.4 Name Key Configuration for Service Tracking via OpenStage . . . . . . . . . . . . . . . . . . A-7

B Appendix B - Importing a New Graphical User Interface Language into HSC . . . . .B-1B.1 Localization of the HSC Graphical User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1B.2 Localization of Reports and Work Order Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

C Appendix C - Import of Mass Data by Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1C.1 HSC V2.6 MasterData-Interface Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1C.2 Description of sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

C.2.1 Sheet "Hotel" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4C.2.2 Sheet "Extension" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5

C.2.2.1 "Assistant Extensions" button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7C.2.2.2 "Assistant Rooms" button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9C.2.2.3 "Show/Hide CAP Entries" button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10

C.2.3 Sheet "Room Facility" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10C.2.4 Sheet "Emergency Call" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10C.2.5 Sheet "Department" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10C.2.6 Sheet "Service Type" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11C.2.7 Sheet "ServiceText" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11C.2.8 Sheet "Satisfaction Level". . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-12C.2.9 Sheet "Roles" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-12C.2.10 Sheet "Employees" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13C.2.11 Sheet "Direct Call" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15

List of Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Y-1

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Z-1

Page 7: HSC Connect service manual

Content Nur für den internen Gebrauch

A31003-E1325-S100-3-7620, 01-20120-4 HSC V2.6, Service Manual

s_TOC-V26_en.fm

Page 8: HSC Connect service manual

s_LOF-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 0-5

Nur für den internen Gebrauch List of Figures

List of Figures 0

Figure 2-1 HSC with Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Figure 3-1 Connection HiPath 4000 - CAP - HSC (Overview) . . . . . . . . . . . . . . . . . . 3-3Figure 3-2 Connection of multiple HiPath 4000 - HSC (Overview). . . . . . . . . . . . . . . 3-6Figure 3-3 Connection HiPath 3000 - HSC (Overview) . . . . . . . . . . . . . . . . . . . . . . . 3-9Figure 3-4 Connection of multiple HiPath 3000 - HSC (Overview). . . . . . . . . . . . . . 3-11Figure 3-5 HiPath 3000 SIP extension configuration 1. . . . . . . . . . . . . . . . . . . . . . . 3-13Figure 3-6 HiPath 3000 SIP extension configuration 2. . . . . . . . . . . . . . . . . . . . . . . 3-14Figure 3-7 HiPath 3000 SIP extension configuration 3. . . . . . . . . . . . . . . . . . . . . . . 3-14Figure 3-8 HiPath 3000 SIP extension configuration 4. . . . . . . . . . . . . . . . . . . . . . . 3-15Figure 3-9 HiPath 3000 SIP extension configuration 5. . . . . . . . . . . . . . . . . . . . . . . 3-16Figure 3-10 HiPath 3000 SIP extension configuration 6. . . . . . . . . . . . . . . . . . . . . . . 3-16Figure 3-11 OpenScape Office LX/MX SIP extension configuration 1 . . . . . . . . . . . . 3-17Figure 3-12 OpenScape Office LX/MX SIP extension configuration 2 . . . . . . . . . . . . 3-17Figure 3-13 OpenScape Office LX/MX SIP extension configuration 3 . . . . . . . . . . . . 3-18Figure 3-14 OpenScape Office LX/MX SIP extension configuration 4 . . . . . . . . . . . . 3-18Figure 3-15 OpenScape Office LX/MX SIP extension configuration 5 . . . . . . . . . . . . 3-19Figure 3-16 OpenScape Office LX/MX SIP extension configuration 6 . . . . . . . . . . . . 3-20Figure 3-17 OpenScape Office LX/MX SIP extension configuration 7 . . . . . . . . . . . . 3-20Figure 3-18 OpenScape Office LX/MX SIP extension configuration 8 . . . . . . . . . . . . 3-21Figure 3-19 OpenScape Office LX/MX SIP extension configuration 9 . . . . . . . . . . . . 3-21Figure 3-20 OpenScape Business SIP extension configuration 1 . . . . . . . . . . . . . . . 3-22Figure 3-21 HSC - Welcome Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24Figure 3-22 HSC - Choose Destination Location for HSC . . . . . . . . . . . . . . . . . . . . . 3-24Figure 3-23 HSC - Start Copying Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25Figure 3-24 HSC - Installation Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25Figure 3-25 HSC - Server Locking-ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26Figure 3-26 HSC - License details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27Figure 5-1 Java - License Agreement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Figure 5-2 Java JRE Setup Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Figure 5-3 Java Control Panel, Disabling Automatical Updates . . . . . . . . . . . . . . . . . 5-3Figure 5-4 Java - Setting of the Correct Version for HSC Start . . . . . . . . . . . . . . . . . 5-4Figure 5-5 Java Control Panel, Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Figure 5-6 Java Control Panel, Proxy Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Figure 6-1 Login Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Figure 6-2 Main Screen of HSC Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Figure 6-3 HSC Maintenance Menu Bar (with Displayed Menu) . . . . . . . . . . . . . . . . 6-4Figure 6-4 Menu Items in "Main" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4Figure 6-5 Menu Items in "Administration" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Figure 6-6 Menu Items in "Trace" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Figure 6-7 Menu Items in "Help". . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

Page 9: HSC Connect service manual

List of Figures Nur für den internen Gebrauch

A31003-E1325-S100-3-7620, 01-20120-6 HSC V2.6, Service Manual

s_LOF-V26_en.fm

Figure 6-8 About Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6Figure 6-9 Message Window Containing Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7Figure 6-10 HSC Maintenance - Interface Status Window . . . . . . . . . . . . . . . . . . . . . . 6-8Figure 6-11 Window for Showing Current Trace Data in Real Time . . . . . . . . . . . . . . 6-10Figure 6-12 Window for Configuring a New Trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12Figure 6-13 Trace Overview Window for Defining/Changing of Traces. . . . . . . . . . . . 6-15Figure 6-14 Window for Adding a New Trace Topic . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18Figure 6-15 Window for Editing Trace Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19Figure 7-1 Mass Data Import, Selection of an XML-file. . . . . . . . . . . . . . . . . . . . . . . . 7-2Figure 7-2 Mass Data Import, Options for Abortion . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Figure 7-3 Mass Data Import, Selection of Type of Data. . . . . . . . . . . . . . . . . . . . . . . 7-3Figure 7-4 Mass Data Import, Selection of Data Categories . . . . . . . . . . . . . . . . . . . . 7-4Figure 7-5 Mass Data Import, Indication of the Elements Currently Being Imported. . 7-5Figure 7-6 Mass Data Import, Logfile after Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6Figure 7-7 Mass Data Export, Selection of File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Figure 7-8 Mass Data Export, Selection of Type of Data. . . . . . . . . . . . . . . . . . . . . . . 7-8Figure 7-9 Mass Data Export, Selection of Data Categories . . . . . . . . . . . . . . . . . . . . 7-9Figure 7-10 Mass Data Export, Export Finished . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Figure 7-11 Mass Data Export, Logfile after Export. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11Figure 8-1 HSC Maintenance, NOEMI Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1Figure 8-2 HSC-Maintenance, Interface NOEMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2Figure 8-3 NOEMI, HiPath 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3Figure 8-4 NOEMI, Add COS/LCOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5Figure 8-5 NOEMI, Multiple HiPath 4000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Figure 8-6 Interfaces - NOEMI - HiPath 3000 / OpenScape Office Configuration . . . . 8-7Figure 8-7 Interfaces - NOEMI - Add or Configure new HiPath 3000 / OpenScape Office / OpenScape Business Connection 8-8Figure 8-8 Interfaces - NOEMI - COS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11Figure 8-9 Interfaces - NOEMI - Assignment of Extensions . . . . . . . . . . . . . . . . . . . 8-12Figure 8-10 Activate VoIP - Configuration Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12Figure 8-11 Activate VoIP - General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13Figure 8-12 Activate VoIP - SIP extension settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14

Page 10: HSC Connect service manual

s-chap1-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 1-1

Introduction

Target Group

1 Introduction

Hospitality Service Center (HSC) V2.6 is a client/server application intended for the hospitality industry. It combines communication features of the HiPath IP system with a hotel services application package that can interface with

● PMS (Hotel Property Management Systems)

● Call Accounting Systems

● Facility Monitoring

● VMS (Voice Mail Systems)

● etc.

HSC V2.6 optimizes telephony at the hotel workstation and makes use of the integration capabilities offered by central data resources. It offers various hospitality industry features:

● service tracking

● call control center

● customer relationship management

The range of functions can be adapted to customer requirements and conditions of use by acquiring different licenses.

1.1 Target Group

HSC is intended for medium to large hotels as well as for hotel chains. It supports the Front Office Client, Tablets or laptop consoles for guests and Tablet devices for hotel staff members. Hotel staff can also use a CMI (Cordless Multicell Integration) or an OpenStage telephone instead of a Tablet device.

It is the purpose of this manual to offer support for service engineers and to provide

> information on HSC-specific settings that have to be made for 3rd-party products, such as HiPath 3000/4000, etc., communicating with HSC and

> information on the installation and configuration of HSC itself.

The service engineers responsible for installation must be experienced in the use of Microsoft Windows products and also have well-founded knowledge with regard to installation and configuration of the PBXs HiPath 3000, HiPath 4000, OpenScape Office, OpenScape

Page 11: HSC Connect service manual

Introduction

A31003-E1325-S100-3-7620, 01-20121-2 HSC V2.6, Service Manual

s-chap1-V26_en.fm

Structure of the Manual

Business, OpenScape Voice. Depending on the equipment of the customer system, also installation experience with regard to software components, such as Java, further Voice Mail Systems, etc. will be a benefit.

1.2 Structure of the Manual

The manual consists of the following chapters and appendices:

Chapter 1 - Introduction provides an overview of HSC and the likely users of the Service Manual.

Chapter 2 - Hardware and Software Requirements specifies the hardware and software required for using HSC and describes the available licenses.

Chapter 3 - Installation and Configuration explains the installation of HSC software and additionally required software products (e.g. Java).

Chapter 4 - Upgrade and Migration on the one hand explains the upgrade of Siemens HHSC V2.0/V2.1/V2.5 to HSC V2.6 and, on the other hand, the migration to more current HSC V2.6 intermediate versions (incl. backup & restore).

Chapter 5 - Client Start offers supports for soling problems that may occur upon the start of a HSC client. It offers informationen about the handling with Java.

Chapter 6 - Using the HSC Maintenance Tool explains how to work with the graphical user interface of HSC Maintenance, it offers a general overview of functions and describes the central functioning of the program i.e. how you can create and archive trace information and/or log files for error analysis and recovery.

The Chapters 7 and 8 - Settings via HSC Maintenance describe in detail further functions that can be executed by means of HSC Maintenance. Import and export of mass data as well as configuration of the NOEMI interface to switches.

Appendix A - HiPath 4000 Configuration describes the configuration of a HiPath/OpenScape 4000 switch based on examples (configuration batch) and notes.

Appendix B - Importing a New Graphical User Interface Language into HSC provides information how Professional Services can implement an additional GUI language for HSC.

Appendix C - Import of Mass Data by Tool supports you when first processing your hotel-specific data.

The Index is a tool which provides fast access to detailed information on a given topic.

Page 12: HSC Connect service manual

s-chap1-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 1-3

Introduction

Notational Conventions

1.3 Notational Conventions

● In the text, screen elements are displayed in italics.

● Important information in the text is highlighted in bold.

● The keys of your keyboard are displayed in italics, in angle brackets (e.g. <Alt>).

● The > sign describes paths through menu items you have to select to reach a certain feature.

> With this symbol notes are indicated.

7 With this symbol warnings are indicated.

Page 13: HSC Connect service manual

Introduction

A31003-E1325-S100-3-7620, 01-20121-4 HSC V2.6, Service Manual

s-chap1-V26_en.fm

Notational Conventions

Page 14: HSC Connect service manual

s-chap2-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 2-1

Hardware and Software Requirements

Hardware-Requirements

2 Hardware and Software Requirements

In this chapter you find the hardware and software requirements for HSC V2.6. The licenses are pointed out in Section 2.3.

The installation and configuration of your HSC system and other required software components are specified in Chapter 3, “Installation and Configuration”

Figure 2-1 HSC with Components

2.1 Hardware-Requirements

2.1.1 HSC Server

Processor (x86); 2,8 GHz min.

RAM 4 GB min.

Hard disk 80 GB min.RAID 1 or RAID 5 recommended

Table 2-1 Hard- and Software Requirements for HSC

Page 15: HSC Connect service manual

Hardware and Software Requirements

A31003-E1325-S100-3-7620, 01-20122-2 HSC V2.6, Service Manual

s-chap2-V26_en.fm

Software-Requirements

2.1.2 HSC-Client

Table 2-2 Hard- and Software Requirements for HSC Client

2.2 Software-Requirements

The following components are installed "automatically" in the course of HSC installation:

Operating system Windows 7 or newer, Windows 2008 Server or newer (server platform recommended)

Network card 2 (1 customer-LAN, 1 HiPath-LAN)

Operating time 24 hours a day

Processor Pentium 4; 2,66 GHz min.

RAM 1 GB

Hard disk 80 GB

Operating system Windows 7, Windows 8

Component Description Version

HSC V2.6 HSC-Server-Application 2.6

PostgreSQL PostgreSQL-Database 8.3

Apache Tomcat Tomcat Servlet Container 5.5

Apache Axis SOAP implementation 1.4

JRE Java Runtime Environment 1.6

Jasper Reports Reporting Service 1.2

Nagios HSC Watchdog 2.0

Cygwin Unix-like environment for Windows 1.5.17

Table 2-3 Automatically installed components

Table 2-1 Hard- and Software Requirements for HSC

Page 16: HSC Connect service manual

s-chap2-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 2-3

Hardware and Software Requirements

License Variants

2.3 License Variants

HSC V2.6 tries to meet different customer requirements by providing a system that caters to the individual needs. HSC comes in a basic variant ("Basic Package" license) comprising the Call Control Center and basic management functions and which can be complemented by additional licenses with additional functions or interfaces to other systems. HSC V2.6 is designed for larger hotels using PMS systems (Property Management Systems) of other vendors.

Your HSC menu depends on the licenses you have acquired, i.e. you can use all functions that you see on your screen (functions and menus of licenses that you have not acquired, are hidden).

For more detailed information please visit our homepage www.pse-pk.com/en/hospitality.

>If Adobe Acrobat Reader is not available on the client PC, it can be installed from the HSC installation CD. (Install this system on C: or D:, otherwise some launches will not be functioning! (Also avoid installation paths using folder names which contain blanks, e.g. do not install Adobe Acrobat Reader in the folder "Program Files"!)

Page 17: HSC Connect service manual

Hardware and Software Requirements

A31003-E1325-S100-3-7620, 01-20122-4 HSC V2.6, Service Manual

s-chap2-V26_en.fm

License Variants

Page 18: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-1

Installation and Configuration

Short Description of Installation

3 Installation and Configuration

This chapter describes the installation and configuration of HSC server: in Section 3.1 as short description, a detailed specification you find in chapter 3.2 to 3.15.

Exact installation instructions exist only for those components that are prerequisites for running HSC. In all other cases we should like to refer you to the original documentation with regard to installation. For specific configurations required for HSC please see the following chapters. For information on additional components, such as PMS; VMS, etc., see Administration Manual, chapter 8 (interfaces) and the original documentation of the systems.

3.1 Short Description of Installation

The short description for the installation includes a recommendation for a certain order. Each component is specified in the subsequent chapters.

Perform the installation steps in the order described below:

1. Configure switch (HiPath 3000/4000, OpenScape Office/Business/Voice, ) (see Section 3.2, “Switch Configuration”")

2. Install HSC V2.6 (see Section 3.3, “HSC Installation”)

3. Activate HSC license(s) (see Section 3.5, “Licensing”)

4. Optional: Installation of third-party systems like PMS, VMS, SCAI, etc. See the original documentation of each system!

5. Activate HSC V2.6 (click Start > Settings > Control Panel > Administrative Tools > Services), if it hasn’t started automatically

Wait a few minutes for the application to start.

Then you can start the HSC graphical user interface by enteringhttp://<servername>:8270into the browser's navigation bar and clicking on Front Office Client.

6. Configure HSC V2.6 (i.e. fill the database with data using the HSC administration functions):

>The installation and configuration of your HSC system and other required software components have to be performed by an installation expert (usually a certified service engineer). Knowledge of installation and configuration of HiPath PBXis required.

Page 19: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-2 HSC V2.6, Service Manual

s-chap3-V26_en.fm

Short Description of Installation

● Make individual entries into the HSC database using the HSC administration graphical user interface (see Administration Manual, Chapter 3 to Chapter 7)

● Import of a charge rate file if used (see Administration Manual, Chapter 8.3)

● Import of mass data (master data and configuration data) (see Section 7.1)

● Interfaces to additional components like PMS, VMS, etc. are to be configured in HSC(see Administration Manual, Chapter 8)

> Please restart your server PC after finishing the installation and configuration!

> For backing up data and upgrading from Siemens HHSC, see Chapter 4, “Upgrade and Migration”.

Page 20: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-3

Installation and Configuration

Switch Configuration

3.2 Switch Configuration

HSC is specifically designed for switches HiPath 3000/4000, OpenScape Office/Business/Voice from Unify. The HSC functionalities have been developed based on HiPath/OpenScape functionalities. HSC is designed as an expansion of switch functionality for hotel requirements.

HSC and HiPath are communicating on two levels:

● Call Accounting - see Administration Manual, Section 8.3

● Authorization changeover, name registration and display language at CheckIn and Check-Out on end devices (by means of AMOS), see Section 8.1

First of all, the switch used in your hotel has to be configured to comply with HSC requirements.

3.2.1 HiPath 4000 - Configuration

At HiPath 4000 third level (authorization switchover, display language and name registration at CheckIn and Check-Out on end devices) is implemented by using the FAMOS protocol. This protocol makes it possible to transmit AMOs from a remote location to change extension pro-perties.

Figure 3-1 offers an overview of the HSC server and all related components to integrate with a HiPath 4000 switch.

You can see the different components interacting with each other. For a proper functionality of HSC all the links (in the figure labeled with port numbers) need to be configured correctly.

Figure 3-1 Connection HiPath 4000 - CAP - HSC (Overview)

It is important for HSC to configure the items below in the switch:

Page 21: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-4 HSC V2.6, Service Manual

s-chap3-V26_en.fm

Switch Configuration

● Creation of extensions:See HiPath 4000 Original documentation

● Switch configuration for "virtual stations": For 2 features virtual stations are required:

– Wakeup calls, if no voice mail system is available

– Service Tracking for sending of service requests to the end devices (CMI or OpenStage)

The number of virtual stations depends on the number of simultaneous wakeup calls and/or service requests to be expected (5 per feature are recommended as a minimum).Example for the configuration of a wakeup call:ADD-SCSU:STNO=2041,DVCFIG=AUXDIGI,DPLN=0,ITR=0,COS1=12,COS2=12,LCOSV1=9,LCOSV2=1,LCOSD1=9,LCOSD2=1,INS=ACLSTN,SSTNO=NO;

● CDR link:A sample AMO batch for the configuration of a Call Accounting link from HiPath 4000 to HSC ’configuration batch HiPath4000 en.txt ’is provided on the HSC CD under \Tools. This configuration batch with comments can also be found in Appendix A.

● FAMOS-LinkYou can find the activating of FAMOS-Link in the configuration batch ’configuration batch HiPath4000 en.txt’ on the HSC installation CD under \Tools as well as in Appendix A.

● RCG set-up for Call-Queue-Handling or if a third party call center is usedSee original HiPath 4000 documentation and Appendix A.

● Key for operating Service Tracking on OpenStage and CMI:

ADD-ZIEL:NAME,<Tln#>,<Key#>,C15C13<AppId><Shortcut>,,,YES;

<Tln#> = extension<Key#> with OpenStage this can be any number, with CMI only 9 and 11 may be used<AppId> = Default 900<Shortcut>: 5, 53 or 55 (with ’5’ the main menu of Service Tracking is displayed when pushing the adequate key, with ’53’ you directly navigate to changing of the status of presence, with ’55’ you directly navigate to the list of open service requests)

Recommendation for CMI: for key 9 you should configure shortcut ’53’ for changing the status of presence (reachable at INT + DTB); for key 11 you should configure either shortcut ’5’ for the main menu or shortcut ’55’ for the list of open service requests (reachable under envelope icon + DTB) (see also Appendix A.3, “Name Key Configuration for Service Tracking via Cordless Phone”)Recommendation for OpenStage: the key number, where shortcut ’5’ for the main menu or shortcut ’55’ for the list of open service requests is assigned, must correspond with the LED number configured via HSC administration (see also Appendix A.4, “Name Key Configuration for Service Tracking via OpenStage”)

Page 22: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-5

Installation and Configuration

Switch Configuration

● Key for entering of wakeup call, room status, minibar and Service Tracking (when Xpres-sions is used):

ADD-ZIEL:NAME,<Tln#>,<Key#>,<Xpressions access><Feature access number>,BD;

<Tln#> = extension<Key#> with OpenStage this can be any number, with CMI 9 or 11 (9 is reachable under INT + DTB, 11 is reachable under envelope icon + DTB)<Xpressions access> = dial-in to Xpressions (= 930) <Feature access number> = 50 or 51 (for wakeup call ’50’, for service menu -> room status, minibar, Service Tracking ’51’)

● Key for text and voice-mail messages, if no VMS is used

ADD-ZIEL:NAME,<Tln#>,<Key#>,<Target>,BD;

<Tln#> = extension<Key#> with OpenStage this can be any number, with CMI 0 or 9 <Target> = extension to which the guest is connected when pushing the adequate buttonSee Administration Manual, Section 8.2.1)

● Dial-in option for entering wakeup call, room status, minibar via analog telephone if no VMS is used

ADD-WABE:CD=*74,DAR=DIGIDAT,CHECK=N;

● Deactivate the second call directly at the PBX. Otherwise the second-call function has to be deactivated at the Front Office extensions.

● Do not configure the extensions of the Front Office as secret station number!

Additional documents:

In Appendix A you will find a configuration batch for HiPath 4000 with comments as well as an instruction for setting up of RCGs. You will also find a HiPath 4000 configuration example for the configuration of name keys for CMI and OpenStage.

You will find the set-up batch for HiPath 4000 on the HSC installation CD under \Tools’configuration batch HiPath4000 en.txt ’.

3.2.2 Multiple HiPath 4000 configuration

At HiPath 4000 third level (authorization switchover, display language and name registration at CheckIn and CheckOut) is implemented by using the FAMOS protocol. This protocol makes it possible to send AMOs from a remote location for changing extension properties. If multiple HiPath 4000 systems are connected with the HSC server, a poll is made via an AMO at start-up to find out which extension is configured on which HiPath.

Page 23: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-6 HSC V2.6, Service Manual

s-chap3-V26_en.fm

Switch Configuration

Bild Figure 3-2 offers an overview of the HSC server and all related components to integrate with several HiPath 4000 switches. You can see the different components interacting with each other.For a proper functionality of HSC all the links (in the figure labeled with port numbers) need to be configured correctly.

Figure 3-2 Connection of multiple HiPath 4000 - HSC (Overview)

For HSC it is important to configure the following items in each switch individually (except for virtual stations, as all of them can be set up in one HiPath system):

● Configure extensions clearly (i.e. an extension number must only be assigned once!)See original documentation of HiPath 4000

● Switch configuration for "virtual stations": For 2 features virtual stations are required:

– Wakeup calls, if no voice mail system is available

– Service Tracking for sending of service requests to the end devices (CMI or OpenStage)

Page 24: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-7

Installation and Configuration

Switch Configuration

The number of virtual stations depends on the number of simultaneous wakeup calls and/or service requests to be expected (5 per feature are recommended as a minimum).Example for the configuration of a wakeup call:ADD-SCSU:STNO=2041,DVCFIG=AUXDIGI,DPLN=0,ITR=0,COS1=12,COS2=12,LCOSV1=9,LCOSV2=1,LCOSD1=9,LCOSD2=1,INS=ACLSTN,SSTNO=NO;

● CDR link:A sample AMO batch for the configuration of a Call Accounting link from HiPath 4000 to HSC ’configuration batch HiPath4000 en.txt ’is provided on the HSC CD under \Tools. This configuration batch with comments can also be found in Appendix A.

● FAMOS-LinkYou can find the activating of FAMOS-Link in the configuration batch ’configuration batch HiPath4000 en.txt’ on the HSC installation CD under \Tools as well as in Appendix A.

● RCG set-up for Call-Queue-Handling or if a third party call center is usedSee original HiPath 4000 documentation and Appendix A.

● Key for operating Service Tracking on OpenStage and CMI:

ADD-ZIEL:NAME,<Tln#>,<Key#>,C15C13<AppId><Shortcut>,,,YES;

<Tln#> = extension<Key#> with OpenStage this can be any number, with CMI only 9 and 11 may be used<AppId> = Default 900<Shortcut>: 5, 53 or 55 (with ’5’ the main menu of Service Tracking is displayed when pushing the adequate key, with ’53’ you directly navigate to changing of the status of presence, with ’55’ you directly navigate to the list of open service requests)

Recommendation for CMI: for key 9 you should configure shortcut ’53’ for changing the status of presence (reachable at INT + DTB); for key 11 you should configure either shortcut ’5’ for the main menu or shortcut ’55’ for the list of open service requests (reachable under envelope icon + DTB) (see also Appendix A.3, “Name Key Configuration for Service Tracking via Cordless Phone”)Recommendation for OpenStage: the key number, where shortcut ’5’ for the main menu or shortcut ’55’ for the list of open service requests is assigned, must correspond with the LED number configured via HSC administration (see also Appendix A.4, “Name Key Configuration for Service Tracking via OpenStage”)

● Key for entering of wakeup call, room status, minibar and Service Tracking (when Xpres-sions is used):

ADD-ZIEL:NAME,<Tln#>,<Key#>,<Xpressions access><Feature access number>,BD;

<Tln#> = extension<Key#> with OpenStage this can be any number, with CMI 9 or 11 (9 is reachable under INT + DTB, 11 is reachable under envelope icon + DTB)

Page 25: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-8 HSC V2.6, Service Manual

s-chap3-V26_en.fm

Switch Configuration

<Xpressions access> = dial-in to Xpressions (= 930) <Feature access number> = 50 or 51 (for wakeup call ’50’, for service menu -> room status, minibar, Service Tracking ’51’)

● Key for text and voice-mail messages, if no VMS is used

ADD-ZIEL:NAME,<Tln#>,<Key#>,<Target>,BD;

<Tln#> = extension<Key#> with OpenStage this can be any number, with CMI 0 or 9 <Target> = extension to which the guest is connected when pushing the adequate buttonSee Administration Manual, Section 8.2.1)

● Dial-in option for entering wakeup call, room status, minibar via analog telephone if no VMS is used

ADD-WABE:CD=*74,DAR=DIGIDAT,CHECK=N;

● Deactivate the second call directly at the PBX. Otherwise the second-call function has to be deactivated at the Front Office extensions.

● Do not configure the extensions of the Front Office as secret station number!

Additional documents:

In Appendix A you will find a configuration batch for HiPath 4000 with comments as well as an instruction for setting up of RCGs. You will also find a HiPath 4000 configuration example for the configuration of name keys for CMI and OpenStage.

You will find the set-up batch for HiPath 4000 on the HSC installation CD under \Tools’configuration batch HiPath4000 en.txt ’.

Page 26: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-9

Installation and Configuration

Switch Configuration

3.2.3 HiPath 3000 / OpenScape Office / OpenScape Business

Figure 3-3 offers an overview of the HSC server and all related components to integrate with a HiPath 3000 / OpenScape Office / OpenScape Business switch.

You can see the different components interacting with each other. For a proper functionality of HSC all the links (in the figure labeled with port numbers) need to be configured correctly.

Figure 3-3 Connection HiPath 3000 - HSC (Overview)

It is important for HSC to configure the items below in the switch: :

● Switch configuration for CAP and Service Tracking:No special settings are required!

The description of the export of the extensions from HiPath for the import in CAP you find in HiPath documentation.

● Switch configuration for "virtual stations": For wakeup calls that are performed without a voice mail system, virtual stations have to be configured in the switch (set the checkbox to "Virtual station" at the stationview by means of HiPath 3000 manager or OpenScape Assistant").The number of virtual extensions depends on the number of simultaneous wakeup calls to be expected (5 are recommended as a minimum).

● Entry of wakeup call (without voice prompt, using the internal “Basic Wakeup Call System”) and room status via room telephone for HiPath 3000 and OpenScape Business (not avail-able for OpenScape Office):If room telephones are used, the parameter Data I/O in HiPath 3000 V6 -V9 has to be set

Page 27: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-10 HSC V2.6, Service Manual

s-chap3-V26_en.fm

Switch Configuration

to "*494" (HiPath 3000 Manager > Settings > System parameters > Service codes, Open-Scape Business Assistant -> Expert mode -> Basic Settings -> System -> Service Codes, codes) and in HiPath 3000 V5 and OpenScape Business to "*42" (OpenScape Business Assistant -> Expert mode -> Basic Settings -> System -> Service Codes -> Telephone Data Service (TDS)).

● Entering of wakeup call, minibar, room status and service tracking (only when using Inter-nal Advanced Messaging system or external voicemail)

Open the menu item 'Key programming' in the HiPath 3000 Manager via Systemview > Settings > Set up station.Activate the radio button 'Key programming' (on the right side above), select the respective extension and key. As a key code select 'Repdial key', then 'external' and state the access number for Internal Advanced Mesaging System. Finally click 'OK' (red check) and 'Apply'.

● Deactivate the second call directly at the PBX. Otherwise the second-call function has to be deactivated at the Front Office extensions.

● Do not configure the extensions of the Front Office as secret station number!

● Additional configurations:To make sure that the selected trunk line number is included in the charge data, LCR has to be activated in the Automatic Routing function.For "output of charges" the output port shall be left on "none".Authorization group 2 is used for check out and authorization has to be set to "semi-restricted" or similar.Authorization group 7 is used for check in and authorization has to be set to "authorized for incoming and outgoing calls" or similar.

3.2.4 Multiple HiPath 3000 / OpenScape Office / OpenScape Business configuration

If multiple HiPath 3000 / OpenScape Office / OpenScape Business systems are connected with the HSC server all extensions have to be clearly assigned to one of the switches.

Figure 3-4 offers an overview of the HSC server and all related components to integrate with several switches. You can see the different components interacting with each other.For a proper functionality of HSC all the links (in the figure labeled with port numbers) need to be configured correctly.

Page 28: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-11

Installation and Configuration

Switch Configuration

Figure 3-4 Connection of multiple HiPath 3000 - HSC (Overview)

For HSC it is important to configure the following items in each switch individually:

● Configure extensions clearly (i.e. an extension number must only be assigned once!)See original documentation of HiPath 3000 / OpenScape Office / OpenScape Business

● Switch configuration for "virtual stations": For wakeup calls that are performed without a voice mail system, virtual stations have to be configured in the switch (set the checkbox to "Virtual station" at the stationview by means of HiPath 3000 manager").The number of virtual extensions depends on the number of simultaneous wakeup calls to be expected (5 are recommended as a minimum).

● Entering of wakeup call, minibar, room status via analog telephone (without voice prompts)If analog telephones are used without Xpressions, the parameter data I/O has to be set to "*494" for HiPath 3000 V6 or newer (HiPath 3000 Manager > Settings > System parame-ters > Service codes) and to "*42" for OpenScape Business (OpenScape Business Assis-tant -> Expert mode -> Basic Settings -> System -> Service Codes -> Telephone Data Ser-vice (TDS)).

● Deactivate the second call directly at the PBX. Otherwise the second-call function has to be deactivated at the Front Office extensions.

Page 29: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-12 HSC V2.6, Service Manual

s-chap3-V26_en.fm

Switch Configuration

● Do not configure the extensions of the Front Office as secret station number!

● Additional configurations:To make sure that the selected trunk line number is included in the charge data, LCR has to be activated in the Automatic Routing function.For "output of charges" the output port shall be left on "none".Authorization group 2 is used for check out and authorization has to be set to "semi-restricted" or similar.Authorization group 7 is used for check in and authorization has to be set to "authorized for incoming and outgoing calls" or similar.

3.2.5 SIP extensions for HSC

HSC Entry requires SIP subscribers for Advanced Internal Call System. Advanced Internal Call System is used for:

● Wakeup call

● Room status

● Minibar posting

● Hotel voicemail

Please configure your switch as shown on screenshots.

Please remember your entries, since you will have to enter these data in HSC later on.

Page 30: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-13

Installation and Configuration

Switch Configuration

3.2.5.1 HiPath 3000 configuration

Figure 3-5 HiPath 3000 SIP extension configuration 1

Before establishing or receiving calls an endpoint MUST register at the system. The system expects the configured call number for registration. For security reasons it is strongly recommended to use Authentication. For each extension a name can be configured in the system. The number and name is presented during call establishment if no restriction is activated (Recomendded naming is Wakeup and Voice mail). At least 2 extensions are recomendded for wakeup functionality.

Page 31: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-14 HSC V2.6, Service Manual

s-chap3-V26_en.fm

Switch Configuration

Figure 3-6 HiPath 3000 SIP extension configuration 2

Figure 3-7 HiPath 3000 SIP extension configuration 3

Entry in telephone directory flag must be disabled.

Page 32: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-15

Installation and Configuration

Switch Configuration

Figure 3-8 HiPath 3000 SIP extension configuration 4

With the increasing deployment of VoIP networks more and more attacks against VoIP equipment can be observed in such networks. SIP as an open and well-known protocol is implemented in various crack tools which are freely available in the internet. To avoid misuse of a SIP access careful configuration is crucial.

For a SIP subscriber access the following rules should be followed:

● Activate authentication

● Use a non trivial password with

a minimum of 8 and a maximum of 20 characters

● at least one upper case letter. (A - Z)

● at least one lower case letter. (a - z)

● at least one number. (0 - 9)

● at least one special character

● no more than 3 repeated characters

Define a SIP user ID different from the Callno

Page 33: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-16 HSC V2.6, Service Manual

s-chap3-V26_en.fm

Switch Configuration

Figure 3-9 HiPath 3000 SIP extension configuration 5

Figure 3-10 HiPath 3000 SIP extension configuration 6

It is recommended to set two hunting groups one for access to the wakeup system and another for the hotel specific voicemail system.

Page 34: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-17

Installation and Configuration

Switch Configuration

3.2.5.2 OpenScape Office LX/MX configuration

Figure 3-11 OpenScape Office LX/MX SIP extension configuration 1

Figure 3-12 OpenScape Office LX/MX SIP extension configuration 2

Before establishing or receiving calls an endpoint MUST register at the system. The system expects the configured call number for registration. For security reasons it is strongly recommended to use Authentication. For each extension a name can be configured in the system. The number and name is presented during call establishment if no restriction is activated (Recomendded naming is Wakeup and Voice mail). At least 2 extensions are recomendded for wakeup functionality.

Page 35: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-18 HSC V2.6, Service Manual

s-chap3-V26_en.fm

Switch Configuration

Figure 3-13 OpenScape Office LX/MX SIP extension configuration 3

Figure 3-14 OpenScape Office LX/MX SIP extension configuration 4

Entry in telephone directory flag must be disabled.

Page 36: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-19

Installation and Configuration

Switch Configuration

Figure 3-15 OpenScape Office LX/MX SIP extension configuration 5

With the increasing deployment of VoIP networks more and more attacks against VoIP equipment can be observed in such networks. SIP as an open and well-known protocol is implemented in various crack tools which are freely available in the internet. To avoid misuse of a SIP access careful configuration is crucial.

For a SIP subscriber access the following rules should be followed:

● Activate authentication

● Use a non trivial password with

a minimum of 8 and a maximum of 20 characters

● at least one upper case letter. (A - Z)

● at least one lower case letter. (a - z)

● at least one number. (0 - 9)

● at least one special character

● no more than 3 repeated characters

● Define a SIP user ID different from the Callno

Page 37: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-20 HSC V2.6, Service Manual

s-chap3-V26_en.fm

Switch Configuration

Figure 3-16 OpenScape Office LX/MX SIP extension configuration 6

Figure 3-17 OpenScape Office LX/MX SIP extension configuration 7

Page 38: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-21

Installation and Configuration

Switch Configuration

Figure 3-18 OpenScape Office LX/MX SIP extension configuration 8

It is recommended to set two hunting groups one for access to the wakeup system and another for the hotel specific voicemail system.

Figure 3-19 OpenScape Office LX/MX SIP extension configuration 9

Page 39: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-22 HSC V2.6, Service Manual

s-chap3-V26_en.fm

Switch Configuration

3.2.5.3 OpenScape Business configuration

Figure 3-20 OpenScape Business SIP extension configuration 1

Before establishing or receiving calls an endpoint MUST register at the system. The system expects the configured call number for registration. For security reasons it is strongly recommended to use Authentication. For each extension a name can be configured in the system. The number and name is presented during call establishment if no restriction is activated (Recomendded naming is Wakeup and Voice mail). At least 2 extensions are recomendded for wakeup functionality.

Entry in telephone directory flag must be disabled.

With the increasing deployment of VoIP networks more and more attacks against VoIP equipment can be observed in such networks. SIP as an open and well-known protocol is implemented in various crack tools which are freely available in the internet. To avoid misuse of a SIP access careful configuration is crucial.

For a SIP subscriber access the following rules should be followed:

● Activate authentication

● Use a non trivial password with

a minimum of 8 and a maximum of 20 characters

● at least one upper case letter. (A - Z)

● at least one lower case letter. (a - z)

Page 40: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-23

Installation and Configuration

Switch Configuration

● at least one number. (0 - 9)

● at least one special character

● no more than 3 repeated characters

● Define a SIP user ID different from the Callno

It is recommended to set two Linear hunting groups one for access to the wakeup system and another for the hotel specific voicemail system.

Page 41: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-24 HSC V2.6, Service Manual

s-chap3-V26_en.fm

HSC Installation

3.3 HSC Installation

The following section shows you all the windows that are displayed during HSC setup.

1. The Welcome window tells you that you are about to install HSC V2.6 on your server.

Figure 3-21 HSC - Welcome Window

2. Choose the destination location for the HSC components.

Figure 3-22 HSC - Choose Destination Location for HSC

Page 42: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-25

Installation and Configuration

HSC Installation

7. Check the current settings and activate the actual installation.

Figure 3-23 HSC - Start Copying Files

Click Install to start the HSC installation.

8. The installation procedure installs all the components necessary for running HSC.

Figure 3-24 HSC - Installation Complete

Page 43: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-26 HSC V2.6, Service Manual

s-chap3-V26_en.fm

HSC Installation on Linux server or Linux HW appliance

3.4 HSC Installation on Linux server or Linux HW appliance

All Linux versions are delivered as already preinstalled appliances (HW or SW appliance). Installation has been carried out by manufacturer, only system configuration has to be completed.

3.5 Licensing

There are two types of licenses used to run HSC. First, there are trial licenses. These are time limited trial licenses which will allow you to run the HSC for up to 30 days on the server of your choice, as often as you like. Trial licenses are fully functional and can be used to try out any of the HSC's functionality. It is useful for trying out configurations before generating an actual Server License, or for running quick tests on a new server or platform. Second, there are Standard Server licenses which are needed to deploy HSC in productive environment. Each of these types of license has different 'flavors' and their own set of features.

After successful installation you will be prompted with your Server Locking-ID number. Press OK to copy Locking-ID to Clipboard.

Figure 3-25 HSC - Server Locking-ID

To obtain valid license please contact support at [email protected] quoting your Locking-ID and Delivery note number for purchased software.

> Please restart your server PC after finishing the HSC installation.

>English and German are provided as GUI language in HSC. For installation of other languages see HSC_Localisation_Tool.doc via ...\PSE\HSC\PostgreS-QL\HSCScripts.

Page 44: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-27

Installation and Configuration

Licensing

License file (key.txt) copied into Tomcat directory (usually C:\PSE\HSC\Tomcat) is automatically activated on server restart. You can check your license details in HSC Help -> License menu.

Figure 3-26 HSC - License details

Page 45: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-28 HSC V2.6, Service Manual

s-chap3-V26_en.fm

Hotel Reward

3.6 Hotel Reward

HSC V2.6 offers a simple file interface for importing and exporting relevant data for "Membership Programs" (Hotel Reward System). Via this interface guest data can be exchanged with any Hotel Reward System.For potential customer adaptations and/or extensions a service package (Professional Service) is offered.

3.6.1 Configuration of the Hotel Reward Export/Import Interface

When using the file interface, the following has to be defined in the properties file iface.properties (located in ...\HSC\Tomcat\modules\HSC_datasource\WEB-INF):

● Name and location of the input/output file (path)

● HSC.interface.external.reward-import.file=HSC.interface.external.reward-export.file=

Presettings:HSC_HOME/Tomcat/reward-import.csvHSC_HOME/Tomcat/reward-export.csv

● Time of execution

HSC.interface.external.reward-import.firstRun=HSC.interface.external.reward-export.firstRun=

The value must be entered as hhmmss (hours from 00 to 23).Presetting: 03:00 am

● Decide whether the interface should be executed at each system start (true) or not (false)

HSC.interface.external.reward-import.runAtStartup=HSC.interface.external.reward-export.runAtStartup=

● Presetting: false (i.e. no interface run upon system start).

3.6.2 Format of the Hotel Reward Export/Import Interface Files

All files have the “.csv” format, the character “;” is used as separator between the records of the file. Each file consists of a header and the following parameters:

● for Hotel Reward export:

– identification code (unique key for guest)

– surname

Page 46: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-29

Installation and Configuration

Hotel Reward

– middle name

– first name

– title

– sex (male / female)

– date of birth (yyyy.mm.dd)

– preferred language (2 letters ISO code)

– citizenship country code (2 letters ISO code

– citizenship (currently identical to address country)

– address country code

– address country

– address region

– address city

– address street

– zip code

– phone

– fax

– e-mail address

– special attributes

– company

– VIP status

– membership status

– last arrival date (yyyy.mm.dd)

● for Hotel Reward import:

– identification code (unique key for guest)

– loyalty category

– loyalty status

– VIP status

– membership status

Page 47: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-30 HSC V2.6, Service Manual

s-chap3-V26_en.fm

Human Resource

3.7 Human Resource

HSC V2.6 offers a simple file interface for exporting HR (Human Resource) relevant data of service attendants. Vai this interface personnel data, collected in HSC, can be transferred to a HR SAP system.For potential customer adaptations and/or extensions a service package (Professional Service) is offered.

3.7.1 Configuration of the Human Resource Interface

When using the file interface, the following has to be defined in the properties file iface.properties (located in ...\HSC\Tomcat\modules\HSC_datasource\WEB-INF):

● Name and location of the output file (path)

HSC.interface.external.hr.file=

Presetting:HSC_HOME/Tomcat/hr.csv

● Time of execution

HSC.interface.external.hr.firstRun=

The value must be entered as hhmmss (hours from 00 to 23).Presetting: 03:00 am,

● Decide whether the interface should be executed at each system start (true) or not (false)

HSC.interface.external.hr.runAtStartup=

Default: false (i.e. no interface run upon system start).

3.7.2 Format of the Export Interface Files

All files have the “.csv” format, the character “;” is used as separator between the records of the file. Each file consists of a header and the following parameters:

– surname

– middle name

– first name

– title

– sex (male / female)

Page 48: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-31

Installation and Configuration

E-Mail

– birth date

– personnel number

– ID for log on to the HSC system

– status of presence

– service attendant (yes / no)

– service attendant identification

– time stamp for status of presence change (yyyy.mm.dd hh:mm:ss)

– status of presence change

The current status of presence is stored in the HSC database for each employee. All associated changes are registered in a table. The latest two entries of the parameter fields described before (i.e. service attendant identification and time stamp for status of presence change) are retrieved from this table.

3.8 E-Mail

HSC V2.6 provides the option to send e-mails for the following applications:

● Service Tracking:The service request can be sent to the service attendants by e-mail.

● Message Handler:Makes possible to send comments to defined persons by e-mail.

For sending of e-mails an e-mail gateway has to be available in the customer environment.

The configuration of the connection to the e-mail gateway has to be performed on the HSC administration interface (see Administration Manual, Chapter 4).

E-Mail Gateway

From HSC to the e-mail system a standard-SMTP connection is required. For this purpose an SMTP server has to be specified in the Settings tab in the System window as follows (example):

smtp.hotelxxx.com(name of the SMTP mail server for outgoing e-mails of the hotel, where HSC is installed)

3.9 SMS

HSC V2.6 provides the option to send SMS to GSM devices for the following applications:

● Service Tracking:The service request can be sent to the service attendants by SMS.

Page 49: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-32 HSC V2.6, Service Manual

s-chap3-V26_en.fm

SNMP

● Message Handler:Makes it possible to send comments to defined persons by SMS.

For sending of SMS an SMS gateway (modem) has to be available in the customer environment supporting the SMS gateway/modem "Kannel".

The configuration of the connection to the SMS gateway/modem "Kannel" has to be performed on the HSC administration interface (see Administration Manual Chapter 4).

SMS Gateway “Kannel”

Please specify the URL of the Kannel (SMS/WAP gateway) in the Settings tab in the System window as follows (example):

http://pc0082sd/sms/sendsms?user=foo&pass=bar

Kannel is a robust, scalable WAP and SMS gateway that should be able to process even several hundreds of SMS messages per second. Kannel supports the most common protocols used in SMS centers.

For details on the Kannel gateway, see the "Kannel User's Guide" in the Internet (http://www.kannel.org/userguide.shtml).

3.10 SNMP

SNMP (Simple Network Management Protocol) is used to manage networks. The purpose is to monitor network elements (servers, routers, etc.) as well as their current status (up/down, capacity, etc.).

Within the SNMP protocol, HSC sends messages (traps) of an FM tool (fault management tool) to the SNMP manager in case of the following events:Start and shutdown of the HSC service (traps ’HSCStartup’ and ’HSCShutdown’)connection setup and failure between HSC and an interface. The name of the interface is sent as well (traps ’HSCInterfaceUp’ and ’HSCInterfaceDown).

Prerequisites

● IP-address of the SNMP manager has to be configured <snmphost>host</snmphost> in the file .../tomcat/conf/HSC.xml(traps will only be sent, if an snmphost entry exists in the HSC.xml).Optionally, port and SNMP community can be configured by means of <snmpport> and <snmpcommunity> tags.

● MIB (Management Information Base) files of HSC have to be imported at the SNMP Manager These files are included in installations CD under \Tools and are required for the mapping of the OIDs (object identifiers) sent in the traps into a text.

Page 50: HSC Connect service manual

s-chap3-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 3-33

Installation and Configuration

Use of Kirk

3.11 Use of Kirk

During the installation of HSC, the KirkApp.exe program is installed.

After installation enter the IP address of Kirk system at .../HSC/Tomcat/modules/HSC_str/WEB-INF/kirk/cfg/configuration.cfg 'call Agent ip'.

Create the following extensions in the Kirk system as virtual extensions. In .../HSC/Tomcat/modules/HSC_str/WEB-INF/kirk/KirkApp.ini these extensions have already been generated during installation (they have to match!)With these numbers the status of the service request can be changed!ForwardNr_Accepted=6001ForwardNr_Rejected=6002ForwardNr_Done=6003

Subsequently there are two issues that still have to be checked:

● The correct IP address at several IP cards

If the server has several IP cards, please check whether the correct IP address is used. Open the file .../HSC/Tomcat/modules/HSC_str/WEB-INF/kirk/KirkApp.ini and, if required, correct the IP-address (the "correct" IP-address is the one used for connecting the HSC server to the customer LAN).

● Correct Java path

If the correct Java path has not been detected during installation, you will get the respective error message ("Cannot copy additional JRE-files because installed JRE-version (<xy>) is unknown"). Open .../HSC/Tomcat/modules/ HSC_str/WEB-INF/kirk/KirkApp.ini and enter the path to the current Java Virtual Machine (e.g. "C:\PSE\Common\JRE_1.5.0.11\bin\client\jvm.dll") at 'jvmPath'.

Page 51: HSC Connect service manual

Installation and Configuration

A31003-E1325-S100-3-7620, 01-20123-34 HSC V2.6, Service Manual

s-chap3-V26_en.fm

Use of Kirk

Page 52: HSC Connect service manual

s-chap4-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 4-1

Upgrade and Migration

Upgrade of HHSC V2.0 or V2.1 to HHSC V2.5

4 Upgrade and Migration

In this chapter the upgrade of HHSC V2.0/2.1 to HHSC V2.5 and the upgrade of HHSC V2.5 into HSC V2.6 is described. In this process also data migration (backup/restore) is explained.

4.1 Upgrade of HHSC V2.0 or V2.1 to HHSC V2.5

4.1.1 Upgrade of V2.0, V2.1 Compact/Business

Compact/Business will not be addressed with HHSC V25. Both versions have been phased out (M4) at 12/07. No migration of Compact/Business towards HHSC V2.5 is available.

4.1.2 Upgrade procedure for HSC V2.0, V2.1 Professional (Short Description)

● Check unique keys (run 'checkUniqueKeys.bat’)

● Run Backup on HHSC V2.0, V2.1 Professional

● Uninstall HHSC V2.0, V2.1 Professional

● Uninstall CLA

● Uninstall Crystal Reports Enterprise, if applicable

● Upgrade Siemens HiPath CAP to SMR 5

● Configure switch for Mute function

● Upgrade Xpressions and Xpressions Connector on the Xpressions Server

● Install HHSC V2.5

● Install HHSC V2.5 License in CLA

● Run Restore on HHSC V2.5

● Configure HiPath Connection, AMO, CDR, COS settings in HHSC Maintenance

● Update customer specific interface plugins

● Convert customer specific MIS reports from Crystal Reports to JasperReports

● Convert customer specific work order lists from Crystal Reports to JasperReports

Page 53: HSC Connect service manual

Upgrade and Migration

A31003-E1325-S100-3-7620, 01-20124-2 HSC V2.6, Service Manual

s-chap4-V26_en.fm

Upgrade of HHSC V2.0 or V2.1 to HHSC V2.5

4.1.3 Check unique keys

From version 2.5 the HHSC database provides unique keys. For checking for double entries in the HHSC database V2.0 please execute 'checkUniqueKeys.bat' before migration (in the HHSC installation folder under ...PostgreSQL/HSCScripts). In the 'CheckUniqueKeys.log' you will get a list of double entries and a suggestion for a solution.

Otherwise the dataset of the double entry and all associated entries (e.g. in case of a service text [the service code has to be unique] all service requests) will not be taken over.

4.1.4 Run Backup on HHSC V2.0, V2.1 Professional

The backup can be done anytime also if HHSC is running. The backup is a batch job and stores the data as follows:HHSC charge rate import fileHHSC facility und Watchdog databaseHHSC database

Use the backup tool delivered with HHSC V2.5 (backup.bat on the installation -CD under \Toolsand start it in ...\HHSC\PostgreSQL\HSCScripts. The data will be saved in …\HHSC\backup directory. Copy this directory to a secure location!

4.1.5 Uninstall HHSC V2.0, V2.1 Professional

Run the HHSC uninstall procedure.

4.1.6 Uninstall CLA

Run the CLA uninstall procedure.

4.1.7 Uninstall Crystal Reports Enterprise

If HHSC V2.0, V2.1 Reporting was used, run the Crystal Reports Enterprise uninstall procedure.

4.1.8 Upgrade of CAP to CAP SMR 5

For upgrading from Siemens HiPath CAP V3 to SMR5 execute the procedure for upgrading of CAP (CAP update procedure) and check your settings in the CAP-Connector (HSC interface to CAP), see Section , “Configuration of NOEMI in HSC”.

Page 54: HSC Connect service manual

s-chap4-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 4-3

Upgrade and Migration

Upgrade of HHSC V2.0 or V2.1 to HHSC V2.5

As the update installation of SMR 3 to SMR 5 is not supported, the update installation has to be executed using SMR4 (export of the available SMR 3 CAP data, execute update SMR 4, execute update SMR 5, reimport data).

Please see installation-CD 2 for the 'CAP update procedure' for SMR 4 and SMR 5!

Please check after the update whether the CAP HHSC license is still available. If not, reassign it!

4.1.9 Configure switch for Mute function

Run the following AMO on the switch for the mute function :

XAPPL:CTYPE=SUBAPPL,APPLNO=62,SUBAPPL=D25,ADDEVT=FEASTST;

4.1.10 Upgrade Xpressions and Xpressions Connector on the Xpressions Server

Upgrade Xpressions 4 to Xpressions 5, if applicable.

Uninstall the HHSC Xpressions Connector V2.0, V2.1 on the Xpressions server. Install the HHSC Xpressions Connector delivered with HHSC V2.5 on the Xpressions Server.

4.1.11 Install HHSC V2.5

Install Hospitality Service Center V2.5, see Section 3.3

4.1.12 Install HHSC V2.5 License in CLA

Install the new HHSC V2.6 License File in CLA using the CLM. Only HHSC V2.5 or V2.0 Professional Connect (as Caracas replacement for V2.0) are accepted.

4.1.13 Run Restore on HHSC V2.5

Run the restore procedure delivered with HHSC V2.5. The restore procedure automatically detects the version of the backup set to be restored (V2.0 and V2.1 also) and converts the data automatically.The procedure can be run on a stopped HSC. If HSC is active it will be stopped and after procedure restarted.

Re-copy the backup directory (containing the saved HHSC data) into the HHSC directory and run restore.bat in the directory ...\HSC\PostgreSQL\HSCScripts. All data will be restored from the …\HSC\backup directory.

Page 55: HSC Connect service manual

Upgrade and Migration

A31003-E1325-S100-3-7620, 01-20124-4 HSC V2.6, Service Manual

s-chap4-V26_en.fm

Upgrade of HHSC V2.5 to a new HSC V2.6 version

4.1.14 Configure HiPath Connection

HSHC V2.5 does not support a migration of Caracas Data. It is necessary to configure the HiPath connection (for one HiPath or up to four) and AMO, CDR and COS settings in the new HSC Maintenance. See Section 8.1

4.1.15 Update customer specific interface plugins

The service technician updates the customer specific interface plugins, if applicable.

4.1.16 Convert customer specific MIS reports from Crystal Reports to JasperReports

Crystal Reports is not required and supported in HHSC V2.5 anymore. Due to the new design and implementation of reporting, the conversion of customer specific reports is not supported. The customer specific reports need to be created with the JasperReports iReport Editor. The iReport Editor is opensource and is available at http://jasperforge.org/sf/projects/ireport.

4.1.17 Convert customer specific work order lists from Crystal Reports to JasperReports

Crystal Reports is not required and supported in HHSC V2.5 anymore. Due to the new design and implementation of reporting, the conversion of customer specific reports is not supported. The customer specific reports need to be created with the JasperReports iReport Editor. The iReport Editor is opensource and is available at http://jasperforge.org/sf/projects/ireport.

4.2 Upgrade of HHSC V2.5 to a new HSC V2.6 version

To install a new version of HSC V2.6, proceed as follows:

1. Data backup:

The backup can be done anytime also if HSC is running. The backup is a batch job and stores the data as follows:HHSC version informationHHSC workorder listsHHSC MIS Reporting reportsHHSC MIS Reporting misData definitionHHSC interface plug-in filesHHSC trace settingsHHSC charge rate import fileHHSC facility und Watchdog databaseHHSC database

Page 56: HSC Connect service manual

s-chap4-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 4-5

Upgrade and Migration

Upgrade of HHSC V2.5 to a new HSC V2.6 version

Use the backup tool delivered with HSC V2.6 (backup.bat on the installation-CD under \Tools and start it in ...\HSC\PostgreSQL\HSCScripts. The data will be saved in …\HSC\backup directory. Copy this directory to a secure location!

2. Uninstall the previous HHSC V2.5 build (reboot is necessary afterwards!) and delete the "HHSC" directory of the previous build (e.g. \Siemens\HSC).

Before starting the new installation, the setup procedure checks if there are any components left from a former de-installation. If so, a message is displayed:

"The HSC service already exists on this machine. Setup cannot continue! Please refer to Administration Manual Chapter 2 for further information."

Then you should perform the following steps:

● Click Start > Settings > Control Panel > Administration Tools > Services and make sure that the service "Siemens HSC" was removed.

● If not, open a command prompt and enter the command sc delete HSC25 to remove the service "Siemens HSC" (command will take effect after reboot).

● Open the registration editor by Start > Execute and the command regedit. Go to "HKEY_LOCAL_MACHINE\SYSTEM\Current ControlSet\Services" and look for the key "HSC20". This key should not exist. If it exists, remove the key.

● Delete the folder "HHSC" where HHSC was formerly installed - with the exception of "backup" (should be copied to a safe location).

● Reboot your PC.

3. Install the new HSC V2.6 build (see Section 3.3)

4. Restore your data:Re-copy the backup directory (containing the saved HSC data) into the \HSC directory and run restore.bat in the directory ...\HSC\PostgreSQL\HSCScripts. All data will be restored from the …\HSC\backup directory. The HSC service will be stopped by the restore.bat und restarted automatically afterwards.

5. Open the HSC start page on the client PCs with http://<servername>:8270/

If you run the HSC system on the server (i.e. client PC = server PC), the start page can also be accessed by clicking Start > Programs > PSE HSC > HSC 2.6.See Chapter 5, “Client Start”

> Report files and PMS PlugIns which are individually defined or changed are not overwritten, they are available furthermore.

Page 57: HSC Connect service manual

Upgrade and Migration

A31003-E1325-S100-3-7620, 01-20124-6 HSC V2.6, Service Manual

s-chap4-V26_en.fm

Upgrade of HHSC V2.5 to a new HSC V2.6 version

Page 58: HSC Connect service manual

s-chap5-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 5-1

Client Start

Installation of JRE

5 Client Start

Open the HSC start page by entering

http://<servername>:8270

into your browser's navigation bar (<servername> is the identification (IP address) of the server PC where the HSC server software is installed).

Please note

● The HSC graphical user interface needs the Java Runtime Environment. If this JRE version is not installed on your client PC, the JRE setup is started automatically as soon as you try to log in with the HSC system (see Section 5.1, “Installation of JRE”).After Java installation you should disable automatical Java upgrade, see Section 5.1.1.

● If you have more than one JRE versions installed, please set Windows Explorer to make sure that HSC will start automatically with the correct version (see Section 5.2, “Settings in Case of Several JRE Versions”).

● If you want to start HSC without the Internet Explorer, you can create a .bat-file and start HSC with this file (see Section 5.3, “Client Start without Internet Explorer”).

● When the activation of your HSC system on the client PC fails, check the settings of Java (see Section 5.4, “Problems at the Client Start”).

5.1 Installation of JRE

If the JRE version 1.6 is not installed on your client PC, the JRE setup is started automatically as soon as you try to log in with the HSC system. You also can download Java from the HSC welcome page.

No settings must be configured during setup. You can executive this setup-procedure by clicking the Accept button and Finish button.

>Java updates will be published from time to time and also incorporated into the HSC set-up. To find out which Java version comes with your HSC system, please refer to the Release Notes. At the time this manual went to press, this was JRE version 1.6. For this reason, the examples and figures in this manual make reference to this particular version.

Page 59: HSC Connect service manual

Client Start

A31003-E1325-S100-3-7620, 01-20125-2 HSC V2.6, Service Manual

s-chap5-V26_en.fm

Installation of JRE

Figure 5-1 Java - License Agreement

Figure 5-2 Java JRE Setup Complete

After the completion of the setup procedure, a message will be displayed to indicate whether or not a reboot is necessary.

Page 60: HSC Connect service manual

s-chap5-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 5-3

Client Start

Settings in Case of Several JRE Versions

5.1.1 Disable automatical Java upgrade

If you have installed Java you will always get the newest Java version automatically. HSC only works with Java version 1.6. Therefore you have to disable the automatical upgrade.

Open the Java Control Panel (by clicking Start > Settings > Java Control Panel) and make sure that Java will not be upgraded by disabling the checkbox "Check for Updates Automatically" (to be set in the Update tab).

Figure 5-3 Java Control Panel, Disabling Automatical Updates

5.2 Settings in Case of Several JRE Versions

If you have installed several JRE versions on your computer, you can set Windows Explorer to start HSC automatically with Java Web Start Version 1.6.

1. Open your Windows Explorer

2. In menu item "Extras/Folder Options" select "JNLP" file on the File Types tab and click Advanced.

3. In the displayed Edit file type window click Edit.

Page 61: HSC Connect service manual

Client Start

A31003-E1325-S100-3-7620, 01-20125-4 HSC V2.6, Service Manual

s-chap5-V26_en.fm

Settings in Case of Several JRE Versions

4. In the new window Editing action for type: the path and the correct JRE version has to be stated (e.g. "C\Program\Files\Java\jre1.5.0_10\jawas\javaws.exe* %1"). Please note that after the path and a blank %1 has to be enclosed by inverted commas!

5. Close all windows by clicking OK.

Figure 5-4 Java - Setting of the Correct Version for HSC Start

Page 62: HSC Connect service manual

s-chap5-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 5-5

Client Start

Client Start without Internet Explorer

5.3 Client Start without Internet Explorer

If you want to start HSC without Internet Explorer, you can create a .bat file yourself and open HSC by means of this file via Java Web Start:

1. Click with the right mouse button on a free space on your desktop to open the context menu.

2. With "New / Text document" create the file "New Text Document.txt".

3. Open this file by means of a double click and enter the correct path:"<absolute path to JRE 1.4>\javaws\javaws.exe" "http://<IP-address of HSC-Server>:8270/apps/gui.jsp"e.g. "C:\Program Files\Java\jre1.5.0_10\javaws\javaws.exe" "http://158.226.25.246:8270/ apps/gui.jsp"

Save your entries and close the file.

4. Rename the file, e.g. "start HSC.bat". The extension .bat is essential.

5. By double-clicking the file the newly created .bat file will be executed and HSC will be opened directly via Java Web Start (on the preconditions that the settings in JNLP extension are correct).

5.4 Problems at the Client Start

When the activation of your HSC system on the client PC fails, check if the following preconditions are fulfilled:

● Open the Java Control Panel (by clicking Start > Settings > Control Panel > Java) and make sure that Java will be used as the default Java Runtime Environment in your browser (to be set in the Browser tab). You also need this setting for viewing the MIS-reports!

> If you open another Java Web Start Application apart from HSC, close the first Inter-net Explorer before starting the second application.

Page 63: HSC Connect service manual

Client Start

A31003-E1325-S100-3-7620, 01-20125-6 HSC V2.6, Service Manual

s-chap5-V26_en.fm

Problems at the Client Start

Figure 5-5 Java Control Panel, Browser

● Open the Java Control Panel (by clicking Start > Settings > Control Panel > Java > General tab > Network Settings) and set the network proxy settings to ’Direct connection’.

Figure 5-6 Java Control Panel, Proxy Settings

Page 64: HSC Connect service manual

s-chap6-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 6-1

Using the HSC Maintenance Tool

Functional Overview

6 Using the HSC Maintenance Tool

6.1 Functional Overview

The HSC Maintenance program runs exclusively on the HSC server and is used in HSC for maintenance, error analysis and configuration. HSC Maintenance can be used to verify if HSC works properly in the hotel system. Therefore the program shows the current status of the interfaces to other systems like PMS and CAP and it enables the service engineer to define and modify trace settings and to save trace data in files.

HSC Maintenance provides you with the functions described in this and some other chapters of the Service Manual, as well as in the Administration Manual:

> It provides data on the interface status.

> It makes possible the definition of traces by combining certain predefined trace topics and the activation of these traces in case of an error.

> It makes possible the configuration of the CAP Connector as well as the NOEMI interface between HiPath switches and the HSC system and the mass data import/export of HSC-specific master and configuration data.

> Within HSC Maintenance you can also launch all functions from the Administration menu of the HSC Front Office user interface (see Administration Manual).

HSC Maintenance can only be used at times when the HSC server components are active as well.All configurations of components that are offered at the user interface of HSC Maintenance can only be performed when the HSC server is running.

6.2 User Interface Structure

The user interface of HSC Maintenance is structured similarly to that of HSC Front Office. Currently you can choose between English and German and also launch a context-sensitive online help for more information.

6.2.1 Login

As soon as you have started HSC Maintenance via Start > Programs > HSC > HSC Maintenance, the Login window will be displayed on your desktop.

> The configuration functions for these components and the mass data transfers should be performed exclusively by a service engineer!

Page 65: HSC Connect service manual

Using the HSC Maintenance Tool

A31003-E1325-S100-3-7620, 01-20126-2 HSC V2.6, Service Manual

s-chap6-V26_en.fm

User Interface Structure

clicked Start Front Office Client on the HSC Homepage the Login window will be displayed on your desktop.

Enter your User name and your Password, select the required GUI language and click OK.

Figure 6-1 Login Window

User name

Enter your user name.

Password

Enter your password.

GUI language

Select the requested language of the graphical user interface (including online help).

>Access to HSC Maintenance (with all its functions!) is only possible for service engineers to whom a role including the right "Maintenance Login" is assigned (see Administration Manual, Chapter 4).

> Contrary to HSC Front Office the GUI language for HSC Maintenance cannot be changed while the program is running, but can only be selected at login.

>Currently English and German can be selected as GUI languages.Additional languages can be integrated into the HSC system by complementing the localization data. The exact procedure has to be discussed with the HSC product management. For more details please see also Appendix B.

Page 66: HSC Connect service manual

s-chap6-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 6-3

Using the HSC Maintenance Tool

User Interface Structure

6.2.2 Main Desktop of HSC Maintenance

After logging in, the main desktop of HSC Maintenance is displayed on your screen, which consists of two areas:

● the navigation area with the menu bar and

● the working area.

Messages are displayed by activating the respective menu item (see Section 6.2.4) as a separate window in the main desktop of HSC Maintenance.

Figure 6-2 Main Screen of HSC Maintenance

Navigation Area

Immediately below the header of the HSC main desktop you will find the menu bar, comprising the menus Main, Administration, Trace and Help.

Page 67: HSC Connect service manual

Using the HSC Maintenance Tool

A31003-E1325-S100-3-7620, 01-20126-4 HSC V2.6, Service Manual

s-chap6-V26_en.fm

User Interface Structure

Figure 6-3 HSC Maintenance Menu Bar (with Displayed Menu)

The functions that can be launched via the menu bar are described - depending on the target group - either in chapters of this manual or in the HSC Administration Manual.

Working Area

The working area is located beneath the navigation area.

If active trace windows were located in the working area when terminating HSC Maintenance, these windows will be displayed in the same position of the working area when you log in again.

6.2.3 Menu Bar

In the menu bar you will find the follwing menus:

With the items in the Main menu described below you can get information about the status of interfaces, show/hide the message area and terminate HSC Maintenance.

Figure 6-4 Menu Items in "Main"

Interface Status

Opens a window for showing the current status of interfaces to 3rd-party components (see Section 6.3).

Messages

Upon activation of this menu item, messages are output as a table in a separate window. The structure of the message window is explained in Section 6.2.4.

Exit

Used for terminating HSC Maintenance on the HSC server.

Page 68: HSC Connect service manual

s-chap6-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 6-5

Using the HSC Maintenance Tool

User Interface Structure

By means of the Administration menu you can activate those HSC-specific administrative functions that are performed, as a rule, (also) by a service engineer. They are described in Chapter 7, “Import of Mass Data” and Chapter 8, “Configuration of NOEMI in HSC” of this manual and in the Administration Manual.

Figure 6-5 Menu Items in "Administration"

The two menu items in the Trace menu allow service engineers to configure and activate traces (see Section 6.4).

Figure 6-6 Menu Items in "Trace"

The Help menu supplies you with information on the currently installed HSC software version and makes access to the start page of the online help.

Figure 6-7 Menu Items in "Help"

Help

Opens a browser window and displays the start page of the HSC-specific online help in HTML format. You can navigate to the individual chapters of the HSC Service Manual or the HSC Aministration Manual by using the table of contents, the index or the search function. For more details on the online help see User Guide, Chapter 3.

Page 69: HSC Connect service manual

Using the HSC Maintenance Tool

A31003-E1325-S100-3-7620, 01-20126-6 HSC V2.6, Service Manual

s-chap6-V26_en.fm

User Interface Structure

About...

Opens the About window, where the version of the entire system as well as the HSC components graphical user interface, database and core are entered and the latest hot fixes are listed.

Figure 6-8 About Window

Clicking the links Detailed module versions... and http://www.siemens.com/hotel you get to the Status Overview and get information on the Siemens Hotel Portal (see User Guide, Chapter 2).

6.2.4 Message Window

You can display the messages output by HSC Maintenance in a separate window on your desktop.For showing the message window you can use the menu item Messages in the Main menu.

In this area messages, especially faults, referring to HSC Maintenance are displayed. However, these messages do not have direct impact on the system. Therefore you do not have to solve potential problems at once. The messages are only meant for your information (and are not saved in the HSC database).

The messages are output as a table with four columns - Received, Priority, Type and Text. If required, use the scroll bar to be able to view all messages.

You can use the button Clear to remove all messages currently displayed in the message window.By means of the button Close you can hide the message window.

Page 70: HSC Connect service manual

s-chap6-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 6-7

Using the HSC Maintenance Tool

Showing the Interface Status

Figure 6-9 Message Window Containing Messages

6.3 Showing the Interface Status

You can open the Interface Status window by means of the Interface Status menu item in the Main menu.

A service engineer can see within this window if the interfaces of HSC to external components are active. For each interface type configured in the HSC system the window shows its current status by means of a colored bar:

Alive interfaces will be shown in green colour,offline interfaces in red colour,interfaces currently being connected in blue colour, andinterfaces with an unknown state are shown in brown.

The date displayed at the right-hand side of the colored bar shows when the current interface status has been established.

Page 71: HSC Connect service manual

Using the HSC Maintenance Tool

A31003-E1325-S100-3-7620, 01-20126-8 HSC V2.6, Service Manual

s-chap6-V26_en.fm

Defining and Activating Traces

Figure 6-10 HSC Maintenance - Interface Status Window

6.4 Defining and Activating Traces

One of the main functions of HSC Maintenance is the definition of traces as well as the production and output/archiving of trace data in case of an error.In doing so, it must be possible that a service engineer can see in real time, which kind of commands and/or data are transferred via an interface.

For error analysis and recovery various traces can be drawn via HSC Maintenance which consist of several trace topics (representing the interface to be traced). For each trace topic a special trace level can be set. The respective trace data is stored in a configurable number of trace files.

All HSC-related trace data can be found in the directory in which the HSC server is installed, i.e. the subdirectory ...HSC\tomcat\logs.

The maximum size and the maximum number of these trace files can be set and should have a reasonable value.By default each of the trace files shall have a maximum size of 10 MB. If this size is reached, the respective trace file will be renamed and the next one will be created. As soon as the

>Note that it might happen that confidential data are passed on via an interface.HSC Maintenance cannot hide such data. A service engineer that is authorized to use HSC Maintenance will always see all data contained the trace information!

Page 72: HSC Connect service manual

s-chap6-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 6-9

Using the HSC Maintenance Tool

Defining and Activating Traces

specified number of trace files of the same type ("max. index"; default = 10) exist, the oldest of these trace files will be overwritten with new trace entries in accordance with the rollover principle.

6.4.1 New Trace Window for Showing Current Trace Data

If you activate menu item New Trace Window in the Trace menu, initially an empty trace window will pop up with a title generated by the system (= "Trace#<n>", where <n> is a consecutive number). By means of the Configure button you can change this title, specify a trace file for archiving trace data and select appropriate trace topics in the subsequent window Configure Trace (see Section 6.4.1.1) in order to get the required HSC trace information displayed in real time in the trace window. A maximum of 5000 lines can be displayed in the window.

The same window - displaying the trace data of the currently active trace in real time - pops up if you activate the Show button in the Trace Overview window (see Section 6.4.2).

>Several of these trace windows can be open at the same time in the working area of the main screen of HSC Maintenance and you can have different trace data shown and/or trace files archived at the same time.

Page 73: HSC Connect service manual

Using the HSC Maintenance Tool

A31003-E1325-S100-3-7620, 01-20126-10 HSC V2.6, Service Manual

s-chap6-V26_en.fm

Defining and Activating Traces

Figure 6-11 Window for Showing Current Trace Data in Real Time

The window contains several buttons for processing the trace data and a working area where the current trace data are displayed:

Opens the subsequent window Configure Trace (see Section 6.4.1.1) where you can define the type of the trace data to be displayed in the trace window in future by selecting appropriate trace topics and pressing the buttons Apply and Show in the Configure Trace window.

Deletes the trace data currently displayed in the window.

Saves the trace data currently displayed in the window to a trace file that can be selected:

> If you have activated the checkbox Selected texts only (see below), only the trace lines selected by you will be stored.

Page 74: HSC Connect service manual

s-chap6-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 6-11

Using the HSC Maintenance Tool

Defining and Activating Traces

> To be able to select trace lines with the mouse we recommend to first activate the checkbox Scroll lock (see below).

Inserts a separation line into the window at the position of the last produced trace line so that current and future trace lines can be clearly discerned visually.

Selected texts only

By activiating this checkbox only trace lines selected by you in the window will be written into a trace file to be selected when the Save button is clicked.If the checkbox has not been activated, all trace data that can be shown in the window (max. 5000) are saved when the Save button is clicked.

Scroll lock

If the checkbox is activated you can only change the currently visible section of the trace data by moving the scroll bar yourself. This simplifies the selection of trace lines (e.g. before storing a trace file).If the checkbox has not been activated, the currently produced trace data are passing through the window in real time from the bottom to the top. Selecting individual trace lines is made more difficult in this way.

Page 75: HSC Connect service manual

Using the HSC Maintenance Tool

A31003-E1325-S100-3-7620, 01-20126-12 HSC V2.6, Service Manual

s-chap6-V26_en.fm

Defining and Activating Traces

6.4.1.1 Configure Trace to be Displayed

This window serves for the management of the trace configuration which is assigned to the window shown in Figure 6-11 for outputting of trace data.

Figure 6-12 Window for Configuring a New Trace

The window contains input fields and a selection area for the definition of the trace currently to be activated and the trace topics to be assigned to it, as well as a determination of the properties of a trace file where the trace data generated by this trace may have to be archived:

Name (optional)

Freely selectable name for the trace topics group selected for the trace window (see Figure 6-11)By default, HSC Maintenance suggests "Trace#<n>", where <n> is a consecutive number.

>Please note that in the Configure Trace window only one trace can be defined, while in the Trace Overview window (see Section 6.4.2) any number of traces can be configured.

Page 76: HSC Connect service manual

s-chap6-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 6-13

Using the HSC Maintenance Tool

Defining and Activating Traces

File

The activation of this checkbox makes possible the determination of properties of a trace file for archiving the current trace data (the respective input fields can be filled in).

Filename (pattern)

Freely selectable name of the trace file for archiving the current trace dataThe name is meant only as an "example", as neither an absolute path nor the exact file name of the trace file can be stated. A consecutive index number will be added to the name stated here as well as the extension ".txt".Each trace file will be stored in the subdirectory ...HSC\omcat\logs.

Max. size (MB)

Maximum size of the trace file; if this size has been reached, either a new trace file of the same type will be created or the oldest of these trace files will be overwritten with new trace entries according to the principle of circulation - depending on what is specified in Max. Index (see below) and the current value of the index.

Max. index

Determines the maximum number of trace files that may belong to a trace

Example:In case of Max. index = 5, the trace files might have the following names (incl. path indication): ...tomcat\logs\um_log.001.txt, ...tomcat\logs\um_log.002.txt, ... ...tomcat\logs\um_log.005.txt. As soon as the maximum index number (= 5) has been reached and the last of the trace files is full, the trace files are overwritten with new trace entries in accordance with the circulation principle: um_log.001.txt is deleted, um_log.002.txt is renamed to um_log.001.txt, um_log.003.txt is renamed to um_log.002.txt, and so on, um_log.005.txt is newly created.

Available HSC clients

This drop-down list is active only if at least one trace topic in the Traced topics list has been defined as "Client-relevant" (setting in the Edit Trace Topics window; see Section 6.4.2.2).In the drop-down list all HSC clients are listed (identified by their client numbers and IP addresses) where a user is currently logged on. (The list can be updated by clicking the Refresh button.)You can choose the HSC client for whom the trace data should be detected. When "Broadcast" has been selected, all HSC clients where currently a user is logged on will be traced.

Traced topics

Selection area where you can assign suitable trace topics to the currently selected trace or revoke existing assignments of trace topics by means of the following buttons:

Page 77: HSC Connect service manual

Using the HSC Maintenance Tool

A31003-E1325-S100-3-7620, 01-20126-14 HSC V2.6, Service Manual

s-chap6-V26_en.fm

Defining and Activating Traces

Opens the Add Trace Topic window (see Section 6.4.2.1) where you can select a trace topic from all the existing ones for the trace currently being configured, assign a trace level to it and add the trace topic to the Traced topics list.

Removes a selected trace topic from the Traced topics list and revokes the assignment of this trace topic to the trace currently being configured.

The buttons Apply, Show and Close have the same function as the ones in the Trace Overview window (see Section 6.4.2).

6.4.2 Trace Overview

By means of the menu item Trace Overview in the Trace menu you can open the Trace Overview window which serves for defining and changing of traces that are composed of certain trace topics. In this window, you can also specify the names and sizes of the related trace files where the trace data have to be archived.

Page 78: HSC Connect service manual

s-chap6-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 6-15

Using the HSC Maintenance Tool

Defining and Activating Traces

Figure 6-13 Trace Overview Window for Defining/Changing of Traces

The window consists of three parts:

● a selection area where you add newly configured traces and/or remove already existing ones

● a selection area where you assign suitable trace topics to the currently selected trace, or clear existing assignments of trace topics

● input fields for the definition of an individual trace file for each configured trace

1. Buttons in the selection area Configured traces

With this button you can insert a new trace in the Configured traces list, assign different trace topics to this trace and define the properties of a trace file where the trace data of this trace should be saved.

Page 79: HSC Connect service manual

Using the HSC Maintenance Tool

A31003-E1325-S100-3-7620, 01-20126-16 HSC V2.6, Service Manual

s-chap6-V26_en.fm

Defining and Activating Traces

Clicking this button clears the selected trace from the Configured traces list.

Name (optional)

Freely selectable name for a traceBy default, HSC Maintenance suggests "Trace#<n>", where <n> is a consecutive number.

2. Buttons and selection list in the selection area Traced topics

Opens the Add Trace Topic window (see Section 6.4.2.1) where you can select a trace topic from all the existing ones for the trace currently being configured, assign a trace level to it and add the trace topic to the Traced topics list.

Removes a selected trace topic from the Traced topics list and revokes the assignment of this trace topic to the trace currently being configured.

Available HSC clients

This drop-down list is active only if at least one trace topic in the Traced topics list has been defined as "Client-relevant" (setting in the Edit Trace Topics window; see Section 6.4.2.2).In the drop-down list all HSC clients are listed (identified by their client numbers and IP addresses) where a user is currently logged on. (The list can be updated by clicking the Refresh button.)You can choose the HSC client for whom the trace data should be detected. When "Broadcast" has been selected, all HSC clients where currently a user is logged on will be traced.

> Note that traces whose trace data are currently displayed in a trace window can only be cleared after the respective trace window has been closed.

Page 80: HSC Connect service manual

s-chap6-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 6-17

Using the HSC Maintenance Tool

Defining and Activating Traces

3. Input fields for the definition of trace files

File

Activation of this checkbox makes possible the determination of properties of a trace file for archiving the trace data of the currently selected trace (the respective input fields can be filled in).

File name (pattern)

Freely selectable name of the trace file for archiving the trace data of the currently selected traceThe name is meant only as an "example" (further details in Section 6.4.1.1).

Max. size (MB)

Maximum size of the trace file (further details in Section 6.4.1.1)

Max. Index

Determines the maximum number of trace files that may belong to a trace(example in Section 6.4.1.1)

To make the activities you have performed in the Trace Overview window effective in HSC Maintenance, click this button.Therefore Apply can be clicked, as soon as you have made a change in the window.

To be able to see the trace data produced by the selected trace in real time as trace lines, open a (new) trace window by clicking this button (see Section 6.4.1).

Closes the Trace Overview window.

Page 81: HSC Connect service manual

Using the HSC Maintenance Tool

A31003-E1325-S100-3-7620, 01-20126-18 HSC V2.6, Service Manual

s-chap6-V26_en.fm

Defining and Activating Traces

6.4.2.1 Add Trace Topic

With this window you can select a trace topic from all the existing ones, assign a trace level to it and, by clicking OK, assign the trace topic to the trace that is currently being edited in the Configure Trace window (see Section 6.4.1.1) or in the Trace Overview window (see Section 6.4.2).

Figure 6-14 Window for Adding a New Trace Topic

Clicking this button will open the subsequent window Edit Trace Topics (see Section 6.4.2.2), where trace topics can be configured, which then will be displayed in the Available predefined topics list and then can be assigned to corresponding traces in the Trace Overview window (see Section 6.4.2).

Trace level

In the Add Trace Topic window the following trace levels can be selected:

Name Contents

FATAL Highest level, lowest number of trace entries (only the most severe errors are logged).

ERROR Errors that impair the functioning of HSC are logged.

WARN Warnings that do not impair the smooth operation of HSC will be logged.

INFO Information that just documents the operation of HSC is logged.

DEBUG Lowest level, highest number of traces (detailed information on the internal processing is output).

Table 6-1 Trace Levels

Page 82: HSC Connect service manual

s-chap6-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 6-19

Using the HSC Maintenance Tool

Defining and Activating Traces

Please note that all trace entries of the trace levels above the set trace level are also displayed in the trace window and/or written in the currently set trace file(s) (e.g. if the trace level WARN is set, the trace file also includes all trace data for the trace levels ERROR and FATAL).

6.4.2.2 Edit Trace Topic

For defining, editing and clearing of trace topics the Edit Trace Topics window is available to you, which will be displayed if you activate the Edit ... button in the Add Trace Topic window (see Section 6.4.2.2).

By combining different trace topics you can define different traces which supply specific trace data for error analysis and recovery. Each trace topic is characterized by one or several loggers, i.e. HSC software parts that provide trace data to a specific software component.

Figure 6-15 Window for Editing Trace Topics

Predefined topics

In this list you can include new trace topics or clear already existing ones. For this purpose the Add and Remove buttons are available to you:

>If you define a new trace topic you have to know the name(s) of the logger(s) required. For this purpose you will usually need the support of Professional Services or of the HSC development team!

Page 83: HSC Connect service manual

Using the HSC Maintenance Tool

A31003-E1325-S100-3-7620, 01-20126-20 HSC V2.6, Service Manual

s-chap6-V26_en.fm

Defining and Activating Traces

Adds a new trace topic to the Predefined topics list whose name you must edit in the input field Name.

Removes a selected trace topic from the Predefined topics list.

Name

Freely selectable name of a newly added trace topicBy default, HSC Maintenance suggests "New topic<n>", where <n> is a consecutive number.

Logger

Selection list and input field for removing and/or adding of loggers to a trace topic.

You can remove loggers from the selection list for the trace topic just selected by selecting one logger at a time in the list and clicking the Remove button.

You can add one or several logger(s) to the trace topic just selected or newly added by entering the name of one logger at a time in the input field beneath the list and clicking the Add button.

In the input field you can always use only the "*" character instead of the "com.siemens.pse.HSC" string. For example, if you have written "*.resman" in the input field and then clicked Add, a "com.siemens.pse.HSC.resman" will be displayed in the list of loggers.

Client-relevant

This checkbox must be activated if you assign loggers referring to the HSC client side to a trace topic.

> If a trace topic is marked as "Client-relevant", all loggers assigned to this trace topic have to be a java-Class or a java-Package of the HSC client.

Page 84: HSC Connect service manual

s-chap6-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 6-21

Using the HSC Maintenance Tool

Defining and Activating Traces

To make the activities you have performed in the Edit Trace Topics window effective in HSC Maintenance, click this button.Therefore Apply can be clicked, as soon as you have made a change in the window.

Closes the Edit Trace Topics window.

6.4.3 Structure of HSC-Specific Trace Entries

Below you will find a general explanation of how HSC-specific trace entries are structured, and which trace data is included in these entries.

Each HSC-specific trace entry contains the following information in English, each separated by "|".

● Date and time

● Trace level

● Class name

● Method name@line number in the source code

● Specific trace message in English as plain text

● Optionally: English text exception

Examples:

1. 02.03 14:47:08| WARN|Thread-0@1977b9b |

com.siemens.pse.HSC.pbx.noemi.SwitchConnectionHolder@61373f |

start()#80|Not enough languages set, using default |

2. 02.03 14:47:20|ERROR|CapConnectionFirstLogin@c16b18 |

com.siemens.pse.HSC.pbx.cap.CapConnection@1e152f4 |

doLogin()#263|Communication error | java.net.ConnectException: Connection

refused: connect; at java.net.PlainSocketImpl.socketConnect(Native Method);

> When trace data refer to a HSC client, the trace entries additionally contain the client number as an idenitification of the client.

Page 85: HSC Connect service manual

Using the HSC Maintenance Tool

A31003-E1325-S100-3-7620, 01-20126-22 HSC V2.6, Service Manual

s-chap6-V26_en.fm

Defining and Activating Traces

at java.net.PlainSocketImpl.doConnect(Unknown Source);

at java.net.PlainSocketImpl.connectToAddress(Unknown Source);

at java.net.PlainSocketImpl.connect(Unknown Source); |

Page 86: HSC Connect service manual

s-chap7-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 7-1

Mass Data - Import, Export

Import of Mass Data

7 Mass Data - Import, Export

By importing and exporting of mass data, HSC 2.6 offers the option to integrate many entries quickly into the database and/or copy them from the database into a file.

HSC offers 3 variants for importing/exporting of data:

● Master data

● Configuration data

● Both (Master data and configuration data)

See Figure 7-4 for a specification of data.

Import is conducted from an XML-file, export into an XML-file.

7.1 Import of Mass Data

When importing data into the HSC database, please take note of the following:

● Import is conducted via an XML-file. This file can be generated by the 'HSC v2 5 MasterData-Interface Tool.xls (on the installation CD 1 under \Tools). This tool can only be used for the import of master data, however not for configuration data. It offers help in the creation of an Excel file (only in the structure necessary for import) and for conversion into an XML-file. You will find an accurate description in Appendix C.

● Master data: Already existing master data (e.g. extensions) are not overwritten or changed. A warning is output in the logfile (see Figure 7-6).

● Configuration data: These data will be overwritten! However you are asked before (during the import), if you really want to do this ("HSC-configuration data are overwritten. Do you want to continue?") Configuration data have to be directly (by means of an editor) imported into the xml-file. The easiest way to do this is to export the configuration data, change the file created in this way and then import it.

> Before importing new data into the database, you may save your old data by exporting them!

>Make sure that during a data import no other administration or configuration activities are executed. Read-only access to the database constitutes no interference.

Page 87: HSC Connect service manual

Mass Data - Import, Export

A31003-E1325-S100-3-7620, 01-20127-2 HSC V2.6, Service Manual

s-chap7-V26_en.fm

Import of Mass Data

Open the Mass Data Import window by means of Start > Programs > Siemens HSC > HSC Maintenance > Administration > Mass Data Import.

Figure 7-1 Mass Data Import, Selection of an XML-file.

By clicking the Select button next to the XML-file, a Search window will be opened for assigning your XML-file with the import data. The name and the path of the selected file is displayed and the file will be submitted to a syntax check. At the same time the generation of a logfile with the name 'Date of creation_Time of creation_HSC_Import.log' in the same folder is suggested. If you want another logfile, click Select next to the logfile to open a search window for selecting a log file in which the log data will then be entered.

By clicking Next another syntax check of the XML-file is made and a window is opened where you can define whether the process shall be continued or aborted in case of errors or already existing data records. If you do not want to abort the process, the logfile will output warnings regarding faulty or duplicate data records (see logfile Figure 7-6).

> The import and export of mass data shall be performed exclusively by service engineers and therefore it can only be opened via HSC Maintenance.

Page 88: HSC Connect service manual

s-chap7-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 7-3

Mass Data - Import, Export

Import of Mass Data

Figure 7-2 Mass Data Import, Options for Abortion

Figure 7-3 Mass Data Import, Selection of Type of Data

Page 89: HSC Connect service manual

Mass Data - Import, Export

A31003-E1325-S100-3-7620, 01-20127-4 HSC V2.6, Service Manual

s-chap7-V26_en.fm

Import of Mass Data

In this window you define the type of data. The data will be specified in the subsequent window.

Figure 7-4 Mass Data Import, Selection of Data Categories

The data categories available in the XML-file are offered for selection. For convenience, the buttons Select All and Select None are offered.

Clicking the button Import will start the data import process.

Page 90: HSC Connect service manual

s-chap7-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 7-5

Mass Data - Import, Export

Import of Mass Data

Figure 7-5 Mass Data Import, Indication of the Elements Currently Being Imported

You can see the elements being imported during the import process. In the end the name and path of the log file is stated once more, where you can read all warnings (see subsequent window). In the logfile all processes are logged individually!

Page 91: HSC Connect service manual

Mass Data - Import, Export

A31003-E1325-S100-3-7620, 01-20127-6 HSC V2.6, Service Manual

s-chap7-V26_en.fm

Import of Mass Data

Figure 7-6 Mass Data Import, Logfile after Import

In der Logdatei werden alle Vorgänge vom Import dokumentiert. Grundsätzlich gibt es 4 Arten von Nachrichten:

All import steps are documented in a log file. There are four message types:

● SUCC: A message of this type is printed always after a row or an entry is saved in the database (e.g. a hotel address).

● INFO: Informative messages, e.g. log file is generated

Page 92: HSC Connect service manual

s-chap7-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 7-7

Mass Data - Import, Export

Export of Mass Data

● WARN: Warnings inform you that there is something incorrect or missing in the import file - however, it is not serious, and the row processing can go on.

● ERROR: An error has occured, the data in the row have not been stored in the database. This is the case usually when the checks (dependences, availability of elements,...) disclose an error.

7.2 Export of Mass Data

When exporting data from the HSC database, please take note of the following:

● All data from the HSC database can be exported into an XML-file. See Figure 7-9 for the selection of data categories.

● Make sure that during data export no other administration or configuration activities are executed. Read-only access to the database constitutes no interference.

Open the Mass Data Export window by means of Start > Programs > Siemens HSC > HSC Maintenance > Administration > Mass Data Import.

Figure 7-7 Mass Data Export, Selection of File

> Import and export of mass data shall be performed exclusively by service engineers and therefore it can only be opened via HSC Maintenance.

Page 93: HSC Connect service manual

Mass Data - Import, Export

A31003-E1325-S100-3-7620, 01-20127-8 HSC V2.6, Service Manual

s-chap7-V26_en.fm

Export of Mass Data

By clicking the Select button next to the XML-file a search window will be opened so that you can select an XML-file for the exported data. The name and the path of the selected file are displayed. At the same time the generation of a logfile with the name 'Date of creation_Time of creation_HSC_Export.log' in the same folder is suggested. If you want a different logfile, click Select next to the logfile to open a search window for selecting a log file, in which the log data will then be entered.

Figure 7-8 Mass Data Export, Selection of Type of Data

In this window you define the type(s) of data. The data will be specified in the subsequent window.

Page 94: HSC Connect service manual

s-chap7-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 7-9

Mass Data - Import, Export

Export of Mass Data

Figure 7-9 Mass Data Export, Selection of Data Categories

You can choose from all data categories currently available. For convenience the buttons Select All and Select None are offered. Clicking the button Export will start the export process.

Page 95: HSC Connect service manual

Mass Data - Import, Export

A31003-E1325-S100-3-7620, 01-20127-10 HSC V2.6, Service Manual

s-chap7-V26_en.fm

Export of Mass Data

Figure 7-10 Mass Data Export, Export Finished

You can see the elements being exported during the export process. In the end the name and path of the log file is stated once more, where you can read all warnings (see subsequent window). In the logfile all processes are logged individually!

Page 96: HSC Connect service manual

s-chap7-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 7-11

Mass Data - Import, Export

Export of Mass Data

Figure 7-11 Mass Data Export, Logfile after Export

Page 97: HSC Connect service manual

Mass Data - Import, Export

A31003-E1325-S100-3-7620, 01-20127-12 HSC V2.6, Service Manual

s-chap7-V26_en.fm

Export of Mass Data

Page 98: HSC Connect service manual

s-chap8-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 8-1

Configuration of NOEMI in HSC

NOEMI - Configuration

8 Configuration of NOEMI in HSC

NOEMI interface is part of the PBX-module of HSC.

NOEMI communicates directly with the switch (for call accounting, authorization changeover and display language).

Figure 8-1 HSC Maintenance, NOEMI Interface

8.1 NOEMI - Configuration

For call accounting, authorization changeover and display language on end devices the NOEMI interface (NOrmalized Equipment Messaging Interface) serves as a direct connection from the HSC server to the switch and must be configured in accordance with the switch version.

> The configuration of NOEMI is effective after restart of the server!

Page 99: HSC Connect service manual

Configuration of NOEMI in HSC

A31003-E1325-S100-3-7620, 01-20128-2 HSC V2.6, Service Manual

s-chap8-V26_en.fm

NOEMI - Configuration

Figure 8-2 HSC-Maintenance, Interface NOEMI

The Edit ... button can only be used when the switch is activated and it opens a subsequent window for editing the parameters.

If you assume inconsistencies in the extension data of HSC and HiPath, you can perform a synchronisation of the extension data of HSC and HiPath by means of the Synchronize button. In a subsequent window you have to decide in which direction you want to synchronize:

● In the direction HiPath --> HSC the current forwarding and DND settings are transferred to HSC.

● In the direction HSC --> HiPath the names assigned to the extensions and the COS settings are transferred to the HiPath. (If, however, no name is assigned to an administrative extension in the HSC system this has no effect on the HiPath data!)

By clicking Close you leave the window.

Page 100: HSC Connect service manual

s-chap8-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 8-3

Configuration of NOEMI in HSC

NOEMI - Configuration

8.1.1 HiPath 4000

Figure 8-3 NOEMI, HiPath 4000

This window contains the following areas and fields:

General

Host name/ IP address

Host name or IP address of HiPath 4000

Languages

Listbox of languages which can be selected for entering the AMOs in HiPath

Page 101: HSC Connect service manual

Configuration of NOEMI in HSC

A31003-E1325-S100-3-7620, 01-20128-4 HSC V2.6, Service Manual

s-chap8-V26_en.fm

NOEMI - Configuration

AMO link

Login service

Communication parameter for the login of an application (HSC) at HiPath; the default values are from the AMOs of the configuration batch.

Login Data

Communication parameter for the login of an application (HSC) at HiPath; the default values are from the AMOs of the configuration batch.

Common login

Hicom FBT password; it is required for initializing the FAMOS link. It must be used when logging in via interface.

Password

Hicom AMO password; it is required for implementing certain AMOs.

CDR link

Charge Data Records - connection to the switch for transferring call accounting data

Login service

Communication parameter for the login of an application (HSC) at HiPath; the default values are from the AMOs of the configuration batch.

Login data

Communication parameter for the login of an application (HSC) at HiPath; the default values are from the AMOs of the configuration batch.

Active

With 'Active' you adjust that the call acounting link is active, i.e. HiPath transmits all call accounting data to HSC. If you deactivate this checkbox, a CDR direct connection can be set-up from HiPath to another system.

>All fields of the areas AMO link and CDR link are deactivated as long as the checkbox next to it, i.e. 'default' is activated. It is recommended to keep the default values, because they have been created by the AMOs of the configuration batch (configuration of HiPath). See Appendix A

> Principally Hipath can only use one accounting link, i.e. other call accounting products cannot retrieve HSC call data directly from HiPath at the same time.

Page 102: HSC Connect service manual

s-chap8-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 8-5

Configuration of NOEMI in HSC

NOEMI - Configuration

COS settings

Rights mode

Checkbox with the values "COS", LCOSS/LCOSD" or "Both"

2 default levels are preset:

Level 0: Lock is activated. Activation is triggered at each Check Out by means of the setting COS 2. The assigned icon is displayed in call control.

Level 1: Lock is deactivated. Deactivation is triggered at each Check In by means of the COS 7 setting. The assigned icon is displayed in call control.

The Add... button opens a subsequent window for entering a new COS/LCOS setting. The Edit... button also opens a subsequent window for changing the parameters. The Delete... button deletes the selected COS/LCOS setting. The arrows up and down change the order (level 0, 1, etc.).

Add COS/LCOS setting

All in NOEMI defined COS/LCOS are to be configured in HiPath too!

Figure 8-4 NOEMI, Add COS/LCOS

Level

Depending on the number of already existing levels, the next higher level will be suggested automatically. However this order can be changed by using the arrows.

Name

> If more than 2 COS/LCOS are configured HSC uses the lowest one for Check In and the highest one for Check Out! Overall you can configure up to 16 levels.

Page 103: HSC Connect service manual

Configuration of NOEMI in HSC

A31003-E1325-S100-3-7620, 01-20128-6 HSC V2.6, Service Manual

s-chap8-V26_en.fm

NOEMI - Configuration

Editable listbox for defining the name of the level; this name will be displayed in Call Control (see User Guide, Chapter 4).

Icon

You can select an icon for the level; it will be displayed in Call Control.

COS

Class of Service; listbox for defining the number of the authorization class

LCOSS/LCOSD

Lower Class of Service; listbox for defining the number of the authorization class (both for LCOSS and for LCOSD!)

8.1.2 Multiple HiPath 4000

If multiple HiPath 4000 are used you can configure the HiPath language for the AMOs and the COS settings for all switches at once. The name, IP address as well as the data for AMO and CDR link are to be entered separately for each switch.

Figure 8-5 NOEMI, Multiple HiPath 4000

Page 104: HSC Connect service manual

s-chap8-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 8-7

Configuration of NOEMI in HSC

NOEMI - Configuration

A detailed field description you find in Section 8.1.1.

8.1.3 HiPath 3000 / OpenScape Office / OpenScape Business

Figure 8-6 Interfaces - NOEMI - HiPath 3000 / OpenScape Office Configuration

Page 105: HSC Connect service manual

Configuration of NOEMI in HSC

A31003-E1325-S100-3-7620, 01-20128-8 HSC V2.6, Service Manual

s-chap8-V26_en.fm

NOEMI - Configuration

In this window you can add several HiPath 3000 / OpenScape Office / OpenScape Business interfaces (by clicking the Edit button).The Edit... button opens the following dialog (see Figure 8-7).

If you assume inconsistencies in the extension data of HSC and HiPath, you can perform a synchronisation of the extension data of HSC and HiPath by means of the Synchronize button. In a subsequent window you have to decide in which direction you want to synchronize:

● In the direction HiPath --> HSC the current forwarding and DND settings are transferred to HSC.

● In the direction HSC --> HiPath the names assigned to the extensions and the COS settings are transferred to the HiPath. (If, however, no name is assigned to an administrative extension in the HSC system this has no effect on the HiPath data!)

By clicking Close you leave the window.

In the subsequent window you have tor specify the HiPath 3000 / OpenScape Office access data and carry out the COS settings.

Figure 8-7 Interfaces - NOEMI - Add or Configure new HiPath 3000 / OpenScape Office / OpenScape Business Connection

Page 106: HSC Connect service manual

s-chap8-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 8-9

Configuration of NOEMI in HSC

NOEMI - Configuration

The Add... button opens a subsequent window for entering a new connection.The Edit... button can only be activated if a Connection is selected and also opens a subsequent window for changing the parameters.The Delete button deletes the selected Connection.

General

Name

This HSC Connection name will be displayed at the HSC user interface!

Connection disabled

Temporally disable this connection!

Page 107: HSC Connect service manual

Configuration of NOEMI in HSC

A31003-E1325-S100-3-7620, 01-20128-10 HSC V2.6, Service Manual

s-chap8-V26_en.fm

NOEMI - Configuration

Use CSTA2 for CDR

Required for old PBX systems without CSTA3 support!

CDR use access code for trunk

Accounting based on access code instead of trunk line!

Disable data services

Disable data services on HiPath 3000 / OpenScape Office / OpenScape Business when voice link is used instead!

Using CAP

This checkbox must not be activated for HiPath 3000 / OpenScape Office / OpenScape Business!

IP address

Enter the IP address of HiPath 3000 / OpenScape Office / OpenScape Business.

Port

Enter the port where HSC shall transmit certain commands for HiPath 3000 / OpenScape Office (default: 7001 for HiPath 3000, 8800 for OpenScape Office and OpenScape Business).

User name

Enter the user name for authentication of HSC at HiPath 3000 / OpenScape Office / OpenScape Business (default: 070397).

Password

Enter the password for authentication of HSC at HiPath 3000 / OpenScape Office / OpenScape Business (default: 070397).

CDR TCP server active (replaces CSTA)

This checkbox must be activated for OpenScape Business.

CDR TCP listen port

Enter the port on which HSC will collect CDR data from OpenScape Business.

>The fields Port and Password are deactivated as long as the checkbox next to it, i.e. Default is activated. For OpenScape Business Booster Card or Booster Server is required for CSTA connectivity. CSTA Interface for OpenScape Business must be activated in OpenScape Business Assistant -> Expert mode -> Middleware -> CSTA Service Provider (CSP).

Page 108: HSC Connect service manual

s-chap8-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 8-11

Configuration of NOEMI in HSC

NOEMI - Configuration

COS Settings

Here you can create all authorization classes (COS = Class of Service):

The Add... button opens a subsequent window for entering a new COS setting. The Edit... button can only be activated if a Level is selected and also opens a subsequent window for changing the parameters.The Delete button deletes the selected COS. The arrows up and down change the order of COS (level 0, 1, etc.).

Figure 8-8 Interfaces - NOEMI - COS Settings

Here you can define how a COS is to be displayed at the HSC user interface and to which authorization class at HiPath 3000 / OpenScape Office it shall correspond:

Level

Depending on the number of already existing levels, the next higher level will be suggested automatically. However, this order can be changed by using the arrow buttons.

Name

This name will be displayed at the HSC user interface.

Icon

This icon will be displayed at the HSC user interface.

COS

Define the number of the authorization class that has to be selected at HiPath 3000 /OpenScape Office / OpenScape Business, if an extension is configured for this COS at the HSC user interface.

Assignment of Extensions

All extension numbers must be assigned to one switch!

Page 109: HSC Connect service manual

Configuration of NOEMI in HSC

A31003-E1325-S100-3-7620, 01-20128-12 HSC V2.6, Service Manual

s-chap8-V26_en.fm

Activate VoIP

Figure 8-9 Interfaces - NOEMI - Assignment of Extensions

8.2 Activate VoIP

Precondition for establishing VoIP connection is activated license for sufficient number of simultaneous calls (B channels). In order to activate VoIP navigate to Administration > Activate VoIP menu. VoIP and ISDN CAPI connectivity cannot operate simultaneously, please confirm Configuration warning.

Figure 8-10 Activate VoIP - Configuration Warning

First you have to enter basic settings:

● VoIP port (default value 5060)

Page 110: HSC Connect service manual

s-chap8-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual 8-13

Configuration of NOEMI in HSC

Activate VoIP

● Local IP (HSC server IP address used for VoIP connectivity to HiPath 3000 / OpenScape Office)

● Default user (normally first configured SIP subscriber)

● Info on remote disconnect (please don't change default value 0)

● Send info on remote disconnect (please don't change default value 1)

● CAPI debug (debug level, it is recommended to keep default value 0, only enable when facing problems)

● CAPI log data messages (relevant only for development purposes, it is recommended to keep default value 0)

● SIP debug (debug level, it is recommended to keep default value 0, only enable when facing problems)

● Debug logs path (path where debug logs are stored)

● RTP port start (it is recommended to keep default value 10000)

● RTP port end (it is recommended to keep default value 10020)

● G711 codec (please don't change default value 0)

Figure 8-11 Activate VoIP - General Settings

Page 111: HSC Connect service manual

Configuration of NOEMI in HSC

A31003-E1325-S100-3-7620, 01-20128-14 HSC V2.6, Service Manual

s-chap8-V26_en.fm

Activate VoIP

Then configure each individual extension with settings as defined in Section 3.2.5, “SIP extensions for HSC”

DTMF mode for SIP user has to be rfc2833.

Figure 8-12 Activate VoIP - SIP extension settings

Page 112: HSC Connect service manual

s-appA-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual A-1

Appendix A - HiPath 4000 Configuration

Example of a Configuration Batch

A Appendix A - HiPath 4000 Configuration

The sections below give an example of a HiPath-4000 configuration batch and provide information of configuration measures for Service Tracking using CMI and System telephones (optiPoint, OpenStage and OpenScape Desk).

A.1 Example of a Configuration Batch

Configuration batch HiPath 4000:

CHANGE-FEASU:A,CDROGTR;

CHANGE-FEASU:D,CDRE;

*CPTP: Configure DVA-connections */

ADD-CPTP:DPCON,55,"PROCID5","1.81.11.110";

ADD-CPTP:APPL,55,"ACM55","PROCID5","APPL55",YES,102,102,"ACM55","APPL55";

/* Set up ACL-Manager */

ADD-ACMSM:A1,55,ACLAPPL,"APPL55","ACM55","PROCID55",CB,"CSTAGW",Y,1020,1020;

/* Set-up and adapt X-applications

ADD-XAPPL:55,"APPL55","APPLICATION_55";

CHANGE-XAPPL:SUBAPPL,55,D25,ACCOUNT&AGASSIGN&AGENT;

CHANGE-XAPPL:SUBAPPL,55,D25,ABANDON&QUEUED&REDIRECT&LOGON;

CHANGE-XAPPL:SUBAPPL,55,D25,RCGDISC&RCGSEL& FEATSTAT;

CHANGE-XAPPL:MONCB,55,D25,RCG;

>This configuration batch is only an example for the configuration of a HiPath4000, which depends on systems and local requirements, and therefore does not constitute a generally applicable solution! This is why it must only be used or modified by service engineers with (HiPath) experience. You will find the configuration batch as ’Configuration batch HiPath4000en.txt’ without any comments on the HSC installation CD under /Tools.

Page 113: HSC Connect service manual

Appendix A - HiPath 4000 Configuration

A31003-E1325-S100-3-7620, 01-2012A-2 HSC V2.6, Service Manual

s-appA-V26_en.fm

Example of a Configuration Batch

/* CPTP: Assign applications to DVA connections */

ADD-CPTP:DPCON,111,"WC_PC","1.81.11.110";

ADD-CPTP:APPL,113,"TCPGUE","WC_PC","TCPGUE",YES,102,5002,"SRC5002","DST5002";

ADD-CPTP:APPL,114,"FAMOS","WC_PC","FAMOS",YES,102,5003,"SRC5003","DST5003";

/* Activate FAMOS */

ACTIVATE-FAMOS:FAMOS;

ACTIVATE-FAMOS:PROT;

ACTIVATE-FAMOS:RESTART;

/*Set up call accounting link*/

EINRICHTEN-FBTID:00,"0000000","00000","IDENTIFIKATION"," "," "," ";

AMO-FBTID is used for setting up data for remote connection establishment between Hicom and Service Center (SC). The data are set up in the operation and data server (ADS) of Hicom by means of the AMO FBTID.

Data are entered by means of parameters: Branch (KENNUNG), contract number (NR), position number of the contract (POSITION), password (PASSWORD), product designation (PRODUCT), customer name (NAME) and call number of the Hicom terminal (TLNNR)

ADD-FEACG:CDRCDUMP&CDRCDIS&CDRSPR;

Used for defining how data should be retrieved!

/*EINRICHTEN-FBTN:TN,1,1,103,1,0&&2,1031; (nicht zwingend erforderlich)

Separate entry for each trunk circuit (not obligatory for HSC to function). An assignment of trunk circuit number to virtual trunk circuit number is entered.

ADD-GEZU:DP,DP,V24HDLC,HDLC,"TCPGUE ","WC_PC ","TCPGUE ";

It is the task of this AMO to manage the device assignment tables. These include the assignment of symbolic device names (charge accounting device names) to physical device names.

Create selection groups - selection group 1:

Set filters to group 1, Data (format in accordance with table 08) are then sent to DVA:

ADD-SELG:SELG,1,N,DPS,NODEV,1,0;

Page 114: HSC Connect service manual

s-appA-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual A-3

Appendix A - HiPath 4000 Configuration

Example of a Configuration Batch

CHANGE-SELG:SELT,1,1,FORM08,NOFORM,NOCALC,A22;

CHANGE-SELG:SELT,1,1,,,,,0&&15;

CHANGE-SELG:SELT,1,1,,,,,,VOICE&FAX&DTE;

CHANGE-SELG:SELT,1,1,,,,,,,0&&15;

CHANGE-SELG:SELT,1,1,,,,,,,,ALL,ALL,N,N,N,N,N,Y,N,N,N,N,N,N,N,N,N,N,N;

CHANGE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,0,000000;

CHANGE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0&&999,0&&254,0&&30;

CHANGE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,N,N,OUTG,0&&8,1&&8,ALL;

ACTIVATE-SELS:1;

Format table 08:(18 fields in the data set are filled in, in accordance with the format of text string 1st and 2nd AMO line)

ADD-FTBL:8,B,FORM,1,N,"GUE0030#@#@#@#@#@#@#@#@#@#@#@#@#@@@@@#@@@#@@@@@@@@";

ADD-FTBL:8,B,FORM,2,N,"@@@@@@@#@@@#@@@@@@@@@@@#@@@";

ADD-FTBL:8,B,CTRL,3,N,LF;

ADD-FTBL:8,B,CTRL,4,Y,CR;

ADD-FTBL:8,B,FIELD,1,STYEAR,CHAR,"0",R;

ADD-FTBL:8,B,FIELD,2,STMONTH,CHAR,"0",R;

ADD-FTBL:8,B,FIELD,3,STDAY,CHAR,"0",R;

ADD-FTBL:8,B,FIELD,4,STHOUR,CHAR,"0",R;

ADD-FTBL:8,B,FIELD,5,STMIN,CHAR,"0",R;

ADD-FTBL:8,B,FIELD,6,STSEC,CHAR,"0",R;

ADD-FTBL:8,B,FIELD,7,ENDYEAR,CHAR,"0",R;

ADD-FTBL:8,B,FIELD,8,ENDMONTH,CHAR,"0",R;

ADD-FTBL:8,B,FIELD,9,ENDDAY,CHAR,"0",R;

ADD-FTBL:8,B,FIELD,10,ENDHOUR,CHAR,"0",R;

ADD-FTBL:8,B,FIELD,11,ENDMIN,CHAR,"0",R;

ADD-FTBL:8,B,FIELD,12,ENDSEC,CHAR,"0",R;

Page 115: HSC Connect service manual

Appendix A - HiPath 4000 Configuration

A31003-E1325-S100-3-7620, 01-2012A-4 HSC V2.6, Service Manual

s-appA-V26_en.fm

Example of a Configuration Batch

ADD-FTBL:8,B,FIELD,13,CHRGEE,CHAR," ",L;

ADD-FTBL:8,B,FIELD,14,CHRGUNIT,CHAR,"0",R;

ADD-FTBL:8,B,FIELD,15,DESTPTY,CHAR," ",L;

ADD-FTBL:8,B,FIELD,16,TKNOLIST,CHAR,"0",R;

ADD-FTBL:8,B,FIELD,17,PIN,CHAR," ",L;

ADD-FTBL:8,B,FIELD,18,ROUTCC,CHAR," ",L;

For using call access code field ROUTCC on Hipath 4000 in CDR output, this is an example of AMO output:

DISPLAY-TEXT:ROUTCC;

H500: AMO TEXT STARTED

OUTPUT TEXTS FOR ROUTING-CODES

SYMBOLIC NAME(call number) OUTPUT TEXT(what will be output to ROUTCC field)

0 0 067 30 068 69 069 69 0672 20 0673 20 0674 20 0675 20 0676 20 0677 20 0678 20

It is also possible to use DISA to add additional digits to the ROUTCC field.

Another way is to use TRKNOLIST field on Hipath 4000 in CDR output. This is selectable in HSC by checking the "Use trunk code" checkbox in Noemi 4000 CDR settings.

TRKNO is a freely selectable trunk identifier and can be applied the same value to multiple trunks. It provides an option to identify

Page 116: HSC Connect service manual

s-appA-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual A-5

Appendix A - HiPath 4000 Configuration

Settings for Call Queue

the trunk device, that was used to complete the call. For example on LCR overflow, the call could be completed through the more expensive provider, so it would have to be charged accordingly.

For that ADD-FBTN:TRKNO must be used to define the trunk number, that will be visible on CDR output in TKNOLIST.

This field is 4 chars long in the output string, but HSC will only take last three digits. Example TRKNO:1234 -> 234 in HSC

A.2 Settings for Call Queue

HSC offers a license for the service of a call queue indication for Call Control. But also if a 3rd party call center is used, HSC will show at least the number of waiting calls in the Call Control Center, either in numbers or as a bar (to be set under Administration > System > Settings; see Administration Manual, Section 4.4).

Preconditions:

● ACD routing in HiPath 4000

In HiPath 4000 ACD routing has to be configured, so that incoming calls are routed to an RCG over a access number (AMO DNIT), and from there via layer settings and calendar routing to the ACD routing table where the call is then queued into an ACD group. (This is standard ACD routing of HiPath 4000 and included in the original documentation of HiPath!)

● Configure RCG in CAP (step 1), see below

● Activate SAT service in CAP (step 2).

● Configure access number (DNIT) in HSC as extension of physical type 'Queue' (step 3), see below

1. Configure RCG in CAP (step 1)

In CAP you need the device of the type RCG, which has been used to route incoming calls into the system. The easiest way to do this is to import the device into CAP by means of a csv-file. This file can be created as follows:

– Export the devices, clear all the lines but one, and change the following values:

In the 'Extension' row the call number of the RCG.

In the 'DeviceId' row the call number + prefix of the RCG.

In the 'DeviceType' row 'RCG'.

In the 'PBX format' row add 33554432 (2^25) to the RCG number of HiPath.

Page 117: HSC Connect service manual

Appendix A - HiPath 4000 Configuration

A31003-E1325-S100-3-7620, 01-2012A-6 HSC V2.6, Service Manual

s-appA-V26_en.fm

Settings for Call Queue

Example: If it is the RCG 100 that is monitored the result will be the value 33554532 (33554432 + 100 = 33554532) in PBX format.

– Save this csv-file and import it.

There is also another method for configuring an RCG in the CAP (described in the CAP original documentation). However, when using this method a great amount of additional, unnecessary data will be imported!

2. Activate SAT service in CAP (step 2)

For the activation of SAT service see the description of CAP installation and configuration.

3. Configure access number (DNIT) in HSC as extension of physical type 'call queue' (step 3)

The extension number 75520 is the ACD access number which refers to RCG.

Figure A-1 Configure Extension as Call Queue

> For each RCG only one access number can be assigned (monitored) in HSC!

Page 118: HSC Connect service manual

s-appA-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual A-7

Appendix A - HiPath 4000 Configuration

Name Key Configuration for Service Tracking via Cordless Phone

A.3 Name Key Configuration for Service Tracking via Cordless Phone

The following configuration steps have to be made for Service Tracking via cordless phones (CMI).

Set up two name keys for each Service Tracking user (service attendant) on his/her cordless phone:

CHANGE-TAPRO:<STN>,,,,,,,,,NA,,NA;

Set the write protection for the name key:

AMO ZIEL (Parameter PROTECT=YES).

All cordless phones need to be correctly configured in the CAT tool of the HiPath switch (“Store calls: DTB with call logging“).

Key 9 and 11 must be configured as name keys with the following targets and with shortcut ’53’ (for key 9) and shortcut ’5’ or ’55’ (for key 11) (see also Section 3.2.1 and Section 3.2.2):

ADD-ZIEL:NA,<STN>,9,C15C13<APPLID>,,,YES;APPLID=900

ADD-ZIEL:NA,<STN>,11,C15C13<APPLID>,,,YES;APPLID=900

In the HSC administration under Administration > General Settings > Extension (see Administration Manual, Section 3.3, "Extension") the physical device type "DECT cordless phone" has to be set for the respective extensions.

A.4 Name Key Configuration for Service Tracking via OpenStage

For Service Tracking via OpenStages, a name key has to be configured in the same way as for cordless phones. Any available OpenStage key can be used.

Set up a name key for each Service Tracking user (service attendant) on his/her OpenStage

CHANGE-TAPRO:<STN>,,,NA;

Set the write protection for the name key (to avoid individual programming of the name key by the user):

Page 119: HSC Connect service manual

Appendix A - HiPath 4000 Configuration

A31003-E1325-S100-3-7620, 01-2012A-8 HSC V2.6, Service Manual

s-appA-V26_en.fm

Name Key Configuration for Service Tracking via OpenStage

AMO ZIEL (Parameter PROTECT=YES).

An available OpenStage key of your choice must be configured as name key with the following target and with shortcut ’5’ or ’55’ (see also Section 3.2.2):

ADD-ZIEL:NA,<STN>,<KEYNO>,C15C13<APPLID>,,,YES;APPLID=900

The same number has to be configured as LED number for the OpenStage device (i.e. key number = LED number !) in the HSC administration under Administration > General Settings > Employee (see Administration Manual, Section 3.4, "Employee").

Moreover, in the HSC administration under Administration > General Settings > Extension (see Administration Manual, Section 3.3, "Extension") the physical device type "OpenStage" has to be set for the respective extensions.

Page 120: HSC Connect service manual

s-appB-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual B-1

Appendix B - Importing a New Graphical User Interface Language into HSC

Localization of the HSC Graphical User Interface

B Appendix B - Importing a New Graphical User Interface Language into HSC

In order to integrate a new language into HSC V2.6, Professional Services has to perform the work steps described below:

● Localization of the entire graphical user interface of HSC

● Localization of the reports of the Management Information System and the work order lists

● Generation of an online help in the language newly integrated into the HSC system, if applicable

B.1 Localization of the HSC Graphical User Interface

The integration of a GUI language in HSC V2.6 is performed in three steps and tool-supported:

1. First extend the HSC localization file localisation.xls, which can be found in the directory ...\HSC\PostgreSQL\HSCScripts and, by default, contains 5 columns:

– Ignore the first two columns (status, warning).

– The third column (key) contains the localization key for HSC Front Office (incl. Management Information System) and HSC Maintenance.

– In the fourth column (en) you will find the English texts, in the fifth column (de) the German texts.

To add a new language, add a 6th column to the HSC localization file and enter the two-digit ISO code of the new language into the header of this column (e.g. "zh" for Chinese, cf. Figure B-1).

>The work steps described in this Appendix are offered and approved solely for integration of a new language into the HSC system, but not for changing the delivered standard localization for English and German. Such changes are not allowed in the HSC system, therefore they will not be supported (exception: localization of work order lists and MIS reports; see Administration Manual, Chapter 9) and have the following consequences:● The online help can no longer be used since it no longer corresponds to the

graphical user interface.● Upon upgrade to a new HSC version all manual changes at the standard

localization are overwritten.

Page 121: HSC Connect service manual

Appendix B - Importing a New Graphical User Interface Language into HSC

A31003-E1325-S100-3-7620, 01-2012B-2 HSC V2.6, Service Manual

s-appB-V26_en.fm

Localization of the HSC Graphical User Interface

.

Figure B-1 Extract from the Localization File (with the New Language Column Added)

Now enter the translation of all existing texts (from the columns 4 and 5) in this 6th column into your new language!

2. When you have completely filled in the 6th column in localisation.xls, export the entire table from the HSC localization file into what are called "language files".

For this purpose use the batch file lang_export.bat (stored in the directory ...\HSC\PostgreSQL\HSCScripts), which is part of the scope of delivery. After the export you can ignore the newly generated language files for English (HSC_en.lan) and German (HSC_de.lan), as they have existed already before.Only the new language file HSC_<lg>.lan (<lg> = two-digit ISO-Code of the new language) is of interest for you, since this language file can now be imported on the HSC server (i.e. it has to be written into a HSC database table).

3. For this import you just have to modify the supplied batch file import_language.bat (also stored in the directory ...\HSC\PostgreSQL\HSCScripts), by adding, for example, the lines:

java -cp %LIB1%\mysql.jar;localisation.jar

com.siemens.pse.HSC.core.util.localisation.Runner import HSC_XX.lan 30000

If Chinese is integrated, the batch file might look as follows:

>Make sure that the ISO code of the new language has also been included by means of HSC administration functions (menu Administration > International > Language; see Administration Manual, Chapter 3).

Page 122: HSC Connect service manual

s-appB-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual B-3

Appendix B - Importing a New Graphical User Interface Language into HSC

Localization of Reports and Work Order Lists

@echo off

echo import language files

set LIB1=..\..\Tomcat\modules\HSC_datasource\WEB-INF\lib

java -cp %LIB1%\mysql.jar;localisation.jar

com.siemens.pse.HSC.core.util.localisation.Runner import HSC_en.lan 10000

java -cp %LIB1%\mysql.jar;localisation.jar

com.siemens.pse.HSC.core.util.localisation.Runner import HSC_de.lan 20000

java -cp %LIB1%\mysql.jar;localisation.jar

com.siemens.pse.HSC.core.util.localisation.Runner import HSC_zh.lan 30000

echo import language files done

The new language will only be available in the HSC system when you have restarted the HSC components on the server.

B.2 Localization of Reports and Work Order Lists

The conversion of the reports and work order lists available in the HSC system into a language that has been newly integrated into the HSC system will be performed completely correctly and automatically if the following preconditions are met:

● For all localization keys included in the HSC localization file a suitable value has to be entered in the column for the new language.

● Any changed or new reports and/or report templates must have been accurately imported into the HSC system in accordance with the rules described in Chapter 9 of the Administration Manual.

The definition and the change of reports (designation (title), filter criteria to be entered as parameters, layout and scope, …) is performed independently of the language. Adaptation to the current user interface language is performed by reference to the respective localization keys in the HSC localization file. For identical terms that are used both in the Front Office user interface and in the report (e.g. title, parameter names) also the same localization keys are used.

Page 123: HSC Connect service manual

Appendix B - Importing a New Graphical User Interface Language into HSC

A31003-E1325-S100-3-7620, 01-2012B-4 HSC V2.6, Service Manual

s-appB-V26_en.fm

Localization of Reports and Work Order Lists

Page 124: HSC Connect service manual

s-appC-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual C-1

Appendix C - Import of Mass Data by Tool

HSC V2.6 MasterData-Interface Tool

C Appendix C - Import of Mass Data by Tool

HSC offers the possibility to import and export large volumes of data (mass data) fast and easily, see Chapter 7.

For import of master data (such as hotel and employee data) the 'HSC V2.6 MasterData Interface Tool' is available (see below).

For the import of master data there are mostly two scenarios:

● On the one hand the transfer of master data in the framework of a new installation of HSC - for which this function has been designed.

● You can use the import function also when the master data has to be added to an existing HSC system on a larger scale (e.g. the modification of a hotel).

During export the data are transmitted into the database in the same way as if they had been entered over the administration interface of Front Office. This means that the same checks (dependencies, license conformity, etc.) are performed as in the use of the administration interface!

Other than in the administration interface, only new data can be added with the mass data import function, while existing ones cannot be changed or deleted. (The attempt to change already existing data is rejected by the system with the message "Entry already exists".)In this way it is prevented that the function of the HSC system is impaired after import.

C.1 HSC V2.6 MasterData-Interface Tool

The import of master data is most conveniently performed by means of the 'HSC V2.6 Master-

Data-Interface Tool'.

This tool supports you in the correct entry of master data with test logic and writes the processed entries into an XML file, by means of a schema (defined in an XSD file), which can be imported subsequently by using the import function in HSC maintenance into the HSC database (see Section 7.1)The procedure is described in detail on the start page. The entry on the individual sheets is mostly self-explanatory. For particularities see the subsequent chapters.

>For a successful import only the minimum data record has to be available. This is always available after HSC reinstallation and may be restored before or by application of the HSC-script ResetDatabase.bat (supplied in directory ..\HSC\PostgreSQL\HSCScripts)!

7The mass data import function is only used for adding of data that have not existed before. Existing data cannot be changed!

Page 125: HSC Connect service manual

Appendix C - Import of Mass Data by Tool

A31003-E1325-S100-3-7620, 01-2012C-2 HSC V2.6, Service Manual

s-appC-V26_en.fm

HSC V2.6 MasterData-Interface Tool

You will find the 'HSC V2.6 MasterData-Interface Tool' on installation CD1 under \Tools\ImportExportTool. The tool itself is only available in English, in the description the English and German terms are used.

Figure C-1 HSC V2.6 MasterData-Interface Tool - Start Page

● Step 1- Read data from an existing XML-File (optional)

> When opening the tools make sure to activate the macros, otherwise the functions of the tools will not be available to you.

Page 126: HSC Connect service manual

s-appC-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual C-3

Appendix C - Import of Mass Data by Tool

Description of sheets

This step is only provided for the case that you have already entered the master data in an XML file. In this way these data are imported from the XML file and stored in the individual Excel Sheets of this tool. Data already existing in the sheets are overwritten (at first a warning is issued)!

● Step 2 - Select the types of data you want to edit

Select one/several/all categories, where you want to edit the data. The respective sheets will then be made available.

Staff and telephone – data concerning employees, rooms and extensions

Service and department – data concerning service tracking and departments

Direct Call Buttons – Data relating to direct call buttons

● Step 3 - Edit Data

Enter or edit data in the displayed sheets.

● Step 4 - Write data from the Sheets into a XML-File

The entries from the sheets are written to an XML file.

● Step 5 - Import into HSC

For the description of the import using HSC Maintenance, see Section 7.1

C.2 Description of sheets

Depending on which sheets you have chosen under step 2, the respective sheets are made available. All of these sheets have the same structure and are modeled after the HSC user interface. Depending on the respective requirements they comprise the following elements:

● Every sheet has a button "Show Examples". If this button is pressed, a few lines with examples are displayed. With "Hide Examples" these lines are hidden.

● With "Validate" the correctness of the data is checked. Many checks are performed already during entry (e.g. exceeding of length, only digits in numeric fields, etc.). When data is imported from an XML file or filled with default values, this check cannot be performed during entry, but only by using the button "Validate".

● Every sheet has a line with Default Values. In the blue fields you can enter default values for the column below (only possible for those columns, where default values make sense).

With "Default All" the default values are entered in each used line of the sheet (only in empty cells; cells with content are not overwritten).

Page 127: HSC Connect service manual

Appendix C - Import of Mass Data by Tool

A31003-E1325-S100-3-7620, 01-2012C-4 HSC V2.6, Service Manual

s-appC-V26_en.fm

Description of sheets

With "Default Marked" the selected cells are filled with default values. If the selection exceeds the used final line of the sheet, the default values are included only until the last line used. This process cannot be reversed! In case of an error, the values have to be deleted manually and subsequently included again!The correctness of the entry is checked during the entry into the line in the same way as in a "normal" cell. During the copying of default values into the cells no check is performed. The correctness of the data can only be checked subsequently by pressing the "Validate" button.

● "—multiple—" means that there can be several entries for each key field in this column.

● The headings of key fields are marked yellow. If a key field is empty, it is assumed that the final key above is the valid key. Key fields have to be unique (they must only be used once per sheet). This is checked by means of Validate.

● If a Combo Box exists, it is recommended to choose a value from the combo box (instead of typing the value). In some cases it is mandatory to select a value from the Combo Box. IThere are 3 buttons below this box:

"Fill Next" (1 arrow): fills in the next empty line of the respective column with the selected value

"Fill All" (2 arrows): fills all empty lines of the respective column with the selected value (currently functioning is limited)

"Fill Marked Range" (M): fills the marked area with the selected value. Values can also be written into totally empty lines.

C.2.1 Sheet "Hotel"

Parameter

Hotel Name

– 60 characters max.

Group Brand

– 60 characters max.

Chain Company

– 60 characters max.

>All sheets are protected against unintentional deletion. Also entire lines and/or columns cannot be deleted or added. Elements, such as buttons, text entry fields, etc. cannot be changed.

Page 128: HSC Connect service manual

s-appC-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual C-5

Appendix C - Import of Mass Data by Tool

Description of sheets

Street

– 60 characters max.

ZIP Code

– 10 characters max.

City

– 60 characters max.

Country

– 60 characters max.

– only value from the combo box

Region

– 60 characters max.

Phone

– 60 characters max.

Fax

– 60 characters max.

E-Mail

– 60 characters max.

– Validity of the e-mail address is checked during entry.

C.2.2 Sheet "Extension"

This sheet contains both fields for "room" and for "extension".

If you want to create a room without extension, state "NO_EXT" in the "Extension" field.

If you want to create an extension without room, leave the "Room Number" field empty. (Contrary to other sheets the last known value is not automatically taken here !)

Some entries are already checked during the entry, other entries (in particular connections between the fields) are only checked when pressing "Validate".

Status information for rooms and extensions is NOT im/exported!

Parameter

Extension Number

Page 129: HSC Connect service manual

Appendix C - Import of Mass Data by Tool

A31003-E1325-S100-3-7620, 01-2012C-6 HSC V2.6, Service Manual

s-appC-V26_en.fm

Description of sheets

– Max. 10 characters (checked during entry)

– has to be unique

– must not be empty (to enter a room without extension, enter "NO_EXT" and leave all columns empty except for the room columns).

Logical Type

– Only value from the combo box (checked during entry)

– must not be empty (except for "NO_EXT")

Extension Prefix

– max. 30 characters (checked during entry)

– must only contain valid CAP-prefixes (checked during entry). It is checked whether the prefix contains invalid characters, however not the exact syntax of the prefix.

Permitted characters are: Digits from 0 – 9"<" and ">""<" and ">"the letters "N", "O" and "P""-" and "+"" " (blanks)

Physical Type

– Only value from the combo box (checked during entry)

– must not be empty (except for "NO_EXT")

Host name

– max. 60 characters (checked during entry)

– optionally, is only analyzed at logical type = "staff" and physical type = "Optiset"

Main number

– yes/no (checked during entry)

– Empty entry interpreted as "no".

Room number

– max. 60 characters (checked during entry)

– The same room must be assigned to several extensions

– The same rooms need not be written below each other (i.e. you can first enter e.g. all Optisets, then all DECTs and then all modems).

Page 130: HSC Connect service manual

s-appC-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual C-7

Appendix C - Import of Mass Data by Tool

Description of sheets

– An empty entry in the "Room Number" column is interpreted to mean that there is no room assigned to this device (e.g. in case of DECT-devices or RCGs, etc.). This is not the same as in other sheets!

– There are combinations of logical type and physical type for which a room number is obligatory (e.g. "room" and "Optiset"). This is checked by means of "Validate". (If a room number is stated, even though it is not required for this combination, the room itself is created, but not its relation to the extension).

– The Room Category and Is Room Bookable are stored when the room first comes up. All further entries are ignored (in case of "Validate" a warning with line number is shown).

Room Category

– max. 60 characters (checked during entry)

– may remain empty (room without category)

Is Room Bookable

– yes/no (checked during entry)

– without entry "no" is assumed

CAP-Extensions

– is displayed only after pressing the "Show CAP Entries" button

– In this column you can copy already existing CAP extensions. You can keep on using them by means of the "Assistant Extension" button (see below)

C.2.2.1 "Assistant Extensions" button

This assistant can be used in the following cases, if

● a list of CAP extensions to be exported exists

● a range of extensions shall be created.

In both cases a room can be generated automatically for each extension.

Extension Information

CAP Prefix

Example for a valid CAP prefix: “+43-51707-“

Logical Type

Select a Logical Type from the list

Physical Type

Page 131: HSC Connect service manual

Appendix C - Import of Mass Data by Tool

A31003-E1325-S100-3-7620, 01-2012C-8 HSC V2.6, Service Manual

s-appC-V26_en.fm

Description of sheets

Select a Physical Type from the list

Create Room from Extension

Select this option if you want to create a room together with the extensions automatically. "Rooms“ will be created by removing n characters from the start ('Length Extension Prefix') and n characters from the end ('Length Extension Postfix')_

Location of Extensions

Choose 'User CAP-entries from sheet' if you want to use CAP-entries stored in column “CAP-Extensions“ Choose “Create New Range“ if you want to create a new range of extensions

Room Information

Room Category

Enter the desired Room Category

Room Bookable

Select this option if the automatically created rooms shall be bookable

Length Extension Prefix

This number will be removed automatically from the beginning of the extension "Example: Extension = 3100, length of Prefix = 1 ==> Room-No = 100)

Length Extension Postfix

This number will be removed automatically from the end of the extensionExample: Extension = 1003, length of Postfix = 1 ==> Room-No = 100)

New Range

Range Start

Start value of the new range (inclusive). Minimum: 1

Range End

End value of the new range (inclusive). Minimum: value given in “Range End“

Step

The step between two rooms or extensions. Maximum: result of substraction: RangeEnd-RangeStart Example: Range = 100 - 110Step = 1 ==> 100, 101, 102, ..., 110 Step = 2 ==> 100, 102, 104, ....., 110

Page 132: HSC Connect service manual

s-appC-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual C-9

Appendix C - Import of Mass Data by Tool

Description of sheets

C.2.2.2 "Assistant Rooms" button

This assistant can be used if a range of rooms shall be created. For each room an extension can be generated automatically

Room Information

Room Category

Enter the desired Room Category

Room Bookable

Select this option if the automatically created rooms shall be bookable.

Create Extension from Room

Select this option if you want to automatically create an extension together with the rooms. Extensions will be created by adding the value given at “Extension Prefix“ at the beginning of the room number and the value given at “Extension Postfix“ at the end of the room number"

New Range

Range Start

Start value of the new range (inclusive). Minimum: 1

Range End

End value of the new range (inclusive). Minimum: value given in “Range End“

Step

The step between two rooms or extensions. Maximum: result of substraction: RangeEnd-RangeStart Example: Range = 100 - 110Step = 1 ==> 100, 101, 102, ..., 110 Step = 2 ==> 100, 102, 104, ..., 110

Extension Information

CAP Prefix

Example for a valid CAP-prefix: “+43-51707-“

Logical Type

Select a Logical Type from the list

Physical Type

Select a Physical Type from the list.

Page 133: HSC Connect service manual

Appendix C - Import of Mass Data by Tool

A31003-E1325-S100-3-7620, 01-2012C-10 HSC V2.6, Service Manual

s-appC-V26_en.fm

Description of sheets

Extension Prefix

The prefix given here is automatically added to the beginning of the room number to form an automatically created extension number, can be combined with Extension Postfix.

Extension Postfix

The postfix given here is automatically added to the end of the room-number to form an automatically created extension number, can be combined with ExtensionPrefix.

C.2.2.3 "Show/Hide CAP Entries" button

There is a column where you can enter and/or copy CAP extensions. This button shows/hides this column.

C.2.3 Sheet "Room Facility"

Parameter

Room Number

– max. 60 characters (checked during entry)

– A line without room number must not contain a "Facility Name" and a "Facility Value".

– A value from the combo box can be selected (in case the room number does not exist, a warning will be issued in the "Validate" procedure).

Facility Name (--multiple--)

– max. 255 characters (checked during entry)

Facility Value (--multiple--)

– max. 255 characters (checked during entry)

C.2.4 Sheet "Emergency Call"

Parameter

Emergency Call

– 255 characters max.

C.2.5 Sheet "Department"

Parameter

Page 134: HSC Connect service manual

s-appC-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual C-11

Appendix C - Import of Mass Data by Tool

Description of sheets

Name

– 60 characters max.

– can have several categories

– If a department has several categories, this column can remain empty until the next department comes up. It is possible to state the same department with another category further down below once again.

– It is also possible to enter a department without category. Then the other columns will remain empty.

Category (-- multiple --)

– 60 characters max.

– Each combination department/category has to be unique.

– Each category has to be unique (a category must not be assigned to 2 departments)

Relevant for Service Tracking" (-- multiple --)

– yes/no

– Only relevant for category

C.2.6 Sheet "Service Type"

Parameter

Name

– 60 characters max.

Submittable

– yes/no

C.2.7 Sheet "ServiceText"

Parameter

Service Code

– 10 characters max.

– must be unique

Service Text

– 60 characters max.

Page 135: HSC Connect service manual

Appendix C - Import of Mass Data by Tool

A31003-E1325-S100-3-7620, 01-2012C-12 HSC V2.6, Service Manual

s-appC-V26_en.fm

Description of sheets

Acceptance Timeout

– Numeric value

Execution Timeout

– Numeric value

Category (-- multiple --)

– Possible values: all categories from the "Department" sheet. Value from the combo box, but not mandatory. If a category does not exist, a warning is issued during the "validate" process.

– The priority of the department is specified by means of the order in which they are created in the Excel Sheet. The further above in the sheet a category is positioned, the higher its priority (1 = highest priority).

Service Type (-- multiple --)

– Possible values: All service types from the sheet "service type"Value from the combo box, but not mandatory. If a service type does not exist, a warning is issued during the "validate" process.

– Category and service type are independent of each other. It is possible that 3 categories are allocated to a service code but only 1 service type. In this case only 1 line is filled in for service type, for department, however, 3.

C.2.8 Sheet "Satisfaction Level"

Parameter

Name

– 60 characters max.

– has to be unique

– A "name" without "level" is not permitted.

Ranking

– Numeric value between 1 and 10

– has to be unique

– A "ranking" without "name" is not permitted.

C.2.9 Sheet "Roles"

Parameter

Page 136: HSC Connect service manual

s-appC-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual C-13

Appendix C - Import of Mass Data by Tool

Description of sheets

Role Name

– 30 characters max.

– It is also possible that a "role" has no "rights".

Rights (-- multiple --)

– Only value from the combo box (checked during entry)

– The combination role – rights must be unique

Predefined Roles (can be shown/hidden by means of button)

– Roles already predefined in HSC

C.2.10 Sheet "Employees"

If a non-multiple field (e.g.: "Service Attendant Id") exists several times for one employee, a warning is issued.

Parameters

First Name

– max. 255 characters (checked during entry)

– Forms the key together with the "Surname"

Middle Name

– 255 characters max.

Surname

– 255 characters max.

– obligatory (if empty, the value above is taken automatically (checked during the "validate" process).

– forms the key together with first name(combination "First Name/Surname" must be unique).

Title

– 255 characters max.

Country

– only value from the combo box (checked during entry)

– obligatory (checked by means of "Validate".

Salutation

Page 137: HSC Connect service manual

Appendix C - Import of Mass Data by Tool

A31003-E1325-S100-3-7620, 01-2012C-14 HSC V2.6, Service Manual

s-appC-V26_en.fm

Description of sheets

– 255 characters max.

Language (--multiple--)

– only value from the combo box (checked during entry)

Is Service Attendant

– yes/no (checked during entry)

– default value "no"

Identification Code

– numeric (checked during entry)

Category (-- multiple --)

– max. 60 characters (checked during entry)

– value from the combo box, but not mandatory. If a category does not exist, a warning is issued during the "validate" process.

User Account Name (--multiple--)

– max. 60 characters (checked during entry)

– If this entry is missing, the entire line is not written to the XML file ("validate" issues a warning).

– The following multiple fields belong together: User Account Name, User Account Role, Passwort, PIN

With "Default All" and "Default Marked" default values are only filled, if a value is stated in the cell "User Account Name".

User Account Role (--multiple--)

– value from the combo box, but not mandatory. If a role does not exist, a warning is issued during the "validate" process.

Password (--multiple--)

– max. 60 characters (checked during entry)

– Obligatory if there is a user account for this employee (checked during "Validate")

– For security reasons this column is not filled in if XML files are read ("Select XML file"). The password has to be entered manually.

PIN (--multiple--)

– numeric (checked during entry)

Page 138: HSC Connect service manual

s-appC-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual C-15

Appendix C - Import of Mass Data by Tool

Description of sheets

– For security reasons this column is not filled in if XML files are read ("Select XML file"). The PIN has to be entered manually.

Extension (-- multiple)

– max. 60 characters (checked during entry)

– Value from the combo box, but not mandatory. If an extension does not exist, a warning is issued during the "validate" process.

– If a phone channel is assigned to an employee, it is not necessary to enter it as extension (but it can be entered).

Transmission Route (--multiple--)

– Value from the combo box (checked during entry)

– The following multiple fields belong together: Transmission Route, Access Data, LED number

With "Default All" and "Default Marked", default values are only filled, if a value is stated in the cell "Transmission Route".

Access Data (--multiple--)

– 255 characters max.

– Obligatory at:PhoneE-Mail (syntax is not checked during entry but during "Validate")SMSKirk

LED Number (--multiple--)

– Obligatory for Transmission Route "Phone" (will be ignored otherwise)

C.2.11 Sheet "Direct Call"

Parameter

Username

– 60 characters max.

– Value from the combo box, but not mandatory. If a user name does not exist, a warning is issued during the "Validate" process.

– obligatory

– No contents: The last user name from above is takenNo contents in the first line: further contents of the line is ignored

Page 139: HSC Connect service manual

Appendix C - Import of Mass Data by Tool

A31003-E1325-S100-3-7620, 01-2012C-16 HSC V2.6, Service Manual

s-appC-V26_en.fm

Description of sheets

Tab name

– 60 characters max.

– obligatory

Name

– 60 characters max.

– obligatory

Phone

– 60 characters max.

– obligatory

– has to be unique for a user

Page 140: HSC Connect service manual

s_abb-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual Y-1

Nur für den internen Gebrauch List of Abbreviations

List of Abbreviations Y

This table shows some important abbreviations.

Abbreviation Definition

ACSE Application Control Service Element

AS Application Server

ATM Asynchronous Transfer Mode

BUM Berechtigungs-Umschaltung

CA Carrier

CAP Common Application Platform

CAPI Common Application Programming Interface

CCC Call Control Comments/Commands

CDP Charge Data Processing

CDR Charge Data Record

CLA Customer License Agent

CLM Customer License Management

CMI Cordless Multicell Integration

CR Change Request

CSTA Computer Supported Telecommunications Application

CTI Computer Telephony Integration

DND Do Not Disturb

DST Display Service Tracking

DUBAI Dedicated Universal Business Application Interface

FAMOS Fernadministration (Interface for HiPath)

GUI Graphical User Interface

HAC Hotel Attendant Console

HSC Hospitality Service Center

HLM HiPath License Management

HO Holiday

IIS Internet Information Services

Page 141: HSC Connect service manual

List of Abbreviations Nur für den internen Gebrauch

A31003-E1325-S100-3-7620, 01-2012Y-2 HSC V2.6, Service Manual

s_abb-V26_en.fm

IMAP Internet Message Access Protocol

IV Import Version

IVR Interactive Voice Response Unit

JRE Java Runtime Environment

MIS Management Information System, local manager

MWI Message Waiting Indicator

ODBC Open Database Connectivity

PABX Private Automatic Branch Exchange

PBX Private Branch Exchange

PDA Personal Digital Assistant

PLC Programmable Logical Controller

PMS Property Management System

RA Rate

RAM Random Access Memory

RCG Route Control Groups

SCC Service Control Center

SOAP Simple Object Access Protocol

SP Service Provider

TN Target Number

TS Tariff Structure

TZ Time Zone

UM Unified Messaging

VMS Voice Mail Server

Abbreviation Definition

Page 142: HSC Connect service manual

s_IX-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual Z-1

Nur für den internen Gebrauch Index

Index Z

AAccess number configuring A-6Adobe Acrobat Reader 2-3

CCall queue

configure access number A-6configuring RCG A-5settings A-5

CAPUpgrade 4-2

CDR link 3-4, 3-7, 8-4Change

GUI language 6-2Client

start 5-1problems 5-5without Internet Explorer 5-5

CMIname key configuration A-7

ConfigurationHiPath 3000 3-9HiPath 3000, multiple 3-10HiPath 4000 3-3HiPath 4000, multiple 3-5switch 3-3trace 6-12

Configuration batch, HiPath 4000 A-1Configuration data

export 7-9import 7-4

ConnectionHiPath 3000 - HSC 3-9HiPath 4000 - HSC 3-3multiple HiPath 3000 - HSC 3-11multiple HiPath 4000 - HSC 3-6

COS, HiPath 3000, OpenScape Office 8-11COS, LCOS 8-5Customize

GUI language 6-2

DData backup, HSC 4-4

EE-mail

gateway 3-31interface 3-31

Error analysis 6-1, 6-8Error recovery 6-8

GGUI language

new in HHSC B-1

HHardware requirements

HSC Client 2-2Help

HSC Maintenance 6-5HiPath 3000 3-9HiPath 3000, multiple 3-10HiPath 4000 3-3HiPath 4000, multiple 3-5Hotel Reward

configuration 3-28export 3-28import 3-29

HSCchoose destination location 3-24client start 5-1components 2-1data backup 4-4installation 3-24installation Linux 3-26languages 3-26server 2-1upgrade 4-4upgrade to an interim version 4-4

Page 143: HSC Connect service manual

Index Nur für den internen Gebrauch

A31003-E1325-S100-3-7620, 01-2012Z-2 HSC V2.6, Service Manual

s_IX-V26_en.fm

HSC Maintenanceadd trace topic 6-18configure trace 6-12define and activate trace 6-8edit trace topic 6-19functional overview 6-1Help 6-5interface status 6-7logger 6-20login 6-1menu bar 6-4message window 6-6navigation area 6-3right 6-2scroll lock 6-11show trace data 6-9structure of a trace entry 6-21trace level 6-18trace overview 6-14trace topic 6-13user interface 6-1working area 6-4

Human Resourceconfiguration 3-30export 3-30

IImport, mass data 7-1

by tool C-1Installation

HSC 3-24HSC Linux 3-26Java 5-1server 3-1steps for server installation 3-1

Interface status 6-7

JJava

disable automatical upgrade 5-3installation 5-1several versions 5-3

KKirk 3-33

LLanguage

change 6-2new GUI in HHSC B-1other languages in HSC 3-26

LCOSS/LCOSD 8-6LED number A-8License variants 2-3Licensing, HSC 3-26Localization

new GUI language B-1reports B-3restrictions B-1work order lists B-3

Logger 6-20Login

HSC Maintenance 6-1

MMaintenance 6-1Manual structure 1-2Manual target group 1-1Mass data 7-1

export 7-7import 7-1import by tool C-1

Master dataexport 7-9import 7-4

Menu barHSC Maintenance 6-4

Message windowHSC Maintenance 6-6

Migration 4-1MIS reports, upgrade 4-4

NName keys

configuration for CMI A-7configuration for Optiset A-7

Navigation areaHSC Maintenance 6-3

NOEMI 8-1HiPath 3000 8-7

Page 144: HSC Connect service manual

s_IX-V26_en.fm

A31003-E1325-S100-3-7620, 01-2012HSC V2.6, Service Manual Z-3

Nur für den internen Gebrauch Index

HiPath 4000 8-3multiple HiPath 4000 8-6

Notational Conventions 1-3

OOpenScape Xpressions Hotel

upgrade 4-3Optiset

name key configuration A-7

PPassword 6-2PBX-module 8-1Predefined trace topic 6-19Proxy settings 5-6

RRCG 3-4, 3-7

configuration A-5Restore 4-5Right

for HSC Maintenance 6-2

SScroll lock 6-11Server

hard- and software 2-1installation 3-1

Service TrackingLED number for Optiset A-8name key configuration

CMI A-7Optiset A-7

SMSgateway 3-32interface 3-31

SNMP 3-32Software requirements 2-1Structure of the manual 1-2Switch 3-3

configuration 3-3HiPath 3000 3-9HiPath 4000 3-3multiple HiPath 3000 3-10multiple HiPath 4000 3-5

TTarget group of the manual 1-1Trace

activate 6-8available HSC clients 6-13, 6-16configure 6-12define 6-8entry structure 6-21HSC-specific entry 6-21level 6-18overview 6-14

Trace datalocation 6-8show 6-9

Trace filemaximum index 6-13, 6-17maximum size 6-8, 6-13, 6-17

Trace topic 6-13add 6-18edit 6-19predefined 6-19

UUnique key 4-2Upgrade

CAP 4-2HSC to an interim version 4-4HSC V2.5 4-1MIS reports 4-4OpenScape Xpressions Hotel 4-3work order lists 4-4

VVirtual station

HiPath 3000 3-9, 3-11HiPath 4000 3-4, 3-6

WWork order lists, upgrade 4-4Working area

HSC Maintenance 6-4

XXML file C-2

Page 145: HSC Connect service manual

Index Nur für den internen Gebrauch

A31003-E1325-S100-3-7620, 01-2012Z-4 HSC V2.6, Service Manual

s_IX-V26_en.fm