Aranea Cem

Aranea - Installation and Configuration
Guide
1
Release date: 15/Jul/2009
PREFACE
This book is valid for Aranea release 1.4.3
NOTE THAT FOR NEW INSTALLATIONS OPENWORX IS NOT SUPPORTED

ANYMORE
2
Contents
1 INTRODUCTION TO ARANEA ................................................................ 5

1.1 INTRODUCTION................................................................................... 5
1.2 THE ARANEA ARCHITECTURE.............................................................. 6
1.3 USING ARANEA .................................................................................. 8
1.3.1 HOW TO START OR STOP A CONFIGURATION? ...................................... 8
1.3.2 HOW TO START A FULL SYNCHRONIZATION OF A CONFIGURATION?........ 8
1.3.3 HOW CAN I SEE THE PROGRESS OF A CONFIGURATION? ....................... 9
1.3.4 HOW TO CHANGE A CONFIGURATION? ............................................... 11
2 ARANEA REQUIREMENTS & INSTALLATION ......................................... 12
2.1 SYSTEM REQUIREMENTS .................................................................. 12
2.2 INSTALLATION OF ARANEA ................................................................ 13
2.2.1 INSTALLING ARANEA......................................................................... 13
2.2.2 UPGRADING ARANEA........................................................................ 24
2.2.3 UNINSTALLING ARANEA .................................................................... 25
3 STANDARD ARANEA CONFIGURATIONS .............................................. 28
3.1 BUSINESS CONNECT AND PHONEW ARE ........................................... 34
3.1.1 W HAT DATA IS SYNCHRONIZED? ........................................................ 34
3.1.2 CONFIGURATION PROCEDURE ........................................................... 34
3.2 BUSINESS CONNECT AND MA4000 .................................................. 39
3.3 OPENW ORX AND PHONEW ARE ........................................................ 45
3.4 CSV FILE AS DATA SOURCE .............................................................. 50
3.5 ACTIVE DIRECTORY AS DATA SOURCE ............................................... 56
3.6 FINISHING UP THE CONFIGURATION ................................................... 61
APPENDIX A. SYNCHRONIZED DATA FIELDS .............................................. 63
A.1. MAPPINGS BUSINESS CONNECT AND PHONEW ARE........................... 63
A.2. MAPPINGS BUSINESS CONNECT AND MA4000 ................................. 71
3
A.3. MAPPINGS CSV FILE AND BUSINESS CONNECT ................................ 78
A.4. MAPPINGS CSV FILE AND PHONEW ARE............................................ 85
A.5. MAPPINGS CSV FILE AND OPENW ORX ............................................. 91
A.6. MAPPINGS ACTIVE DIRECTORY AND BUSINESS CONNECT ................. 97
A.7. MAPPINGS ACTIVE DIRECTORY AND PHONEW ARE ........................... 105
A.8. MAPPINGS ACTIVE DIRECTORY AND OPENW ORX ............................ 112
A.9. MAPPINGS OPENW ORX AND PHONEW ARE ..................................... 119
APPENDIX B. CUSTOMIZING MAPPING SCRIPTS ....................................... 126
B.1. TRANSFORMATION MAPPING PROCESS ........................................... 127
B.2. EXAMPLE HOW TO CHANGE A MAPPING SCRIPT. ............................... 128
APPENDIX C. LDAP TERMINOLOGY ........................................................ 135
C.1. THE LDAP SYNTAX ........................................................................ 135
C.2. USING LDAP SYNTAX..................................................................... 135
APPENDIX D. ARANEA SUPPORT TOOLS ................................................. 138
D.1. DIAGNOSTIC MONITOR ................................................................... 138
D.2. SECURITY CONFIGURATOR ............................................................. 138
APPENDIX E. TROUBLESHOOTING .......................................................... 141
4
1 INTRODUCTION TO ARANEA
1.1 INTRODUCTION
Aranea is an add-on for networks that include the:
- PhoneWare Directory (SV60E/Management@Net Phonebook)
- OpenWorX 5.0
- United database (Business ConneCT 4.x and/or Management@Net 3.2)
- MA4000 7.x - 8.0
All of these databases contain contact-data. When two or more of these products are
present, Aranea can be used to synchronise the contacts. Furthermore Aranea can be used
to import and maintain contacts from external information sources (i.e. csv-files or Active
Directory).
Aranea 1.4.3 supports:

- Both initial (full) import as well as incremental import.
- Import of new contacts as well as changed and deleted contacts.
- Customizing which contact-data is imported from the source and how it is
mapped to the fields in the destination database.
Table 1: Possible configurations in Aranea 1.4.3
To
From Phonebook OpenworX1 BCT MA4000
Phonebook Yes Yes Via United
OpenworX1 Yes No No
BCT Yes No Yes
MA4000 Via United No Yes
CSV File Yes Yes Yes No
Active Yes Yes Yes No

Directory
1
Obsolete. OpenWorX is not supported for new installations anymore.
5
Aranea 1.4.3 does not support:
- Direct synchronization between MA4000 and OpenWorX/Phonebook.
- Synchronisation between OpenWorX and MA4000. Instead, use the build in
synchronisation of OpenWorX.
- Synchronisation between Active Directory/CSV File and MA4000. Instead, use
the build in synchronisation of MA4000.
1.2 THE ARANEA ARCHITECTURE

The global architecture of Aranea is shown in the following figure:
Figure 1: Global Architecture of Aranea
Each changed Source Directory record is processed by the Aranea Agent. After conversion
by a Transformation Script a corresponding Sink Directory record is changed.
The Transformation Script is written in VB-script, and can therefore easily be adapted by a
local NEC Philips or Third-Party Customer Engineer. Although this requires knowledge of
the database tables and programming experience in VB-scripting, only a text editor is
required. This provides for a very powerful and flexible customising of data mapping. The
6
Transformation Script is specific for each Directory combination and determines the
mapping between specific contact-data in the Source Directory and contact-data in the Sink
Directory. The Contact Source Component and Contact Sink Component are specific for
each type of Directory (database). These components contain the way the databases are
accessed (API or SQL queries) and the rules for adding, modifying or deleting records.
If Aranea is used with a Management@Net system, the Aranea Agent can also trigger the
@Net Data Distribution Module for distribution of Surname-NDNR data. This is required
for name distribution to the MAC-Manager and the Call Reporting Module.
After installation of Aranea, you can customize Aranea to suit the customer's environment
by using the Aranea Configurator. It allows for adaptations like database locations,
authorisations, indication of full/incremental import and so on. This program can be used
both at initial installation and for changes later on.
Aranea can run real time or as a periodical, time-scheduled job under Windows (once per
hour or day, for example), and therefore has no direct users.
7
1.3 USING ARANEA
1.3.1 How to start or stop a configuration?
Start the Aranea Configurator. Select a configuration from the List of configurations. From
menu, select Configurations, Status... and then Start or Stop. You can also Start or Stop by
clicking with the right mouse button on a configuration in the List of configurations.
Figure 2: Start / stop a configuration
1.3.2 How to start a Full synchronization of a configuration?
the menu, select Configurations and Full sync. You can also start a Full sync by clicking
with the right mouse button on a configuration in the List of configurations. This is necessary
Figure 3: Start Full Synchronization of a configuration.
8
during initial filling or after adding a new site.
1.3.3 How can I see the progress of a configuration?
From the Aranea Configurator menu, select View and Running tasks. Under the List of
configurations another box is opened. This box shows information if Aranea is taking an
action.
Figure 4: Running tasks show the progress of a configuration.
A task line consists of three parts:

- Status Icon. The status of the task. These can be:
- Waiting for processing by Aranea Agent
- Currently running task being processed by Aranea Agent
- Processed task finished.
- Processed task finished with warnings.
- Time stamp. The date/time the task has been initiated.
- Synchronization direction. The direction the task has to synchronize.
9
Figure 4 shows three types of tasks:
- The first line has as warnings or exceptions to be aware of.
- The second is the current running task being processed
- The last one is waiting task to be processed.
The task with the warnings status can show detailed information about a failed mapping by
Double Clicking or Right Mouse click the task (see Figure 5). The log info area shows an
overview of the processed synchronization showing start/end time, the number of contacts
processed (successful / skipped / failed) and a list of failed contacts.
The report data as shown is kept in memory which means that after a reboot of the server,
Figure 5: Task info window showing task report.

the report data is lost. By pressing the Save button, the report data can be exported to a
log file (see Figure 6).
10
Figure 6: Example log file of failed task.
1.3.4 How to change a configuration?
the menu, select Configurations and Edit....
Note: Stop the configuration first before editing.
11
2 ARANEA REQUIREMENTS & INSTALLATION
2.1 SYSTEM REQUIREMENTS
Since Aranea is an add-on tool for networks install Aranea on the same server as the
products involved. The system requirements for these servers are more than sufficiently for
Aranea.
Table 2: Where to install Aranea
Aranea Configuration Where must Aranea be installed?
BCT to Install Aranea on the PC where the Business ConneCT 4.x /

PhoneWare/OpenWorX or Management @Net is running.
MA4000.
CSV/ Active Directory to Install Aranea on the PC where the Business ConneCT 4.x
BCT. /Management @Net is running.
OpenWorX to PhoneWare.1 Install Aranea on the PC where OpenWorX is running.
CSV/ Active Directory to Install Aranea on the PC where OpenWorX is running.

OpenWorX1
CSV/ Active Directory to Install Aranea on the PC where PhoneWare has been
PhoneWare installed. Aranea accesses the Phonebook through SQL
queries. So jet type phone books are not supported.
More instances of Aranea cannot be installed on the same PC. However, simultaneous
synchronisation of multiple databases is possible (i.e. the BCT to MA4000 and PhoneWare).
Aranea supports an SQL type database:

- SQL 2000 SP4
- MSDE SP4
- SQL 2005 (Express)
- SQL 2008
1
Obsolete. OpenWorX is not supported for new installations anymore.
12
2.2 INSTALLATION OF ARANEA
The following procedure describes the installation and upgrades of Aranea.
2.2.1 Installing Aranea
Preconditions
Before you install Aranea, check that:

- An SQL type database service has been installed and is running.
- Depending on the desired configuration check one (or more) of the following:
- Business ConneCT: the Business ConneCT is up and running;
- PhoneWare: the Phonebook is present and the SQL Server for the Phonebook is up
and running;
- MyOffice@Net: the MyOffice@Net is up and running;
- Management@Net: the Management@Net server is up and running. Youll need to
know the IP-address of this server if Aranea is not installed on the
Management@Net server.
Actions
1. Log on to the server with user account with Administrator-rights (i.e. Administrator).
2. On the Start menu, point to Settings and then click Control Panel.
3. Double-click Add/Remove Programs.
4. Click Add New Programs.
5. Browse to the Aranea CD, open the folder Disk1 and double click setup.exe.
6. Follow the steps from the Installation Wizard for Aranea.
- After the Welcome screen, press Next.
- In the two following screens (Program Files Destination Folder and Data Files
Destination Folder), different destination folders can be selected for program files
and data files. Or keep the defaults and press Next.
- Select Yes or No on the question if there is a Management@Net Server installed and
press Next.
If there is a Management@Net server then status messages will be sent to the
Management Information Console (MIC).
- If Yes, enter the location of the Management@Net Server in the following screen and
press Next.
13
7. Depending on the installed product, one of the following Select Option screens
appears may appear:
Figure 7: Select the desired base configuration (a or b)
a. Select OpenWorX / PhoneWare if you want to synchronize between

OpenWorX and PhoneWare and/or
if you want to import customer data to OpenWorX or PhoneWare using
Active Directory or a CSV File.
b. Select MyOffice@Net / PhoneWare if you want to synchronize between

MyOffice@Net and PhoneWare and/or
if you want to import customer data to MyOffice@Net using Active
Directory or a CSV File.
14
Figure 8: Select the desired base configuration (a or c)
c. Select Business ConneCT / MA4000 / PhoneWare if you want to synchronize

between:
Business ConneCT and MA4000 or
Business ConneCT and PhoneWare or
Business ConneCT and MA4000 and PhoneWare and/or
if you want to import customer data to Business ConneCT or PhoneWare
using Active Directory or a CSV File.
Press Next.
15
8. Based on the selected base configuration the following data distribution configurations
are possible:
a. When OpenWorX / PhoneWare is selected the next screen contains the possible
data distribution configurations. It is possible to select more than one
configuration.
Figure 9: OpenWorX and PhoneWare possible configurations
For OpenWorX / PhoneWare there is a maximum of three possible configurations

simultaneously:
OpenWorX and PhoneWare Installation - Distribution between OpenWorX
and PhoneWare;
Active Directory or CSV File for PhoneWare Installation - Distribution from
Active Directory or external CSV source towards PhoneWare;
Active Directory or CSV File for OpenWorX Installation - Distribution from
Active Directory or external CSV source towards OpenWorX;

ANYMORE
16
b. When MyOffice@Net / PhoneWare is selected the next screen contains the
possible data distribution configurations. It is possible to select more than one
configuration.
Figure 10: MyOffce@Net and PhoneWare possible configurations
For MyOffice@Net / PhoneWare there is a maximum of two possible

configurations simultaneously:
MyOffice@Net and PhoneWare Installation - Distribution between
MyOffice@Net and PhoneWare;
Active Directory or CSV File for MyOffice@Net Installation - Distribution
from Active Directory or external CSV source towards MyOffice@Net;
17
c. When Business ConneCT / MA4000 / PhoneWare is selected the next screen
contains the possible data distribution configurations. It is possible to select more
than one configuration.
Figure 11: Business ConneCT / MA4000 / PhoneWare possible configurations
For Business ConneCT / MA4000 / PhoneWare there is a maximum of three

possible configurations simultaneously:
Business ConneCT and PhoneWare Installation - Distribution between
Business ConneCT and Phoneware;
Active Directory or CSV File for Business ConneCT Installation - Distribution
from Active Directory or external CSV source to Business ConneCT;
MA4000 and Business ConneCT Installation - Distribution between MA4000
and Business ConneCT.
Select the required components and press Next.
18
9. Depending on the selected configuration, you have to provide additional information
regarding the connection to data sources.
Figure 12: Provide Business ConneCT (United) data source properties.
a. For connection to Business ConneCT you have to provide:

BCT SQL server name: Provide the servername of the BCT server where
the database is installed on. This could be a separate SQL server. If needed
also have to provide the instance name on the SQL service. (see Figure 12)
By default this is (local).
SQL username: The SQL server login of a user that has access to read/write
the database.
By default this is sa.
SQL password: The password of this SQL User login.
19
Figure 13: Provide MA4000 data source properties.
b. For connection to MA4000 you have to provide:

MA4000 SQL server name: Provide the servername of the MA4000 server
where the database is installed on. This could be a separate SQL server. If
needed also have to provide the instance name on the SQL service. (see
Figure 21)
the database.
20
Figure 14: Provide OpenWorX data source properties.
c. For connection to OpenWorX you have to provide:
OpenWorX SQL server name: Provide the servername of the OpenWorX
server where the database is installed on. This could be a separate SQL
server. If needed also have to provide the instance name on the SQL service.
(see Figure 14)
the database.
21
Figure 15: Provide PhoneWare data source properties.
d. For connection to PhoneWare you have to provide:

PhoneWare SQL server name: Provide the servername of the PhoneWare
server where the database is installed on. This could be a separate SQL
server. If needed also have to provide the instance name on the SQL service.
(see Figure 15)
the database.
Database name: The name of the PhoneWare database.
By default this is bts_dir. (see Figure 16)
22
Figure 16: Provide PhoneWare database name.
10. Wait until all modules have been installed and press Finish.
11. A restart of the PC is requested to finish up the installation after reboot.
12. After restart of the PC, you MUST login using the same (administrator) account as
before the reboot. Wait until Aranea has finalised the installation.
WARNING: IF YOU INSTALL ARANEA ON A PC WHERE ANOTHER NEC-

PHILIPS APPLICATION IS RUNNING, THE INSTALLATION CAN
CAUSE THIS OTHER APPLICATION TO FAIL. THIS IS BECAUSE
ARANEA USES THE SAME USER (PBC-USERACCOUNT) TO
START PROCESSES ON THE SERVER; THE INSTALLATION
RENEWS THIS USERS PASSWORD. RUN THE SECURITY
CONFIGURATOR TO SOLVE THIS PROBLEM, SEE SECTION D.2
SECURITY CONFIGURATOR IN THIS BOOK FOR MORE
INFORMATION.
13. Now follow the correct configuration procedure in

chapter 3.2 Business ConneCT and MA4000 or
chapter 3.3 OpenWorX and or
23
chapter 3.4 CSV File as data source or
chapter 3.5 Active Directory as data source.
Note: The password of the PBC-UserAccount is reset after installation of Aranea. The PBC-
UserAccount is used for DCOM-settings on component to give the component
access/execution rights. This can be for example access rights to a file. To re-apply the
password, use the Security Configurator (see section D.2 Security Configurator) to
manually reset the password. Rebooting the system is advisable.
2.2.2 Upgrading Aranea

Upgrade from all versions is supported. After reinstallation, always perform a full upload to
all destinations. This is needed, because the used transfer database is changed. It also means
that the configuration data is lost.
The following procedure describes the upgrade instructions for upgrading an Aranea 1.4.x
to an Aranea 1.4.3 system.
Preconditions
- Stop currently running configurations of Aranea 1.4.x.

- Stop all other (foreground) applications.
- Backup custom-made mapping scripts (.vbs)
Actions
4. Click Add New Programs.
5. Browse to the Aranea CD, open the folder Disk1 and double click setup.exe.
6. The installation wizard guides you through the entire upgrade.
7. When the installation of the software starts, for all modules:
a. Answer Yes when asked to overwrite the existing Program Files;
b. Select Use the existing data-files.
8. All (installed) modules are now upgraded.
9. Reboot the PC when requested. After the reboot you MUST login using the same
(administrator) account as before the reboot.
10. Please note that rebooting can take a few minutes.
11. After installation, the security settings might be changed. Please refer to the warning in
step 12 of chapter 2.2.1.
24
Note: The password of the PBC-UserAccount is reset after installation of Aranea. The PBC-
UserAccount is used for DCOM-settings on component to give the component
password, use the Security Configurator (see section D.2 Security Configurator) to
manually reset the password. Rebooting the system is advisable
2.2.3 Uninstalling Aranea
This chapter describes the uninstall process of Aranea. It shows the steps to take and what
to expect. This strongly depends on the installed configurations. Note that the un-
installation does not require the installation Disk to be present. Further more you have to
be sure that the synced data sources are still present and accessible like a SQL connection
to SQL server via a LAN. This is needed so Aranea can remove the database adaptations
made during the installation process.
Preconditions
Before you uninstall Aranea, check that:
- Stop currently running configurations of Aranea.

- Stop all other (foreground) applications.
- Depending on the installed configurations, check the following:
- Business ConneCT: the BCT SQL service (United database) is up and running;
- MA4000: the MA4000 SQL service (MA4000 database) is up and running;
- PhoneWare: the SQL Server for the Phonebook is up and running;
- OpenWorX: the MA4000 SQL service (OpenWorX database) is present and up and
running;
- MyOffice@Net: the MyOffice@Net is up and running;
Actions
4. Select Aranea Install from the Currently installed programs.
5. Click button Change/Remove.
25
Figure 17: Uninstall Aranea.
6. The uninstaller guides you through the entire uninstallation.

7. When the uninstall of the software starts:
a. Provide data source properties for BCT and/or MA4000 and/or PhoneWare
and/or OpenWorX when requested. The default properties of the data sources
shown are taken from the configuration settings filled in during the installation or
with the use of the Aranea Configurator.
b. Answer Yes when asked to delete the existing Data Files;
Figure 18: Delete all contents of the Aranea DATA files directory.
8. Aranea is now uninstalling.
26
Figure 19: Uninstall Aranea has finished.
9. In rare situations you have to reboot the PC for Aranea to finish up the un-installation
process. After reboot, you MUST login again using the same (administrator) account
used as before the reboot.
10. Please note that rebooting can take a few minutes.
27
3 STANDARD ARANEA CONFIGURATIONS
The following sections contain procedures that describe the configuration of Aranea for
standard available contact-data synchronisation between NEC Philips products. Standard
configurations are:
- Business ConneCT (United) and Phoneware (bts_dir);
- Business ConneCT (United) and MA4000;
- OpenWorX and Phoneware .
- MyOffice@Net and Phoneware.
In addition to that Aranea can also connect to external sources to synchronise data from:
- Active Directory;
- CSV files.
All possible Aranea configurations are based on the same principle. The data from the
source database is mapped to the destination database using a mapping script. This script is
based on a scripting technology called Visual Basic Scripting (vbs) and maps user attributes
from Source DB to user attributes to Destination DB. (The scripts files are installed on the
system in the folder C:\NEC\Data Files\Aranea-module) Aranea sets up a
connection to the Source and Destination databases (on a scheduled base or real time) and
checks if there are any changes in the source database on user data and/or extension data. If
there are any changes these will be send to the destination database using the mapping
scripts.
To connect to a database (or data source) Aranea needs to be configured. The next
Table 3: Configuration items explained explains what items need to be configured so
that Aranea can connect to its respective data source. For example to connect to
the BCT database (United), the SQL server name (and eventual supplemented with
the instance name of the SQL service) is needed but also the Username and
Password must be provided.
Table 3: Configuration items explained
Data Source/ Configuration

Destination Item Explanation
Business Server The name of the SQL server where the database is
ConneCT located.
(United) Default setting: (Local)
User The SQL server login of a user that has access to
read/write the database.
Default setting: sa
28
Password The password of this User login.
PhoneWare Server The name of the SQL server where the database is
located.
Default setting: (Local)
Database The name of the PhoneWare database.
Default setting: bts_dir
User The SQL server login of a user that has access to
Default setting: sa
Password The password of this login.
Send updates to Enter Yes or No to configure if the updates need to

DSM be distributed to other Management@Net modules
(This is only using DSM/spider.
available as item Default setting: No
for Data
Destination)
OpenWorX Server The name of the SQL server where the database is
located.
Username The SQL server login of a user that has access to
Default setting: sa
MA4000 Server The name of the SQL server where the database is
located.
Username The SQL server login of a user that has access to
Default setting: sa
CSV File Column Delimiter The character in the input file that separates columns
Default setting: ,
File Name The name of the input file
Text Qualifier The character in the input file that indicates clear text
Default setting: (single quote)
29
Incremental Enter Yes to add the records to the destination
database, Enter No to indicate this is a new import.
Active Directory DomainName The domain name of the Active Directory.

Example: mydomain
User The domain username of a user that has read access
rights to the Active Directory tables.
Example: mydomain\domainuser
Password The password of this User.
LDAPFilter The default LDAP query can be extended with specific

filtering to include or exclude records from AD, see
Appendix C LDAP T.
LDAPBase The part of Active Directory that is used for the
input, for instance a specific Organisational Unit. This
must be done in LDAP notation see: Appendix C
LDAP T.
What data is synchronised?
Synchronization between the different data sources contains a set of data

fields which are in general supported by all configurations. The fields have
a descriptive name and the data will have their specific properties. This can
differ per configuration. For example: the size of the data field Z in data
source X has a maximum length of n while in data source Y it has a
maximum length of n-10. So when synchronizing data source X and Y, the
shortest data size will then be the maximum size for data field Z (= n-10).
This is something to be aware of especially where CSV file is part of the
configuration. The size of the data fields are not predefined so can easily
be oversized for the data source.
30
Table 4 shows a list of data fields supported by Aranea. Note that these
fields are not always available for every configuration. Per configuration this
is described in the upcoming chapters.
Table 4: Data fields supported by Aranea
General
Descriptions Description
1
PBX ID Unique identifier of PBX source db.
1
ContactID Unique identifier of the Contact
Operation1 Type of Operation needed fro processing.

1
Operation Time Timestamp of operation
Type1 Type of Contact (internal/External)
ContactID
Field where to store/search ContactID in the destination db.
FieldName1
User ID1 Unique identifier of User in the source db.
ExtensionID1 Unique identifier of Extension in the source db.

1
Foreign PBXID Unique identifier of PBX in the destination db.
1
Foreign UserID Unique identifier of User in the destination db.
Foreign ExtensionID1 Unique identifier of Extension in the destination db
The hierarchy data in the PhoneWare database is shared with

Costcenter TABS Call Reporting and is therefore mapped to the costcenter
field of the United database.
First name Firstname of the contact.
1
Last name Lastname of the contact.
Middle name The middle initial of the contact.
Fullname Fullname of the contact.
Initials The initials of the contact.

1
Extension Extension number of the contact.
1
Obligated fields. Depends on used configuration
31
General
BSPT BSPT of the extension
The United db does not contain a field that can be mapped to the
site name in the PhoneWare db. Since this is a mandatory field the
Extension Site default value Local is used. In multi-site environments the
mapping script must be changed to support synchronisation, use a
user defined field in United in that case.
Email Email address of the contact.
VIP The VIP status of the contact.
Title Title of suffix of the contact
Mobile Cell phone number of the contact.
Voicemail Voicemail access number of the contact.
Pager Pager number of the contact.
Modem Modem number of the contact.
Fax Fax number of the contact.
Company The company of the contact.
Division The division of the contact.
Department The department of the contact.
Alt. Extension Alternative extension number of the contact.
Same as for the extension number, the United db does not contain
Alt. Extension Site a field that can be mapped to the site name of the alternative
extension, the default value Local is used instead.
Building The room number of the contact.
Photo The path name of the contacts picture file on a web server.
NT Account The windows login name of the contact.
Licenceplate 1 The car registration number of the contacts car.
Licenceplate 2 The car registration number of the contacts 2nd car.
Job Title The job title of the contact.
User Defined 1 User defined field 1.
32
General
Home Address 1 Home address 1 of the contact
Home Address 2 Home address 2 of the contact
Home City Home city of the contact
Home State Home state of the contact
Home Zip Home zip code of the contact
Home Extension Home extension of the contact
Login Name Login name of the contact
Admin Rights Use of admin rights
Language Language of the contact
User ID code User ID code of the contact
Pincode Pincode of the contact (voicemail)
User Agent Is User Agent
Info Personal info of the contact
Office User rights Office user rights for this contact (only for new entries)
Password Password of the contact
SIP Uri SIP uri
LCS Presence State Presence state in LCS (optional)
LCS Presence Note Presence note in LCS (optional)
X400 X400 address notation of the contact
PBC User
All other user defined fields.
Defined 1 - 20
PBC Yes/No 1-20 All yes/no fields
33
3.1 BUSINESS CONNECT AND PHONEWARE
The synchronisation between the Business ConneCT and PhoneWare databases is

bidirectional. User and extension data is synced using script files called:
UNI2PWMapping.vbs and PW2UNIMapping.vbs. The script file can be found in the
C:\NEC\Data Files\Aranea-module folder. Aranea can create new users / update
users in both databases. This is also the case for extension data. Updates of extension data
are always synchronized. New extensions however can only be created for non-monitored
PBXs: a configured PBX in BCT / PhoneWare which is not monitored (synced) by its
application.
3.1.1 What data is synchronized?
Appendix A.1 Mappings Business ConneCT and PhoneWare shows a list data fields
supported by this configuration. It shows which fields are synchronized between BCT and
PhoneWare. The first column (General Descriptions) resembles the fields name in Table 4:
Data fields supported by Aranea (page 31).
3.1.2 Configuration procedure
This chapter describes the procedures to follow when configuring the synchronization
between Business ConneCT and PhoneWare.
Preconditions
Before you configure Aranea, check that you know the username and password of a user
account that has enough rights to start and run automatic tasks of Windows's Task
Scheduler. This is needed to be able to schedule a data synchronization task.
Further more you need know the username (SQL login) and password of the Business
ConneCT database (United) and Phoneware database. By default the same username is
used as provided during the installation.
And make sure the SQL server (or MSDE, SQL Express) is running in Mixed
Authentication Mode.
34
Actions
1. Start the Aranea Configurator.

2. From the List of configurations, select 'Business ConneCT and PhoneWare'.
Figure 20: List of installed Configurations.
3. From the menu, choose Configurations and Edit...
Figure 21: Configuration settings Business ConneCT/PhoneWare

35
4. Select the check box 'Enable Synchronization of section Business ConneCT to
PhoneWare' if you wish to synchronise from the Business ConneCT towards
PhoneWare and press 'Modify' of the same section. A 'Contact data configurator' box
opens.
5. Select the 'Contact Source' tab and enter the required configuration items (see Table
3: Configuration items explained page 28).
Figure 22: Configuration items screen

6. Press Test Contact Source to verify the provided settings.
Note: Pressing the Test-buttons of Contact Source and Sink is required otherwise the
configuration will not be marked validated. Only then the Schedule- and
Mapping-buttons are enabled!
7. Select the 'Contact Sink' -tab and enter the required configuration items. Press Test
Contact Sink to verify the provided settings.
8. In the bottom of the Configuration items screen the Transfer Script File can be
selected. Make sure you choose the UNI2PWMapping.vbs script located in
36
C:\NEC\Data Files\Aranea-Module and press OK to save the changes.
(NOTE: If Aranea is upgraded from a previous version, the script location might differ:
C:\Philips\Data Files\Aranea-Module)
9. Select the check box 'Enable Synchronization of section PhoneWare to Business
ConneCT if you wish to synchronise from the PhoneWare towards Business
ConneCT and press 'Modify' of the same section. You can use the same settings as
described in the previous steps, only the 'Contact Source' settings are now the
PhoneWare database, the 'Contact Sink' settings are now the Business ConneCT. The
Transfer Script File is now the PW2UNIMapping.vbs script.
10. Press Test Contact Source/ Test Contact Sink to verify the provided settings.
11. Configure the settings for the Synchronization Schedular:

a. Press the Schedule button. The Synchronization Scheduler window will be
shown.
Figure 23: Synchronization Scheduler screen
37
b. Select 'Real time' or 'Scheduled'.
If you choose 'Scheduled', configure the Schedule settings:
Occurs:
(1) Once; specify a date
(2) Daily
(3) Weekly; specify a day.
Dial frequency:
(1) Start at: specify the start time.
(2) During; specify the duration of the synchronization task. (only available
for Occurs: Daily and Weekly)
(3) Every; specify the interval for starting the task within the duration time.
(only available for Occurs: Daily and Weekly)
Account:
Fill in the user account and password that has enough rights to run the task in
the Windows Scheduled Taks. This could be the user account you are
currently logged in now.
12. Press Mapping to configure the mapping between the PBXs defined in both data
sources. Aranea needs to know which PBXs belong together.
Figure 24: PBX Mapping screen BCT-PhoneWare
38
13. Select the PBX mapping from the Mapping table and in Jointed PBX name you can
select the corresponding PBX name from the PhoneWare data source.
14. Press OK and Close the Configuration settings window.
15. For further actions, see chapter 3.6 Finishing up the configuration.
3.2 BUSINESS CONNECT AND MA4000
The synchronisation between the Business ConneCT and MA4000 databases is

bidirectional. User and extension data is synced using script files called:
UNI2MA4000Mapping.vbs and MA40002UNIMapping.vbs. The script file can be found in
the C:\NEC\Data Files\Aranea-module folder. Aranea can create new users / update
users in both databases. This is also the case for extension data. Updates of extension data
are always synchronized. New extensions however can only be created for non-monitored
PBXs: a configured PBX in BCT / PhoneWare which is not monitored (synced) by its
application. Towards MA4000, Aranea cannot crfeate new extensions.
Appendix A.2 Mappings Business ConneCT and MA4000 shows a list data fields supported
by this configuration. It shows which fields are synchronized between BCT and MA4000.
The first column (General Descriptions) resembles the fields name in Table 4: Data fields
supported by Aranea (page 31).
between Business ConneCT and MA4000.
Preconditions
ConneCT database (United) and MA4000 database. By default the same username is used
as provided during the installation.
39
Actions

2. From the List of configurations, select 'MA4000 and Business ConneCT'.

40
Figure 26: Configuration settings Business ConneCT/MA4000
4. Select the check box 'Enable Synchronization of section MA4000 to Business

ConneCT' if you wish to synchronise from the MA4000 towards Business ConneCT
and press 'Modify' of the same section. A 'Contact data configurator' box opens.
41
Figure 27: Configuration items screen for MA4000 contactsource

selected. Make sure you choose the UNI2MA4000Mapping.vbs script located in
9. Select the check box 'Enable Synchronization of section Business ConneCT to
42
MA4000 if you wish to synchronise from the Business ConneCT towards MA4000 and
press 'Modify' of the same section. You can use the same settings as described in the
previous steps, only the 'Contact Source' settings are now the MA4000 database, the
'Contact Sink' settings are now the Business ConneCT. The Transfer Script File is now
the MA40002UNIMapping.vbs script.
11. Configure the settings for the Synchronization Scheduler:

shown.

43
Occurs:
(2) Daily
Dial frequency:
Account:
Figure 29: PBX Mapping screen BCT-MA4000
44
select the corresponding PBX name from the Business ConneCT data source.
3.3 OPENWORX AND PHONEW ARE

ANYMORE
The synchronisation between OpenWorX and PhoneWare databases is bidirectional. User

and extension data is synced using script files called: OWX2PWMapping.vbs and
PW2OWXMapping.vbs. The script file can be found in the C:\NEC\Data Files\Aranea-
module folder. Aranea can create new users / update users in both databases. This is also
the case for extension data. Updates of extension data are always synchronized. New
extensions however can only be created for non-monitored PBXs: a configured PBX in
OpenWorX / PhoneWare which is not monitored (synced) by its application.
Appendix A.9 Mappings OpenWorX and PhoneWare shows a list data fields supported by
this configuration. It shows which fields are synchronized between OpenWorX and
PhoneWare. The first column (General Descriptions) resembles the fields name in Table 4:
Data fields supported by Aranea (page 31).
between OpenWorX and PhoneWare.
Preconditions
Further more you need know the username (SQL login) and password of the OpenWorX
database and Phoneware database. By default the same username is used as provided during
the installation. And make sure the SQL server (or MSDE, SQL Express) is running in
Mixed Authentication Mode.
Actions
45
2. From the List of configurations, select OpenWorX and PhoneWare'.
46
Figure 31: Configuration settings OpenWorX/PhoneWare
4. Select the check box 'Enable Synchronization of section OpenWorX to PhoneWare' if

you wish to synchronise from the OpenWorX towards PhoneWare and press
'Modify' of the same section. A 'Contact data configurator' box opens.
47
Figure 32: Configuration items screen

selected. Make sure you choose the OWX2PWMapping.vbs script located in
48
9. Select the check box 'Enable Synchronization of section PhoneWare to OpenWorX if
you wish to synchronise from the PhoneWare towards OpenWorX and press
'Modify' of the same section. You can use the same settings as described in the
previous steps, only the 'Contact Source' settings are now the PhoneWare database,
the 'Contact Sink' settings are now the OpenWorX. The Transfer Script File is now
the PW2OWXMapping.vbs script.
11. Configure the settings for the Synchronization Schedular:

shown.
49
Occurs:
(2) Daily
Dial frequency:
Account:
select the corresponding PBX name from the PhoneWare data source.
3.4 CSV FILE AS DATA SOURCE
The CSV File Contact Source is used for customers that are using an External Directory
(database) for which we have no direct Contact Source Component (no Lotus Notes or
Active Directory) is available. The CSV File Contact Source is based on importing contact
data from a file into the Business ConneCT, PhoneWare or openWorX data source. This
means that such a file must be created and should reflect the contents (initially) and changes
of the customer's database. This could be a scheduled procedure (task or script) that
regularly exports data from customer's database into such a file.
The contents of such a file must meet specific requirements. This information is given in this
section.
An example of the contents of the file:
Operation, ContactID, Extension, Mobile, LastName, FirstName, Email

-,0007,1000,0612345678,Bond,James,james.bond@mi6.com
+,0008,1001,0687654321,Tanasescu,Adela,tanasescu@mi6.com
50
The requirements are:
- It is a comma-separate (CSV) file. Note that the delimiter (comma) can be

specified. (See Table 3: Configuration items explained page 28 ).
- The first line contains the column headers, where:
- Operation is the action to be taken:
- +: add or update this contact
- -: delete this contact.
- ContactID is a unique ID for every contact.
This means that whatever is done for this contact, you must always use the
same ContactID. This identifier is used for looking up the contact in the
target database. If not found, the contact will be added (operation=+) or
deleted (operation = -). If two lines contain the same ContactID, they refer to
the same contact.
- Extension and LastName refer to fields to be added, modified or deleted.
These fields are obligated.
- Mobile, FirstName, and Email refer to the fields to be added, modified or
deleted. These are additional fields and are not obligated.
- All lines after the header line will contain the actual data to be added, modified
or deleted. Fields may be left empty (by given a comma), but the corresponding
field in the target database will be cleared.
- The fields Operation, ContactID, Extension and LastName are obligatory. The
other fields are optional and custom extendable.
- The header may vary in number of columns but must at least contain the
obligatory fields. And the data lines must have the same number of columns as
defined in the header.
NOTE that the ContactID only is used for Internal Contacts. For External Contacts a id is
created based on name/extension. This might result in duplicated entries on name change.
This can be resolved by adding a - operation in the CSV file that first removes the old entry
(with the old data). The + operation will add a new entry with the new parameters.
The synchronisation between a CSV File and the supported data source is one direction
only. Table 1: Possible configurations in Aranea 1.4.3 (page 5) shows a list of supported
configurations:
- CSV File to Business ConneCT
- CSV File to PhoneWare
- CSV File to OpenWorX
Appendices A.3 Mappings CSV File and Business ConneCT, A.4 Mappings CSV File and
51
PhoneWare, and A.5 Mappings CSV File and OpenWorX shows a list data fields supported
by this configuration. It shows which fields are synchronized from CSV towards BCT,
PhoneWare and OpenWorX. The first column (General Descriptions) resembles the fields
name in Table 4: Data fields supported by Aranea (page 31).
between CSV File and one of the data sources Business ConneCT, PhoneWare and
OpenWorX. When there is a specific difference with one of the data sources this will be
mentioned in the text.
Preconditions
ConneCT database (United), PhoneWare or OpenWorX database. By default the same
username is used as provided during the installation.
Actions

2. From the List of configurations, select 'File and Business ConneCT (or File and
PhoneWare, or File and OpenWorX).
52
Figure 35: Configuration settings File/Business ConneCT
4. Press Modify of section File to Business ConneCT' .A 'Contact data configurator'

box opens.
3: Configuration items explained - page 28).
53
Figure 36: Configuration items screen for File contactsource

configuration will not be marked validated. Only then the Schedule-button will be
enabled!
selected. Make sure you choose the correct mapping script file. Depending on the
selected configuration the next script files are selected:
a. Business ConneCT: CSV2UNIMapping.vbs
b. PhoneWare: CSV2PWMapping.vbs
54
c. OpenWorX: CSV2OWXMapping.vbs
By default the script files are located in C:\NEC\Data Files\Aranea-
Module and press OK to save the changes.
(NOTE: If Aranea is upgraded from a previous version, the script location might
differ: C:\Philips\Data Files\Aranea-Module)

shown.
b. By default you can only schedule the synchronization task. Configure the Schedule
settings:
Occurs:
(2) Daily
55
Dial frequency:
Account:
10. Press OK and Close the configurator.
3.5 ACTIVE DIRECTORY AS DATA SOURCE
The Active Directory Contact Source is based on importing contact data from an Active
Directory environment into the Business ConneCT, PhoneWare or openWorX data source.
It connects to a configured domain controller and queries for user accounts using the LDAP
query mechanism. The configuration can be customized by applying a specific LDAP query
to filter out the undesired user accounts like for example Administrator or Guest.
The synchronisation between Active Directory and the supported data source is one
direction only. Table 1: Possible configurations in Aranea 1.4.3 (page 5) shows a list of
supported configurations:
- Active Directory to Business ConneCT
- Active Directory to PhoneWare
- Active Directory to OpenWorX
Appendices A.3 Mappings CSV File and Business ConneCT, A.4 Mappings CSV File and
PhoneWare, and A.5 Mappings CSV File and OpenWorX shows a list data fields supported
by this configuration. It shows which fields are synchronized from CSV towards BCT,
PhoneWare and OpenWorX. The first column (General Descriptions) resembles the fields
name in Table 4: Data fields supported by Aranea (page 31).
between Active Directory and one of the data sources Business ConneCT, PhoneWare and
OpenWorX. When there is a specific difference with one of the data sources this will be
56
mentioned in the text.
Preconditions
ConneCT database (United), PhoneWare or OpenWorX database. By default the same
username is used as provided during the installation. Make sure you have an AD account
name and password with rights to read the AD content from the domain controller. And
make sure the SQL server (or MSDE, SQL Express) is running in Mixed Authentication
Mode.
Actions

2. From the List of configurations, select 'Active Directory and Business ConneCT' (or
Active Directory and PhoneWare, or Active Directory and OpenWorX).

57
Figure 39: Configuration settings Active Directory/Business ConneCT
4. Press Modify of section Active Directiry to Business ConneCT' .A 'Contact data

configurator' box opens.
3: Configuration items explained - page 28).
58
Figure 40: Configuration items screen for Active Directory contactsource

configuration will not be marked validated. Only then the Schedule-button will be
enabled!
59
selected. Make sure you choose the correct mapping script file. Depending on the
selected configuration the next script files are selected:
a. Business ConneCT: ADSI2UNIMapping.vbs
b. PhoneWare: ADSI2PWMapping.vbs
c. OpenWorX: ADSI2OWXMapping.vbs
By default the script files are located in C:\NEC\Data Files\Aranea-Module and

press OK to save the changes.

shown.
b. By default you can only schedule the synchronization task. Configure the Schedule
settings:
60
Occurs:
(2) Daily
Dial frequency:
Account:
10. Press OK and Close the configurator.
3.6 FINISHING UP THE CONFIGURATION
When finished configuring, the list of configuration are showing that the synchronization
process is ready activate. This is shown by the status icon in front of the configuration.
There are three types to status:
1. Not validated:
The configuration is not validated. The configuration settings are not filled in or not
validated by the Aranea Configurator with the data sources. The text behind the
configuration name can give some explanation what is not validated:
a. Configuration settings not validated;
b. No PBX mapping configured; There are no
c. No schedule configured;
2. Stopped / Ready to be started:
The configuration is validated and ready to be started.
3. Operational:
The configuration is operational. The text behind the configuration name displays the
type of synchronization:
a. Real time;
b. Scheduled task;
Figure 42 gives an example of two configurations and their status.
61
Figure 42: Not Ready status of the configurations.
Both configurations are not validated. Configuration MA4000 and business ConneCT has
already been validated on the data source settings but has no Synchronization Schedule set.
After setting the Synchronization Schedule and when needed the PBX Mapping, the status
of the configuration MA4000 and business ConneCT has changed to Stopped / Ready to
be started. (see Figure 43)
Figure 43: Ready status of the configurations.
62
Appendix A. Synchronized Data fields
This appendix gives an overview of the data fields which are mapped for
the different configuration. It lists the fields as named in Table 4: Data fields
supported by Aranea (page 5) and the mapping between the data sources.
The Mapped To shows if the data is mapped one- or bi-directional.
A.1. Mappings Business ConneCT and PhoneWare
The following table shows the list of field supported by Aranea which are
included in the synchronization of Business ConneCT and PhoneWare. The
mapping is based on the default mapping scripts PW2UNIMapping.vbsand
UNI2PWMapping.vbs. If desired the script can be customized to own need.
PhoneWare "Mapped to" Business ConneCT

Mapping script used:
PW2UNIMapping.vbs
()
General Available Data UNI2PWMapping.vbs Available Data
Descriptions Fields (size) () Fields (size)
ContactID1 ContactID ContactID
1
Operation Operation Operation
Operation
OperationTime
Time1

default value:
"I" = Internal Extension
"E" = External Extension
Distinction is made
based on the
Type1 Type Type
value of field
'_site_group_code '.
By default:
If <_site_group_code> =
"999" then
Type = "E".
ContactID
ContactIDFieldName
FieldName
1
Obligated field
63
PW2UNIMapping.vbs
()
Foreign PBXID1 _site_group_code PW_site_group
Foreign
_owxempid emp_uniqueID
UserID1
Foreign
_owxextid ext_uniqueID
ExtensionID1

PBX ID1 _site_group_code (Using PBX Mapping pbxID
table)
Extension ID1 _entry_number pbc_ext_id
Costcenter _hier1_name (36) Costcenter (50)

1
User ID _entry_number PW_entry_nr

if Type="E" and
First name _forename (15) lastName has format firstName (30)
"<lastName>,
<firstName>":
_forename is extracted
from the lastName

if Type="E" and
Last name1 _surname (40) lastName has format lastName (30)
"<lastName>,
<firstName>":
_surname is extracted
from the lastName
middleName (30)
Middle name _user19 (30)
prefix (30)
1
Obligated field
64
PW2UNIMapping.vbs
()

merged value:
Fullname fullName = "<_surname>, fullName (60)
<_forename>
<_user19>."
Extension1 _extn_num (20) extension (16)
BSPT PBC_BSPT (40)

Extension Site _extn_site (8)
default value: "Local"

_email_address
Email email (50)
(50) if Type="E":
_email_address =
<userDefined1>
VIP _user11 (30) vip
Title _title (4) title (30)
_mobile_number
Mobile mobilePhone (25)
(20)
Voicemail _voice_mail (20) voiceMail (25)
_pager_number
Pager Pager (25)
(20)
Modem modem (25)

Fax _fax_number (20) fax (25)
if Type="E":
_fax_number =
<userDefined2>
Company _location (30) company (30)
Division _user05 (30) division (30)
Department _user01 (30) departmen (30)
65
PW2UNIMapping.vbs
()
_alt_extn_num
Alt. Extension alternateNumber (25)
(20)

default value:
Alt. Extension
_alt_extn_site (8) If <_alt_extn_num> is
Site
NOT empty then
_alt_extn_site = "Local"
Building _user13 (30) building (30)
Photo _user17 (30) Photo (255)
NT Account _user08 (30) PBC_NTLogin (140)

PBC_LicencePlate1
Licenceplate 1 _user09 (30)
(40)
PBC_LicencePlate2
(40)
Job Title _user06 (30) PBC_Jobtitle (40)
1
Initials _initials (5) n.m.

Only if Type="E":
User Defined 12 userDefined1 (50)
userDefined1 =
<_email_address>

Only if Type="E":
userDefined2 =
<_fax_number>

Only if Type="E":
userDefined3 =
<_user03>

Only if Type="E":
userDefined4 =
<_user04>
1
N.m. = Not Mapped
2
External contacts only
66
PW2UNIMapping.vbs
()
Home Address
homeAddress1 (60)
1
Home Address
homeAddress2 (60)
2
Home City homeCity (30)
Home State homeState (30)
Home Zip homeZip (10)

Home
homePhone (25)
Extension
Login Name PBC_LoginName (80)
PBC_AdminRights
Admin Rights
(40)
Language PBC_Language (40)
PBC_usr_Identification
User ID code
(20)
PBC_usr_PinCode
Pincode
(20)
PBC_usr_UserAgent
User Agent
(400)
PBC_PersonalInfo
Info
(400)
Can be one or more
(addition sum) of the
values:
"1" = OfficeUser
"2" = Agent
"4" = Operator
Office User "8" = Administrator
OfficeUser
rights "16" = MyOffice user
"32" = Management user
"64" = Voicemail user
"128" = Phone Based
Agent
"256" = No right to see
other permissions
67
PW2UNIMapping.vbs
()
Password PBC_Password (40)
SIP Uri SipUri (500)

LCS Presence
LcsPresenceState
State
LCS Presence LcsPresenceNote
Note (500)
X400 X400 (255)

PBC User
_user01 (30) pbc_empuser1 (50)
Defined 1
PBC User
Defined 2

PBC User
Defined 3 if Type="E":
_user03 =
<userDefined3>

PBC User
Defined 4 if Type="E":
_user04 =
<userDefined4>
PBC User
Defined 5
PBC User
Defined 6
PBC User
Defined 7
PBC User
Defined 8
PBC User
Defined 9
PBC User
Defined 10
68
PW2UNIMapping.vbs
()
PBC User
Defined 11
PBC User
Defined 12
PBC User
Defined 13
PBC User
Defined 14
PBC User
Defined 15
PBC User
Defined 16
PBC User
Defined 17
PBC User
Defined 18
PBC User
Defined 19
PBC User
Defined 20
PBC Yes/No 1 _yesno01 pbc_empyesno1
69
PW2UNIMapping.vbs
()
70
A.2. Mappings Business ConneCT and MA4000
included in the synchronization of Business ConneCT and MA4000. The
mapping is based on the default mapping scripts
MA40002UNIMapping.vbsand UNI2MA4000Mapping.vbs. If desired the script
can be customized to own need.
MA4000 "Mapped to" Business ConneCT

MA40002UNIMapping.vbs
()
General Available Data UNI2MA4000Mapping.vbs Available Data
Operation1 Operation Operation

Operation
OperationTime
Time
Type1 Type Type

ContactID
ContactIDFieldName
FieldName
Foreign
PW_site_group
PBXID
Foreign
ExtrnEmployeeUniqueID emp_uniqueID
UserID1
Foreign
ExtrnExtensionUniqueID ext_uniqueID
ExtensionID1

PBX ID1 PbxID (Using PBX Mapping pbxID
table)
Extension ID1 ExtensionID pbc_ext_id
Costcenter Costcenter (50)
pbc_usr_id
User ID1 UserID
PW_entry_nr
1
Obligated field
71
()
First name FirstName (50) firstName (30)
Last name1 LastName (50) lastName (30)
Middle name MiddleInit (1) middleName (30)

merged value:
fullName =
Fullname fullName (60)
"<LastName>,
<FirstName>
<MiddleInit>."

Extracted from the
Number field:
"xxxx-yy" => extension
Extension1 Number = xxxx extension (16)

merged value:
Number = "<extension>-
<PBC_BSPT>"

Extracted from the
BSPT Number field: PBC_BSPT (40)
"xxxx-yy" =>
PBC_BSPT = yy
Extension Site
Email Email (255) email (50)
VIP vip
Title title (30)
Voicemail voiceMail (25)
Pager Pager (25)
1
Obligated field
72
()
Modem modem (25)
Fax fax (25)

Extracted from the
OrganisationLevel field:
/C/D/P/ => company = C
Company company (30)
merged value:
Organisationlevel =
"/<company>/<division>
/<department>/"

Extracted from the
/C/D/P/ => division = D
Division Organisationlevel division (30)
(450) merged value:
Organisationlevel =
/<department>/"

Extracted from the
/C/D/P/ => department =
P
Department departmen (30)

merged value:
Organisationlevel =
/<department>/"
Alt. Extension
Site
Building building (30)
Photo Photo (255)
NT Account PBC_NTLogin (140)
73
()
PBC_LicencePlate1
Licenceplate 1
(40)
PBC_LicencePlate2
Licenceplate 2
(40)
Job Title PBC_Jobtitle (40)
Initials
User Defined
userDefined1 (50)
11
User Defined
userDefined2 (50)
21
User Defined
userDefined3 (50)
31
User Defined
userDefined4 (50)
41
Home
homeAddress1 (60)
Address 1
Home
homeAddress2 (60)
Address 2

Home
homePhone (25)
Extension
Login Name PBC_LoginName (80)
PBC_AdminRights
Admin Rights
(40)
PBC_usr_Identificatio
User ID code
n (20)
1
74
()
PBC_usr_PinCode
Pincode
(20)
PBC_usr_UserAgent
User Agent
(400)
PBC_PersonalInfo
Info
(400)
Can be one or more
values:
"1" = OfficeUser
"2" = Agent
"4" = Operator
"8" = Administrator
Office User
"16" = MyOffice user OfficeUser
rights
"32" = Management
user
"128" = Phone Based
Agent
other permissions

LCS Presence
LcsPresenceState
State
Note (500)
X400 X400 (255)
PBC User
pbc_empuser1 (50)
Defined 1
PBC User
pbc_empuser2 (50)
Defined 2
PBC User
pbc_empuser3 (50)
Defined 3
PBC User
pbc_empuser4 (50)
Defined 4
75
()
PBC User
LoginName (255) pbc_empuser5 (50)
Defined 5
PBC User
DisplayName (20) pbc_empuser6 (50)
Defined 6
PBC User
pbc_empuser7 (50)
Defined 7
PBC User
pbc_empuser8 (50)
Defined 8
PBC User
pbc_empuser9 (50)
Defined 9
PBC User
pbc_empuser10 (50)
Defined 10
PBC User
pbc_empuser11 (50)
Defined 11
PBC User
pbc_empuser12 (50)
Defined 12
PBC User
pbc_empuser13 (50)
Defined 13
PBC User
pbc_empuser14 (50)
Defined 14
PBC User
pbc_empuser15 (50)
Defined 15
PBC User
pbc_empuser16 (50)
Defined 16
PBC User
pbc_empuser17 (50)
Defined 17
PBC User
pbc_empuser18 (50)
Defined 18
PBC User
pbc_empuser19 (50)
Defined 19
PBC User
pbc_empuser20 (50)
Defined 20
PBC Yes/No 1 pbc_empyesno1
76
()

PBC Yes/No
pbc_empyesno10
10
PBC Yes/No
pbc_empyesno11
11
PBC Yes/No
pbc_empyesno12
12
PBC Yes/No
pbc_empyesno13
13
PBC Yes/No
pbc_empyesno14
14
PBC Yes/No
pbc_empyesno15
15
PBC Yes/No
pbc_empyesno16
16
PBC Yes/No
pbc_empyesno17
17
PBC Yes/No
pbc_empyesno18
18
PBC Yes/No
pbc_empyesno19
19
PBC Yes/No
pbc_empyesno20
20
77
A.3. Mappings CSV File and Business ConneCT
included in the synchronization of CSV File towards Business ConneCT.
The mapping is based on the default mapping script CSV2UNIMapping.vbs.
If desired the script can be customized to own need.
CSV "Mapped to" Business ConneCT

General Available Data CSV2UNIMapping.vbs Available Data
Descriptions Fields () Fields (size)
Operation Time

default value:
Distinction is made based
on the
Type1 Type
length of 'Extension'
fieldvalue.
By default:
If length of extension > 6
then
Type = "E".

ContactID
default value ContactIDFieldName
FieldName
"pbc_empuser20" 2
Foreign PBXID PW_site_group
Foreign UserID PW_entry_nr

Foreign
ext_uniqueID
ExtensionID
PBX ID1 PbxID pbxID
1
Obligated field
2
Can be modified by editing the mapping script
78
Extension ID pbc_ext_id
User ID emp_uniqueID
First name FirstName firstName (30)

1
Last name LastName lastName (30)
Middle name prefix middleName (30)

merged value:
fullName = "<LastName>,
<FirstName> <prefix>." 2
Extension1 Extension extension (16)
BSPT PBC_BSPT (40)
Extension Site
Email email email (50)

VIP vip
default value: "0" 2

Title title (30)
default value: " " 2
Mobile Mobile mobilePhone (25)


Pager Pager (25)

Modem modem (25)

Fax fax (25)

Company company (30)
1
Obligated field
2
79

Division division (30)

Department departmen (30)
alternateNumber
Alt. Extension
default value: " " 1 (25)
Alt. Extension
Site


Photo Photo (255)
NT Account AccountName PBC_NTLogin (140)
PBC_LicencePlate1
Licenceplate 1
PBC_LicencePlate2
Licenceplate 2

Job Title PBC_Jobtitle (40)
Initials
User Defined 1 2 userDefined1 (50)

2

Home Address 1 homeAddress1 (60)



1
2
80


Home Extension homePhone (25)
PBC_LoginName
Login Name
(80)
PBC_AdminRights
Admin Rights
(40)
PBC_usr_Identificati
User ID code
on (20)
PBC_usr_PinCode
Pincode
(20)
PBC_usr_UserAgent
User Agent
(400)
PBC_PersonalInfo
Info
(400)

Can be one or more
(addition sum) of the values:
"1" = OfficeUser
"2" = Agent
"4" = Operator
Office User
"8" = Administrator OfficeUser
rights
"16" = MyOffice user
"32" = Management user
"128" = Phone Based Agent
"256" = No right to see other
permissions

LCS Presence
LcsPresenceState
State
Note (500)
1
81
X400 X400 (255)
PBC User
pbc_empuser1 (50)
Defined 1
PBC User
pbc_empuser2 (50)
Defined 2
PBC User
pbc_empuser3 (50)
Defined 3
PBC User
pbc_empuser4 (50)
Defined 4
PBC User
pbc_empuser5 (50)
Defined 5
PBC User
pbc_empuser6 (50)
Defined 6
PBC User
pbc_empuser7 (50)
Defined 7
PBC User
pbc_empuser8 (50)
Defined 8
PBC User
pbc_empuser9 (50)
Defined 9
PBC User
pbc_empuser10 (50)
Defined 10
PBC User
pbc_empuser11 (50)
Defined 11
PBC User
pbc_empuser12 (50)
Defined 12
PBC User
pbc_empuser13 (50)
Defined 13
PBC User
pbc_empuser14 (50)
Defined 14
PBC User
pbc_empuser15 (50)
Defined 15
PBC User
pbc_empuser16 (50)
Defined 16
PBC User
pbc_empuser17 (50)
Defined 17
82
PBC User
pbc_empuser18 (50)
Defined 18
PBC User
pbc_empuser19 (50)
Defined 19
PBC User
pbc_empuser20 (50)
Defined 20
83
84
A.4. Mappings CSV File and PhoneWare
included in the synchronization of CSV File towards PhoneWare. The
mapping is based on the default mapping script CSV2PWMapping.vbs. If
desired the script can be customized to own need.
CSV "Mapped to" PhoneWare

General Available Data CSV2PWMapping.vbs Available Data Fields
Descriptions Fields () (size)
Operation Time OperationTime

default value:
Distinction is made
based on the
Type1 Type
fieldvalue.
By default:
If length of Extension > 6
then
Type = "E".
ContactID
FieldName
Foreign PBXID _site_group_code
Foreign UserID _owxempid

Foreign
_owxextid
ExtensionID

1 If Type = "E" then
PBX ID PbxID _site_group_code
<_site_group_code > =
"999"
1
Obligated field
85
Extension ID _entry_number
Costcenter _hier1_name (36)
User ID _entry_number

merged value:
First name FirstName fullName = _forename (15)
"<LastName>,
<FirstName> <prefix>." 1
Last name2 LastName _surname (40)
Middle name prefix _user19 (30)
Fullname
Extension2 Extension _extn_num (20)
BSPT
Email email _email_address (50)

VIP _user11 (30)
Title _title (4)
Mobile Mobile _mobile_number (20)
Voicemail _voice_mail (20)
Pager _pager_number (20)
Modem
Fax _fax_number (20)
1
2
Obligated field
86
Company _location (30)
Division _user05 (30)
Department _user01 (30)
Alt. Extension _alt_extn_num (20)
Alt. Extension
_alt_extn_site (8)
Site
Building _user13 (30)
Photo _user17 (30)

1
NT Account AccountName n.m. _user08 (30)
Job Title _user06 (30)
Initials _initials (5)
User Defined 1 2
User Defined 2 2
User Defined 3 2
User Defined 4 2
Home Address 1
Home Address 2
Home City
Home State
1
N.m. = Not Mapped
2
87
Home Zip
Home Extension
Login Name
Admin Rights
Language
User ID code
Pincode
User Agent
Info
Office User
rights
Password
SIP Uri
LCS Presence
State
LCS Presence
Note
X400
PBC User
_user01 (30)
Defined 1
PBC User
_user02 (30)
Defined 2
PBC User
_user03 (30)
Defined 3
PBC User
_user04 (30)
Defined 4
PBC User
_user05 (30)
Defined 5
88
PBC User
_user06 (30)
Defined 6
PBC User
_user07 (30)
Defined 7
PBC User
_user08 (30)
Defined 8
PBC User
_user09 (30)
Defined 9
PBC User
_user10 (30)
Defined 10
PBC User
_user11 (30)
Defined 11
PBC User
_user12 (30)
Defined 12
PBC User
_user13 (30)
Defined 13
PBC User
_user14 (30)
Defined 14
PBC User
_user15 (30)
Defined 15
PBC User
_user16 (30)
Defined 16
PBC User
_user17 (30)
Defined 17
PBC User
_user18 (30)
Defined 18
PBC User
_user19 (30)
Defined 19
PBC User
_user20 (30)
Defined 20
PBC Yes/No 1 _yesno01
89







90
A.5. Mappings CSV File and OpenWorX
included in the synchronization of CSV File towards OpenWorX. The
mapping is based on the default mapping script CSV2OWXMapping.vbs. If
CSV "Mapped to" OpenWorX

General Available CSV2OWXMapping.vbs Available Data
Descriptions Data Fields () Fields (size)

default value:
Distinction is made based on
Type1 the Type
fieldvalue.
By default:
If length of Extension > 6 then
Type = "E".
ContactID
FieldName
Foreign UserID emp_uniqueID
Foreign
ext_uniqueID
ExtensionID
PBX ID1 pbxID pbxid
1
Obligated field
91
Costcenter costcenter (5)
User ID PW_entry_nr
First name firstName firstName (30)
Last name1 fastName lastName (30)
prefix (30)
Middle name prefix
middleName (30)

merged value:
Fullname fullName = "<sn>, fullName (60)
<givenName>
<MiddleName>." 2
Extension1 extension extension (16)
BSPT
Extension Site
Email email email (50)
VIP vip

Title title (30)
Mobile Mobile mobilePhone (25)
Voicemail voicemail (25)

Pager pager (25)
Modem modem (25)

Fax fax (25)
1
Obligated field
2
92

Company If <company> is empty then company (30)
company = "NEC Philips" 1
Division division (30)

If <department> is empty
Department department (30)
then
department = "NEC Philips" 1
Alt. Extension
Site

Photo
NT Account AccountName n.m.2
Licenceplate 1
Licenceplate 2
Job Title
Initials
User Defined 13
User Defined 23
User Defined 33
User Defined 43
Home Address
1
1
2
N.m. = Not Mapped
3
93
Home Address
2
Home City
Home State
Home Zip
Home
homePhone (25)
Extension
Login Name
Admin Rights
Language
User ID code
Pincode
User Agent
Info
Office User
rights
Password
SIP Uri
LCS Presence
State
LCS Presence
Note
X400
PBC User
pbc_empuser1 (50)
Defined 1
PBC User
pbc_empuser2 (50)
Defined 2
94
PBC User
pbc_empuser3 (50)
Defined 3
PBC User
pbc_empuser4 (50)
Defined 4
PBC User
pbc_empuser5 (50)
Defined 5
PBC User
pbc_empuser6 (50)
Defined 6
PBC User
pbc_empuser7 (50)
Defined 7
PBC User
pbc_empuser8 (50)
Defined 8
PBC User
pbc_empuser9 (50)
Defined 9
PBC User
pbc_empuser10 (50)
Defined 10
PBC User
pbc_empuser11 (50)
Defined 11
PBC User
pbc_empuser12 (50)
Defined 12
PBC User
pbc_empuser13 (50)
Defined 13
PBC User
pbc_empuser14 (50)
Defined 14
PBC User
pbc_empuser15 (50)
Defined 15
PBC User
pbc_empuser16 (50)
Defined 16
PBC User
pbc_empuser17 (50)
Defined 17
PBC User
pbc_empuser18 (50)
Defined 18
PBC User
pbc_empuser19 (50)
Defined 19
PBC User
pbc_empuser20 (50)
Defined 20
95







96
A.6. Mappings Active Directory and Business ConneCT
included in the synchronization of Active Directory towards Business
ConneCT. The mapping is based on the default mapping script
ADSI2UNIMapping.vbs. If desired the script can be customized to own
need.
"Mapped to"
Active Directory Business ConneCT
General Available Data ADSI2UNIMapping.vbs Available Data
1
Operation Time

default value:
Distinction is made
based on the
length of
Type1 Type
'telephoneNumber'
fieldvalue.
By default:
If length of
telephoneNumber > 6
then
Type = "E".

ContactID
default value ContactIDFieldName
FieldName
"PBC_NTLogin" 2
Foreign UserID PW_entry_nr
1
Obligated field
2
97
"Mapped to"
Foreign
ext_uniqueID
ExtensionID
PBX ID pbxID
User ID employeeID n.m.1 emp_uniqueID
First name givenName firstName (30)

2
Last name sn lastName (30)
Middle name middleName middleName (30)

merged value:
<givenName>
<MiddleName>." 3
Extension 2 telephoneNumber extension (16)
BSPT PBC_BSPT (40)
Extension Site
Email mail email (50)

VIP vip
Title personalTitle title (30)
Mobile mobile mobilePhone (25)

1
N.m. = Not Mapped
2
Obligated field
3
98
"Mapped to"
Pager Pager Pager (25)

Modem modem (25)
facsimileTelephone
Fax fax (25)
Number
Company company company (30)
Division division division (30)
Department department departmen (30)

alternateNumber
Alt. Extension
Alt. Extension
Site
physicalDeliveryOffi
ceName

Photo Photo (255)
NT Account sAMAccountName PBC_NTLogin (140)
PBC_LicencePlate1
Licenceplate 1
PBC_LicencePlate2
Licenceplate 2
Job Title title PBC_Jobtitle (40)
Initials initials n.m.2

3
1
2
N.m. = Not Mapped
3
99
"Mapped to"





Home Extension homePhone homePhone (25)
PBC_LoginName
Login Name
(80)
PBC_AdminRights
Admin Rights
(40)
PBC_usr_Identificati
User ID code
on (20)
PBC_usr_PinCode
Pincode
(20)
PBC_usr_UserAgent
User Agent
(400)
PBC_PersonalInfo
Info info
(400)
1
2
100
"Mapped to"

Can be one or more
values:
"1" = OfficeUser
"2" = Agent
"4" = Operator
Office User "8" = Administrator
OfficeUser
rights "16" = MyOffice user
"32" = Management
user
"128" = Phone Based
Agent
other permissions

LCS Presence
LcsPresenceState
State
Note (500)
X400 legacyExchangeDN X400 (255)
ipPhone n.m.1
displayName n.m. 1
generationQualifier n.m. 1
userAccountControl n.m. 1
description n.m. 1
wwwHomePage n.m. 1
url n.m. 1
1
N.m. = Not Mapped
101
"Mapped to"
userPrincipalName n.m. 1
PBC User
pbc_empuser1 (50)
Defined 1
PBC User
pbc_empuser2 (50)
Defined 2
PBC User
pbc_empuser3 (50)
Defined 3
PBC User
pbc_empuser4 (50)
Defined 4
PBC User
pbc_empuser5 (50)
Defined 5
PBC User
pbc_empuser6 (50)
Defined 6
PBC User
pbc_empuser7 (50)
Defined 7
PBC User
pbc_empuser8 (50)
Defined 8
PBC User
pbc_empuser9 (50)
Defined 9
PBC User
pbc_empuser10 (50)
Defined 10
PBC User
pbc_empuser11 (50)
Defined 11
PBC User
pbc_empuser12 (50)
Defined 12
PBC User
pbc_empuser13 (50)
Defined 13
PBC User
pbc_empuser14 (50)
Defined 14
PBC User
pbc_empuser15 (50)
Defined 15
1
N.m. = Not Mapped
102
"Mapped to"
PBC User
pbc_empuser16 (50)
Defined 16
PBC User
pbc_empuser17 (50)
Defined 17
PBC User
pbc_empuser18 (50)
Defined 18
PBC User
pbc_empuser19 (50)
Defined 19
PBC User
pbc_empuser20 (50)
Defined 20
103
"Mapped to"
104
A.7. Mappings Active Directory and PhoneWare
included in the synchronization of Active Directory towards PhoneWare.
The mapping is based on the default mapping script ADSI2PWMapping.vbs.
If desired the script can be customized to own need.
"Mapped to"
Active Directory PhoneWare
General ADSI2PWMapping.vbs Available Data
Descriptions Available Data Fields () Fields (size)
ContactID1 sAMAccountName ContactID
1
Operation Time1 OperationTime

default value:
on the
length of
Type1 Type
'telephoneNumber'
fieldvalue.
By default:
If length of
telephoneNumber > 6
then
Type = "E".
ContactID
FieldName
Foreign PBXID _site_group_code
Foreign UserID _owxempid
Foreign
_owxextid
ExtensionID
1
Obligated field
105
"Mapped to"

If Type = "E" then
PBX ID _site_group_code
<_site_group_code > =
"999"
Extension ID _entry_number
Costcenter _hier1_name (36)
User ID employeeID n.m. 1 _entry_number
First name givenName _forename (15)
Last name 2 sn _surname (40)
Middle name middleName n.m. 1 _user19 (30)
Fullname
Extension 2 telephoneNumber _extn_num (20)
BSPT

_email_address
Email mail
(50)
VIP _user11 (30)
1
Title personalTitle n.m. _title (4)
_mobile_number
Mobile mobile
(20)
Voicemail _voice_mail (20)
_pager_number
Pager Pager
(20)
Modem
facsimileTelephoneNum
Fax _fax_number (20)
ber
1
n.m. = Not Mapped
2
Obligated field
106
"Mapped to"
Company company _location (30)
Division division _user05 (30)
Department department _user01 (30)

_alt_extn_num
Alt. Extension
(20)
Alt. Extension
_alt_extn_site (8)
Site
physicalDeliveryOfficeN
Building _user13 (30)
ame
Photo _user17 (30)
NT Account sAMAccountName n.m. 1 _user08 (30)
Job Title title n.m. 1 _user06 (30)

1
Initials initials n.m. _initials (5)
User Defined 1 2
User Defined 2 2
User Defined 3 2
User Defined 4 2
Home Address 1
Home Address 2
Home City
1
N.m. = Not Mapped
2
107
"Mapped to"
Home State
Home Zip
Home Extension homePhone
Login Name
Admin Rights
Language
User ID code
Pincode
User Agent
Info info
Office User
rights
Password
SIP Uri
LCS Presence
State
LCS Presence
Note
X400 legacyExchangeDN
ipPhone
displayName
generationQualifier
userAccountControl
description
108
"Mapped to"
wwwHomePage
url
userPrincipalName
PBC User
_user01 (30)
Defined 1
PBC User
_user02 (30)
Defined 2
PBC User
_user03 (30)
Defined 3
PBC User
_user04 (30)
Defined 4
PBC User
_user05 (30)
Defined 5
PBC User
_user06 (30)
Defined 6
PBC User
_user07 (30)
Defined 7
PBC User
_user08 (30)
Defined 8
PBC User
_user09 (30)
Defined 9
PBC User
_user10 (30)
Defined 10
PBC User
_user11 (30)
Defined 11
PBC User
_user12 (30)
Defined 12
PBC User
_user13 (30)
Defined 13
PBC User
_user14 (30)
Defined 14
PBC User
_user15 (30)
Defined 15
109
"Mapped to"
PBC User
_user16 (30)
Defined 16
PBC User
_user17 (30)
Defined 17
PBC User
_user18 (30)
Defined 18
PBC User
_user19 (30)
Defined 19
PBC User
_user20 (30)
Defined 20
110
"Mapped to"
111
A.8. Mappings Active Directory and OpenWorX
included in the synchronization of Active Directory towards OpenWorX. The
mapping is based on the default mapping script ADSI2OWXMapping.vbs. If
"Mapped to"
Active Directory OpenWorX
General Available Data ADSI2OWXMapping.vbs Available Data
1

default value:
on the
Type1 Type
length of 'telephoneNumber'
fieldvalue.
By default:
If length of
telephoneNumber > 6 then
Type = "E".
ContactID
FieldName
Foreign UserID emp_uniqueID

Foreign
ext_uniqueID
ExtensionID
PBX ID pbxid
1
Obligated field
112
"Mapped to"
Costcenter costcenter (5)
User ID employeeID n.m.1 PW_entry_nr
First name givenName firstName (30)

2
Last name sn lastName (30)
prefix (30)
Middle name middleName
middleName (30)

merged value:
<givenName>
<MiddleName>." 3
Extension2 telephoneNumber extension (16)
BSPT
Extension Site
Email mail email (50)
VIP vip

Title personalTitle title (30)
Mobile mobile mobilePhone (25)
Voicemail voicemail (25)

Pager Pager pager (25)
Modem modem (25)
facsimileTelephone
Fax fax (25)
Number default value: " " 3
1
N.m. = Not Mapped
2
Obligated field
3
113
"Mapped to"

Company company If <company> is empty then company (30)
company = "NEC Philips" 1
Division division n.m.2 division (30)

If <department> is empty
Department department then department (30)
department = "NEC Philips"
1
alternateNumber
Alt. Extension
(25)
Alt. Extension
Site
physicalDeliveryOffi
ceName
Photo
NT Account sAMAccountName
Licenceplate 1
Licenceplate 2
Job Title title
Initials initials
3
User Defined 1
User Defined 23
User Defined 33
User Defined 43
Home Address
1
1
2
N.m. = Not Mapped
3
114
"Mapped to"
Home Address
2
Home City
Home State
Home Zip
Home
homePhone homePhone (25)
Extension
Login Name
Admin Rights
Language
User ID code
Pincode
User Agent info
Info
Office User
rights
Password
SIP Uri
LCS Presence
State
LCS Presence
Note
X400 legacyExchangeDN
ipPhone
displayName
generationQualifier
115
"Mapped to"
userAccountControl
description
wwwHomePage
url
userPrincipalName
PBC User pbc_empuser1

Defined 1 (50)
Defined 2 (50)
Defined 3 (50)
Defined 4 (50)
Defined 5 (50)
Defined 6 (50)
Defined 7 (50)
Defined 8 (50)
Defined 9 (50)
Defined 10 (50)
Defined 11 (50)
Defined 12 (50)
Defined 13 (50)
Defined 14 (50)
116
"Mapped to"
Defined 15 (50)
Defined 16 (50)
Defined 17 (50)
Defined 18 (50)
Defined 19 (50)
Defined 20 (50)


117
"Mapped to"





118
A.9. Mappings OpenWorX and PhoneWare
included in the synchronization of OpenWorX and PhoneWare. The
mapping is based on the default mapping scripts PW2OWXMapping.vbsand
OWX2PWMapping.vbs. If desired the script can be customized to own need.
"Mapped to"
OpenWorX PhoneWare
OWX2PWMapping.vbs
()
General Available Data PW2OWXMapping.vbs Available Data
Operation Time OperationTime OperationTime

default value:
on the
Type1 Type Type
value of field
'_site_group_code '.
By default:
If <_site_group_code> =
"999" then
Type = "E".
ContactID
FieldName
Foreign PBXID1 PW_site_group _site_group_code
Foreign UserID1 emp_uniqueID _owxempid
Foreign
ext_uniqueID _owxextid
ExtensionID1
1
Obligated field
119
"Mapped to"
OpenWorX PhoneWare
OWX2PWMapping.vbs
()

PBX ID1 pbxid (Using PBX Mapping _site_group_code
table)
Extension ID1 pbc_ext_id _entry_number
Costcenter costcenter (5) _hier1_name (36)
User ID1 PW_entry_nr _entry_number

if Type="I" and
<prefix> is NOT empty:
_forename = "<firstName>
<prefix>"
if Type="E" and
First name firstName (30) lastName has format _forename (15)
"<lastName>,
<firstName>":
_forename is extracted
from the lastName

if Type="E" and
lastName has format
"<lastName>,
Last name1 lastName (30) <firstName>": _surname (40)
_surname is extracted
from the lastName

prefix (30) n.m.2

Middle name _user19 (30)
middleName (30) n.m. 2
1
Obligated field
2
N.m. = Not Mapped
120
"Mapped to"
OpenWorX PhoneWare
OWX2PWMapping.vbs
()

merged value:
fullName = "<_surname>,
<_forename>"
Extension1 extension (16) _extn_num (20)
BSPT

_email_address
Email email (50)
(50)
VIP vip _user11 (30)
Title title (30) _title (4)

_mobile_number
(20)
Voicemail voicemail (25) _voice_mail (20)
_pager_number
Pager pager (25)
(20)
Modem modem (25)
Fax fax (25) _fax_number (20)
Company company (30) _location (30)
Division division (30) _user05 (30)
Department department (30) _user01 (30)

alternateNumber _alt_extn_num
Alt. Extension
(25) (20)

default value:
Alt. Extension
If <_alt_extn_num> is NOT _alt_extn_site (8)
Site
empty then
_alt_extn_site = "Local"
Building building (30) _user13 (30)
121
"Mapped to"
OpenWorX PhoneWare
OWX2PWMapping.vbs
()
Photo _user17 (30)
NT Account _user08 (30)
Job Title _user06 (30)
Initials _initials (5)
User Defined 1 1
User Defined 2 1
User Defined 3 1
User Defined 4 1
Home Address 1
Home Address 2
Home City
Home State
Home Zip
Home Extension homePhone (25) n.m.2
Login Name
Admin Rights
Language
1
2
N.m. = Not Mapped
122
"Mapped to"
OpenWorX PhoneWare
OWX2PWMapping.vbs
()
User ID code
Pincode
User Agent
Info
Office User
rights
Password
SIP Uri
LCS Presence
State
LCS Presence
Note
X400
_user01 (30)
Defined 1 (50)
_user02 (30)
Defined 2 (50)
_user03 (30)
Defined 3 (50)
_user04 (30)
Defined 4 (50)
_user05 (30)
Defined 5 (50)
_user06 (30)
Defined 6 (50)
_user07 (30)
Defined 7 (50)
_user08 (30)
Defined 8 (50)
123
"Mapped to"
OpenWorX PhoneWare
OWX2PWMapping.vbs
()
_user09 (30)
Defined 9 (50)
_user10 (30)
Defined 10 (50)
_user11 (30)
Defined 11 (50)
_user12 (30)
Defined 12 (50)
_user13 (30)
Defined 13 (50)
_user14 (30)
Defined 14 (50)
_user15 (30)
Defined 15 (50)
_user16 (30)
Defined 16 (50)
_user17 (30)
Defined 17 (50)
_user18 (30)
Defined 18 (50)
_user19 (30)
Defined 19 (50)
_user20 (30)
Defined 20 (50)
PBC Yes/No 1 pbc_empyesno1 _yesno01
124
"Mapped to"
OpenWorX PhoneWare
OWX2PWMapping.vbs
()
125
Appendix B. Customizing Mapping scripts
All available standard configurations from the Table 1 Possible configurations in Aranea
1.4.3 (page 5) can be customised to fit the customers need. Because of the design of
Aranea, the basic customising of the tool is not complicated.
Figure 44: Global Architecture of Aranea
Aranea links two databases with a Contact source and a Contact Sink Component, what
actually is synchronised is based on the Conversion script. This Visual Basic script can be
easily adapted. This chapter gives an example how to do this based on a synchronisation of a
CSV file and the Business ConneCT (United) database.
WARNING: CHANGING THE CONVERSION SCRIPT CAN LEAD TO LOSS OF

DATA IF NOT EXECUTED PROPERLY, MAKE SURE YOU ARE
FAMILIAR WITH THE PROCEDURE AND MAKE BACKUPS
BEFORE EXECUTING ARANEA
126
B.1. Transformation Mapping Process
The mapping process in Aranea is a generic process for each types of configuration. The
contacts will be mapped one-by-one using a Transformation Script. This process is
described in Figure 45. As an example we use the CSV to BCT as starting-point.
Figure 45: Process flow of mapping contact data (CSV to BCT).
127
The actual process is initiated by the Aranea Agent. This will retrieve the contacts from the
data source (CSV). Then it will process the contacts one-by-one and if the mapping is
successful, it stores them in the data sink (BCT). When all contacts have been processed,
the mapping process will be finished.
In detail the steps take as shown in Figure 45.

1. Query the contacts from the data source.
2. Start Mapping process by calling the function Initialize().
3. Get the first contact from the queried list.
4. Is the contact processable? No, goto step 11.
5. Start the mapping if contact data by calling function MapContact().
6. Check if the preconditions are met. These are the obligated data fields as mentioned in
appendix A.3.
7. Preconditions are not met. Skip processing contact.
Get the next contact from the queried list. Continue with step 4.
8. Do the actual mapping of the data fields by calling function SetGlobalUNI(). (This
function is specific for CSC to BCT. In other mapping scripts they have the same
naming conventions: SetGlobalXXX(), where XXX can be any name).
9. Store the contact in the data sink.
10. Get the next contact from the queried list. Continue with step 4.
11. Finalize Mapping process by calling the function Terminate().
Note: these steps do not describe the exceptions. Of course when one (or more) contacts
could not be mapped (due to not meting the pre-conditions), it is reported to the Aranea
Agent. With the Aranea Configurator the reports of the failed tasks can be reviewed.
B.2. Example how to change a mapping script.
In this example we will have a look at the mapping script CSV2UNIMapping.vbs. This is
the default mapping who will come with the example CSV file FileSourceExample.csv.
(The files can be found at folder location C:\NEC\Data Files\Aranea-module).
The CSV file has following lines to process:

Operation, ContactID, Extension, pbxID, Mobile, LastName, FirstName, prefix,
email, AccountName
-,0007,1000,2,'0612345678','Bond','James','','james.bond@mi6.com', ''
+,0008,1001,2,'0687654321','Tanasescu','Adela','','adela.tanasescu@mi6.com',''
+,0009,1022,2,'0687653322','Baas','Johan','van de','Johan.Baas@xyz.com',''
128
There are three contacts to process. The first one is a contact which should
be deleted form the data sink. The next two are inserts/updates.
Looking at the mapping process as described above, the Aranea Agent will
first call function Initialize() and then for each contact (so three times) it
will call function MapContact() and finally function Terminate().
In the mapping script you can find the functions as below:
Figure 46: Script function Initialize().
Figure 47: Script function Terminate().
129
Figure 48: Script function MapContact().
130
Figure 49: Script function SetGlobalUNI().
131
As you can see the function SetGlobalUNI(), does the actual mapping.
For example:
Contact("lastName") = SourceContact("LastName")
Contact("firstName") = SourceContact("FirstName")
Contact("extension") = SourceContact("Extension")
Contact("middleName") = SourceContact("prefix")
The LastName field from the CSV file is mapped to the lastname field of
the BCT. This is also for FirstName, Extension and middleName.
A view lines later there is also a mapping of the fullName:
If Len(Contact("lastName")) > 0 Then

Contact("fullName") = Contact("lastName")
If Len(Contact("firstName")) > 0 Then
Contact("fullName") = Contact("fullName") & ", " &
Contact("firstName")
End If
If Len(Contact("middleName")) > 0 then
Contact("fullName") = Contact("fullName") & " " &
UCase(Left(Contact("middleName"), 1)) & "."
End If
End If
It is merged by clueing lastName, firstName and middleName

together. This is only done when the lastName is available.
If we use the contact data from the example CSV we will get for contact 3:
lastName = Baas
firstName = Johan
middleName = van de
The fullName will be: Baas, Johan v.
Lets say we like to extend the CSV fields with and additional fields
ourCompany, ourDivision and ourDepartment. The header of the
CSV file has to be extended with these field names:
Operation, ContactID, Extension, pbxID, Mobile, LastName, FirstName, prefix,
email, AccountName, ourCompany, ourDivision, ourDepartment
132
It is important to use clear appellations for the fieldnames. These names
will be reused in the mapping script. You can use any name you like as
long as they consist of the
- Use alphanumeric characters like: a-z, A-Z, 0-9, _
- Do not use symbolic characters like: or , or or ^ or + or -
- Do not start a field name with a number.
- 01234Test -> NO
Example of correct field names:

- Test01234 -> OK
- Test_01234 -> OK
- _Tst_012 -> OK
Note: Aranea does not check the used characters for the names. If you
use these characters it might be that the mapping script will not
work properly.
Now the header of the CSV file has been extended, the data lines need to
provide the data. We extend the above data lines:
+,0008,1001,2,'0687654321','Tanasescu','Adela','','adela.tanasescu@mi6.com','',
MyCompany, MyDivision, MyDepartment
+,0009,1022,2,'0687653322','Baas','Johan','van de','Johan.Baas@xyz.com','',
MyCompany, MyDivision, MyDepartment
(Note that the delete data line has been removed. It has no contribution to
this subject. It does not mean however that these types of data lines are not
allowed! It is only removed for surveyability.)
Before processing these data lines, we need to update the mapping script.
According to the mapping process, the mapping of the data fields must be
done in the function SetGlobalUNI(). It is only useful to do the mapping if
the preconditions are met.
We like to map the new fields of the data source to the same (or similar
named) fields of the data sink:
ourCompany -> company
ourDivision -> division
ourDepartment -> department
133
In the mapping script we will update the following lines:
Contact("company") = ""
Contact("division") = ""
Contact("department") = ""
into
Contact("company") = SourceContact("ourCompany")
Contact("division") = SourceContact("ourDivision")
Contact("department") = SourceContact("ourDepartment")
The mapping script will now copy for each contact the data of the data
fields ourCompany, ourDivision and ourDepartment from the data
source to the data fields company, division and department of the
data sink.
Save the mapping file and test the file using Aranea Configurator by:
- Starting a Full sync (see 1.3.2 How to start a Full synchronization of a
configuration?).
- Or by starting the scheduled task Aranea Scheduled Task ANY2UNI in
Windows Scheduled Tasks.
Please make sure to backup the database first before executing it on a live
system.
134
Appendix C. LDAP Terminology
LDAP or Lightweight Directory Access Protocol is mostly associated with data

synchronisation with Active Directory. In principle this is not true, instead it is a protocol
that can be used with any LDAP compliant database. For the scope of this manual we will
focus only on Active Directory as this is the only LDAP compliant database supported by
Aranea. This appendix gives a short overview of LDAP terminology to help configuration of
Aranea.
C.1. The LDAP syntax
- LDAP Notation: LDAP uses its own name convention to speed-up searching in
a large database like Active Directory. LDAP names can be translated into fully
qualified domain names and vice versa. For instance the administrator@nec-
philips.com becomes cn=administrator, cn=users, dc=nec-philips, dc=com in
LDAP notation. Below are some examples of attributes you may be able to use
in the name string, depending on your directory structure:
- OU=organizational unit;
- DC=domain controller;
- CN=common name;
- DN=distinguished name.
- Organisational Unit: Active Directory is arranged in a tree structure, on top of
that organisational units can be defined to group resources (users / printers/
pcs). These OUs can be included in the search base. For instance if you only
want to include the Business ConneCT users of the nec-philips.com domain in
an Aranea update you create an OU named BCT and move all Business
ConneCT users to this OU. The LDAPBase in this example becomes: ou=BCT,
dc=nec-philips, dc=com.
C.2. Using LDAP syntax
It is possible to query a specific list of users from a specific AD location or/and by using a
LDAP filter. This filter uses the LDAP syntax as specified in RFC2251 and is a LDAP string
representation of the search query executed at the LDAP base location. LDAP Search
Filters are described in RFC2254.
When an extended query is needed, the following two items can be provided:
1. LDAPBase: The location to conduct the search in. The Search base indicates where in
the LDAP data tree you wish to begin the search. An LDAP directory is arranged in a
tree structure (directory information tree, or DIT), with a root and various branches
off this root. The LDAPBase you enter is used to indicate at which node the search
135
should originate. This must be the Distinguished Name of this node in LDAP notation.
A typical example for this configuration item is:
LDAPBase Description
DC=mydomain,DC=COM Connect to domain controller mydomain.com
OU=Sales, DC=mydomain, DC=COM Connect to default domain controller for

mydomain.com and Organization Unit Sales
directoryserver/OU=Sales, Connect to domain controller directoryserver

DC=mydomain, DC=COM
for mydomain.com and Organization Unit
Sales.
2. LDAPFilter: Here you can define a filter to get a subset of users from the AD
environment. The LDAP import might contain more data then required. When using
LDAP you can add criteria to exclude certain records from the search base by using a
filter. Before you can filter, you have to know what to filter. This can only be done by
looking at the data currently in the LDAP directory via an LDAP browser or the LDAP
server application. Once you know the structure of your LDAP server, and understand
the data within the folders, you can then begin to devise the plan on how and what you
want to filter. For example, to search for all people named John Doe, type cn=John
Doe. This search filter matches entries with the common name John Doe.
Below are the operators you can use in a search filter. Search filters can be combined
with Boolean operators to form more complex search filters.
Note that it is not required to specify both parameters. If the LDAPBase is left empty, the
default AD location is queried. This is the domain of the server where Aranea is installed on.
Below some examples in using LDAP syntax for Active Directory queries. Search filters can
be combined with Boolean operators (= &, | or !) to form more complex search filters.
136
LDAPFilter Description
(&(objectCategory=Person)(objectClass= Every user object from the category

user)) person
user)(cn=Andy)) person where the common name is
Andy.
user)(mail=*)) person who has email filled in.
user)(|(mobile=065*)(mobile=062*))) person with Mobile numbers starting
with 065 or 062.
In addition to the above filter options, it is also possible to use Bitwise Operators. This can
be used to for example filter out the non-active accounts on AD control bits.
LDAP Bitwise Operators Description
1.2.840.113556.1.4.803 LDAP_MATCHING_RULE_BIT_AND A match is found only

if all bits from the attribute match the value. This rule is
equivalent to a bitwise AND operator.
1.2.840.113556.1.4.804 LDAP_MATCHING_RULE_BIT_OR
A match is found if any bits from the attribute match the
value. This rule is equivalent to a bitwise OR operator.
Example using a bitwise operator to filter out the non-active users:
LDAPFilter Description

user)(telephoneNumber=*) person with any telephoneNumber
(!userAccountControl:1.2.840.113556.1. filled in and userAccountControl
4.804:=2)) BITWISE OR with 2 (2 = bitlocation
for disabled account)
More information about the LDAP syntax can be found in the international standardisations
RFC2251 and RFC2254.
137
Appendix D. Aranea Support Tools
After installation, Aranea has three supporting tools:
- Diagnostic Monitor;
- Security Configurator.
All three tools can be started via Start-> All Programs -> Aranea ->Support.
These tools will be described in the sections below.
D.1. Diagnostic Monitor
With the Diagnostic Monitor, you can see events as they happen. So you can check the
progress and behaviour of a module.
You find the Diagnostic Monitor in Start -> All Programs -> Aranea -> Support
-> Diag@Net Monitor.
In the left pane, you can select a process and in the right pane you see the Events and
Exceptions for that process as they happen.
In the menu Options and Trace Level Settings, you can select more detailed monitoring
(tracing) for some modules.
D.2. Security Configurator
The Security Configurator can be used to:
- Enable NEC-Philips applications in case the Windows Firewall is turned on;
Note: The Windows Firewall is introduced in Windows XP Professional, Service Pack 2 and
Windows Server 2003, Service Pack 1.
- Enable DCOM and other Services or Tasks, if the password of the PBC-UserAccount
has changed. This can happen if the security policy forces you to change passwords
every x days, or if you install another NEC-Philips application on the same server.
Note: If you changed either the name (PBC-UserAccount) or the password with the Security
Configurator, you have to run it again after a reinstall or upgrade of NEC Philips
applications.
138
You find the Security Configurator in Start -> All Programs -> Aranea ->
Support ->Security Configurator.
After starting the Security Configurator, the Windows Firewall tab shows. Aranea has no
services affected by the windows firewall so in a stand alone installation this screen will be
empty.
Figure 50: Identity tab of the Security Configurator.
Selecting the Identity tab, Figure 50 screen appears. This is a list of DCOM components that
are started using the username: PBC-UserAccount this user is automatically created during
installation of a number of NEC Philips products, Aranea included. The password of this
user is randomly created according to the strong password demands of the Windows
environment. When more applications are installed on the same machine, it can happen that
the password is not the same for all installations, leading to system failure of.
139
To reset the password for all applications at one press: Modify. Select the use the Use
generated strong password tickbox and Renew to change the password, or alternatively,
remove the tickbox and manually enter the new password. Select OK to reset the PBC-
UserAccount for all DCOM objects at one.
Figure 51: Modify password of PBC-UserAccount
140
Appendix E. Troubleshooting
? Not able to login: unknown user name or bad password...

The password of the PBC-UserAccount might be reset after installation of Aranea. The
PBC-UserAccount is used for DCOM-settings on component to give the component
password, use the Security Configurator (see appendix D.2 Security Configurator) to
manually reset the password. Rebooting the system is advisable.
? Aranea is not visible anymore as an installed program...

After cancelling an Uninstall of Aranea from the "Add or Remove programs" tool of the
Control Panel, the program entry for Aranea (Aranea Install) disappeared from the "Add or
Remove programs" tool. Actions to be taken:
1. Initiate Install of Aranea from the "Add or Remove programs" tool.
2. In the first screen click next.
3. In the second screen click cancel.
? Uninstall did not remove everything...

Reboot the server. After reboot the components are gone.
? The jointed PBX name drop down list is empty...(BCT 3.1)

This happens only the first time when you configured the PBX mappings and access the
"jointed PBX name" drop down list. You first need to exit the mappings screen, then re-
enter it before the jointed PBX name dropdown list becomes filled with the possible PBXs
to pick from. This is improved in Business ConneCT 3.1.
? The extension which was deleted in OpenWorX is still visible in the MyOffice and
PhoneWare database...
Extensions should be maintained either in OpenWorX or in MyOffice. Furthermore, Aranea
cannot delete extensions in the United database when they are imported by MATSync.
141

Aranea Cem

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Aranea Cem

Uploaded by

Copyright:

Available Formats

Aranea - Installation and Configuration

NOTE THAT FOR NEW INSTALLATIONS OPENWORX IS NOT SUPPORTED

1 INTRODUCTION TO ARANEA ................................................................ 5

Aranea 1.4.3 supports:

From Phonebook OpenworX1 BCT MA4000

Phonebook Yes Yes Via United

BCT Yes No Yes

MA4000 Via United No Yes

CSV File Yes Yes Yes No

Active Yes Yes Yes No

1.2 THE ARANEA ARCHITECTURE

Figure 1: Global Architecture of Aranea

1.3.1 How to start or stop a configuration?

Figure 2: Start / stop a configuration

1.3.2 How to start a Full synchronization of a configuration?

Figure 3: Start Full Synchronization of a configuration.

1.3.3 How can I see the progress of a configuration?

Figure 4: Running tasks show the progress of a configuration.

A task line consists of three parts:

Figure 5: Task info window showing task report.

1.3.4 How to change a configuration?

Note: Stop the configuration first before editing.

Aranea Configuration Where must Aranea be installed?

BCT to Install Aranea on the PC where the Business ConneCT 4.x /

OpenWorX to PhoneWare.1 Install Aranea on the PC where OpenWorX is running.

CSV/ Active Directory to Install Aranea on the PC where OpenWorX is running.

Aranea supports an SQL type database:

2.2.1 Installing Aranea

Before you install Aranea, check that:

Figure 7: Select the desired base configuration (a or b)

a. Select OpenWorX / PhoneWare if you want to synchronize between

b. Select MyOffice@Net / PhoneWare if you want to synchronize between

c. Select Business ConneCT / MA4000 / PhoneWare if you want to synchronize

Figure 9: OpenWorX and PhoneWare possible configurations

For OpenWorX / PhoneWare there is a maximum of three possible configurations

NOTE THAT FOR NEW INSTALLATIONS OPENWORX IS NOT SUPPORTED

Figure 10: MyOffce@Net and PhoneWare possible configurations

For MyOffice@Net / PhoneWare there is a maximum of two possible

Figure 11: Business ConneCT / MA4000 / PhoneWare possible configurations

For Business ConneCT / MA4000 / PhoneWare there is a maximum of three

Select the required components and press Next.

Figure 12: Provide Business ConneCT (United) data source properties.

a. For connection to Business ConneCT you have to provide:

b. For connection to MA4000 you have to provide:

d. For connection to PhoneWare you have to provide:

WARNING: IF YOU INSTALL ARANEA ON A PC WHERE ANOTHER NEC-

13. Now follow the correct configuration procedure in

2.2.2 Upgrading Aranea

- Stop currently running configurations of Aranea 1.4.x.

2.2.3 Uninstalling Aranea

Before you uninstall Aranea, check that:

- Stop currently running configurations of Aranea.

6. The uninstaller guides you through the entire uninstallation.

8. Aranea is now uninstalling.

Data Source/ Configuration

Send updates to Enter Yes or No to configure if the updates need to

Active Directory DomainName The domain name of the Active Directory.

LDAPFilter The default LDAP query can be extended with specific

What data is synchronised?

Synchronization between the different data sources contains a set of data

Operation1 Type of Operation needed fro processing.

Type1 Type of Contact (internal/External)

User ID1 Unique identifier of User in the source db.

ExtensionID1 Unique identifier of Extension in the source db.