Avaya Integrated Management Application Notes: Release 3.1 Windows Installation Properties - Issue 1.0

Transcription

1 Avaya Integrated Application Notes: Release 3.1 Windows Installation Properties - Issue 1.0 Abstract This paper attempts to provide the customer with relevant information about the Integrated Microsoft Windows-based applications in order for customers to make an assessment of the necessary protocols and services needed to run on their Windows server. Integrated White Paper 1 of 26

2 Table of Contents 1. INTRODUCTION NOTATION, TERMINOLOGY AND ACRONYMS INTEGRATED MANAGEMENT RELEVANT DIRECTORIES: INTEGRATED MANAGEMENT COMMON COMPONENTS: INTEGRATED MANAGEMENT LAUNCH PAGE: AVAYA SITE ADMINISTRATION: VOICE ANNOUNCEMENT MANAGER: VOIP MONITORING MANAGER: WebLM: MSDE: NETWORK MANAGEMENT: PROVISIONING AND INSTALLATION MANAGER (PIM): NETWORK MANAGEMENT SYSTEM INTEGRATION (NMSI): TOMCAT SERVLET CONTAINER APACHE WEB SERVER SCP/SSH JDK INTEGRATED MANAGEMENT PORT USAGE CONCLUSION ADDITIONAL REFERENCES... 4 Integrated White Paper 2 of 26

3 1. Introduction This paper covers information on what the Integrated software configures on the customer-provided Windows Server. It covers the following: 1. Installed Files, Default Directory Locations and Registry Entries 2. Application Communication Information Service Default Transport Protocol Direction This paper attempts to provide the customer with relevant information about the Integrated Windows-based applications in order for customers to make an assessment of the necessary protocols and services needed to run on their Windows server. Integrated White Paper 3 of 26

4 1.1. Notation, Terminology And Acronyms The following table gives meanings for most of the terms and acronyms used in this document. Term API ASA CLAN FIFO FTP GUI HKCU HKLM HTML HTTP HTTPS IP NM NMSI NNM OV PIM PPP RMATS RMI SAT SMTP SNMP SSH T&M TCP TSC UDP VAM VMM VNC VPN Meaning Application Programming Interface Avaya Site Administration Control-LAN, a Communication Manager IP interface circuit pack First In First Out File Transfer Protocol Graphical User Interface HKey Current User HKey Local Machine HyperText Markup Language HyperText Transfer Protocol HyperText Transfer Protocol Secure Internet Protocol System Integration Node Manager HP OpenView Provisioning and Installation Manager Point-to-Point Protocol Remote Maintenance and Test System Remote Method Invocation System Access Terminal Simple Mail Transfer Protocol Simple Protocol Secure Shell Time and Materials Transmission Control Protocol Technical Service Center User Datagram Protocol Voice Announcement Manager VoIP Monitoring Manager Virtual Computing - software that makes it possible to view and fully-interact with one computer from any other computer or mobile device anywhere on the Internet Virtual Private Integrated White Paper 4 of 26

5 2. Integrated Relevant Directories: This section lists the directories used and created by various Integrated applications. The directories are the locations on the Windows server where the Integrated files are installed Integrated Common Components: C:\Program Files\Avaya\Required Components contains Integrated Client and Server Configuration GUI files, launchapp, and *.vl files C:\Program Files\Avaya\JRE C:\Program Files\Avaya\Third Party Installed contains the Java Runtime Environment needed by various applications contains copies of all the third party installers used for IM install HKLM\SOFTWARE\Avaya\Avaya Integrated \ HKLM\SOFTWARE\Avaya\JRE 1.4.2_06\ HKLM\SOFTWARE\Avaya\JRE 1.4.2_06\AppsInstalled\ Environment Variables: The following entries are made in the environment registry at HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\: PROP_PATH Integrated White Paper 5 of 26

6 2.2. Integrated Launch Page: C:\Program Files\Avaya\Home Page\html contains Integrated Launch Page HTML files HKLM\SOFTWARE\Avaya\Avaya Integrated \ Environment Variables: The following entries are made in the environment registry at HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\: AIM_VERSION AIM_FPM AIM_CCS AIM_GMS AIM_EPI AIM_IMD AIM_EPI_PORT AIM_MSA AIM_PATH AIM_MSG AIM_SERVER AIM_NSM AVAYA_ROOT AIM_PA ASA_FLAG AIM_VOIP VAM_FLAG MM_FLAG AIM_VMSC AIM_IEM AIM_MM Integrated White Paper 6 of 26

7 2.3. Avaya Site Administration: C:\Program Files\Avaya\Site Administration\bin C:\Program Files\Avaya\Site Administration\data C:\Documents and Settings\<username>\ Application Data\Avaya\Site Administration\user C:\Documents and Settings\<username>\ Application Data\Avaya\Site Administration\ user\backup program executable files and *.dll files data files; such as bitmaps, defaults and list files location of persist.dat, template data, button label print data, etc Also default directory for reports and import/export tasks Backup of persist.dat, template data, button label print data, etc HKLM\SOFTWARE\Avaya\Avaya Integrated \ HKLM\SOFTWARE\Avaya\Avaya Integrated Avaya Site Administration 3.1\ HKLM\SOFTWARE\Avaya\Avaya Site Administration\ HKLM\SOFTWARE\Avaya\Avaya Site Administration\SASL Library\ HKLM\SOFTWARE\Avaya\Avaya Site Administration \System\ HKCU\SOFTWARE\Avaya\Avaya Site Administration\ Environment Variables: The following entries are made in the environment registry at HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\: AIM_PATH AIM_SERVER SA_PATH DSA_PATH Integrated White Paper 7 of 26

8 2.4. Voice Announcement Manager: C:\Program Files\Avaya\Voice Announcement Manager\bin C:\Program Files\Avaya\Voice Announcement Manager\data C:\Program Files\Avaya\Voice Announcement Manager\images C:\Program Files\Avaya\Voice Announcement Manager\ossidoc C:\Program Files\Avaya\Voice Announcement Manager\resources C:\Documents and Settings\<username>\ Application Data\Avaya\Voice Announcement Manager\user contains program executable Jar files contains sample CSV files and backup policy files contains JPEG, GIF and bitmap image files contains OSSI mapping files contains property files for all supported languages; only default file and English US file is present contains data files; such as property files, error logs, status logs, etc Also default location for storage of announcement files HKLM\SOFTWARE\Avaya\Avaya Integrated \ HKLM\SOFTWARE\Avaya\Avaya Integrated Administration Tools 3.1\ Environment Variables: The following entries are made in the environment registry at HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\: AIM_PATH AIM_SERVER VAL_PATH JRE2_BIN Integrated White Paper 8 of 26

9 2.5. VoIP Monitoring Manager: C:\Program Files\Avaya\VoIP Monitoring Manager contains program executable Jar files under the jars subdirectory HKLM\SOFTWARE\Avaya\Avaya Integrated \ HKLM\SOFTWARE\Avaya\Avaya Integrated VoIP Monitoring Manager 3.1\ HKLM\SOFTWARE\Avaya\VoIP Monitoring Manager\ HKLM\SOFTWARE\Avaya\VoIP Monitoring Manager\RtcpMon\ HKLM\SYSTEM\CurrentControlSet\Services\VoIP Monitoring Manager Server HKLM\SYSTEM\CurrentControlSet\Services\VoIP Monitoring Manager Server\Parameters HKLM\SYSTEM\CurrentControlSet\Services\VoIP Monitoring Manager Server\Security HKLM\SYSTEM\CurrentControlSet\Services\VoIP Monitoring Manager Server\Enum Environment Variables: The following entries are made in the environment registry at HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\: AIM_PATH AIM_SERVER VMON_PATH JRE2_BIN AIM_VOIP WebLM: C:\Program Files\Apache Group\Tomcat 4.1\ webapps\weblm contains expanded war file, once WebLM is started None Environment Variables: The following entries are made in the environment registry HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\: WEBLM_IP WEBLM_PORT CATALINA_HOME JAVA_HOME Integrated White Paper 9 of 26

10 MSDE: C:\Program Files\Microsoft SQL Server contains program executable files HKLM\SOFTWARE\Microsoft\MSSQLSERVER\ SQL Logins Created: sa (user defines password during installation) VmmUser Integrated White Paper 10 of 26

11 2.6. : C:\Program Files\Avaya\ contains program executable Jar files HKLM\SOFTWARE\Avaya\Avaya Integrated \ HKLM\SOFTWARE\Avaya\Avaya Integrated 3.1\ HKLM\SOFTWARE\Avaya\Avaya Integrated 3.1\ Components\ HKLM\SOFTWARE\Avaya\Avaya Integrated 3.1\ Versions\ Environment Variables: The following entries are made in the environment registry at HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\: AIM_VERSION AIM_FPM AIM_CCS AIM_GMS AIM_EPI AIM_IMD AIM_EPI_PORT AIM_MSA AIM_PATH AIM_MSG AIM_SERVER AIM_NSM NM_PATH AIM_PA NM_INSTALLED AIM_VOIP JRE2_BIN AIM_VMSC AVAYA_ROOT AIM_IEM CYGWIN AIM_MM SCP_PATH ASA_FLAG CV_PATH VAM_FLAG CVS_HOME MM_FLAG LUL_HOME Integrated White Paper 11 of 26

12 2.7. Provisioning and Installation Manager (PIM): C:\Program Files\Avaya\Jboss3.2.5 contains program executable Jar files HKLM\SOFTWARE\Avaya\Avaya Provisioning and Installation Manager 3.1\ HKLM\SOFTWARE\Avaya\Avaya Provisioning and Installation Manager\ HKLM\SOFTWARE\Avaya\General\ NOTE: PIM must be installed on the same server as. Integrated White Paper 12 of 26

13 2.8. System Integration (NMSI): The installation of NMSI will follow the directory structure created by the HPOV installation. Since NMSI only integrates with HPOV, all files for NMSI will be installed under the HPOV installation directory. Following subdirectories are created under the main installation directory of HPOV: \avaya\ pre-configuration folder \classes\ mfpma.jar \bin\ nmsitalk.exe \www\htdocs\bitmaps\c\vendor/avaya\ bitmap files delivered by development \registration\c\avaya\ VisAbility \www\registration\jovw\c\ VisAbility \bitmaps\c\vendor\avaya Bitmap files delivered by development \fields\c\ Avaya_nmsi_fields and Avaya_voice_fields \symbols\c\vendor\avaya\ Symbol files delivered by development \snmp_mibs\vendor\avaya *.asn1 mibs delivered by development HKLM\SOFTWARE\Avaya\Avaya Integrated \ HKLM\SOFTWARE\Avaya\Avaya Integrated NMSI 3.1\ HKLM\SOFTWARE\Avaya\JRE\ Environment Variables: The following entries are made in the environment registry at HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\: AIM_PATH AIM_IMD NMSI_PATH JRE2_BIN Integrated White Paper 13 of 26

14 2.9. Tomcat Servlet Container The tomcat web server installs into the standard Tomcat Windows installation locations including the following directories: C:\Program Files\Apache Group\Tomcat 4.1 contains executable files HKLM\SOFTWARE\Apache Group\Tomcat\ Apache Web Server The apache web server installs into the standard Apache Windows installation locations including the following directories: C:\Program Files\Apache Group\Apache2 contains executable files HKLM\SOFTWARE\Apache Group\Apache\ SCP/SSH OpenSSH for Windows used for SCP C:\Program Files\OpenSSH\ C:\Program Files\OpenSSH\bin\ contains executable files HKLM\SOFTWARE\Cygnus Solutions\ Cygwin\ Environment Variables: The following entries are made in the environment registry at HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\: CYGWIN SCP_PATH Integrated White Paper 14 of 26

15 2.12. JDK Needed for Tomcat C:\j2sdk1.4.2_06\ C:\j2sdk1.4.2_06\bin\ C:\Program Files\Java C:\Program Files\Java\bib\ contains executable files contains executable files HKLM\SOFTWARE\JavaSoft\Java Development Kit HKLM \SOFTWARE\JavaSoft\Java Runtime Environment Integrated White Paper 15 of 26

16 3. Integrated Usage Source Source Source Table 1: Windows-Based Application Communication Information Transport Protocol Direction Description IP Phones Yes VMM Server 5005 Yes TCP RTCP In IP Phones send IP statistics to VMM Server Medpro Boards Yes VMM Server 5005 Yes TCP RTCP In Medpro Boards send IP statistics to VMM Server Media Gateways 5005 Yes VMM Server 5005 Yes TCP RTCP In Media Gateways send IP statistics to VMM Server VMM Server No SQL Database 1433 No TCP sql In SQL Database Server and Monitor VMM Client No VMM Server 1099, 49177, 51173, No TCP RMI In VMM Client to Server communication (Note: VMM Client can be configured to tunnel RMI via HTTP VMM Server Yes VMM Monitor Yes TCP custom In Used by VMM Server to configure the VMM Monitor WebLM No Tomcat 3999 Yes TCP http In Used by WebLM to communicate to Tomcat Web/Servlet Server PIM No JBoss Yes TCP RMI In Used by JBOSS on PIM Server PIM No Tomcat 2020 Yes TCP http In Used by PIM to communicate to Tomcat Web/Servlet Server; Part of JBoss installation Integrated White Paper 16 of 26

17 Source Source Source Transport Protocol Direction Description No Multiple 2843 Yes TCP RMI In Used for Client access, RMI, services; cv.jum.rmi.port No Multiple 2400 Yes TCP Multiple In Used for Client access, RMI, services; cv.trap.port No Multiple 2401 Yes TCP Multiple In Used for Client access, RMI, services; cv.launcher.port No Multiple 2402 Yes TCP Multiple In Used for Client access, RMI, services; llm.clients.port No Multiple 2403 Yes TCP RMI In Used for Client access, RMI, services; fileaccess.rmi.port Integrated White Paper 17 of 26

18 Source Source Source Transport Protocol Direction Description No Multiple 2404 Yes TCP RMI In Used for Client access, RMI, services; userver.rmi.port No Multiple 2405 Yes TCP Multiple In Used for Client access, RMI, services; llm.servers.port No Multiple 2406 Yes TCP Multiple In Used for Client access, RMI, services; userver.socket.port No Multiple 2407 Yes TCP Multiple In Used for Client access, RMI, services; service.smuserdb.port No Multiple 2408 Yes TCP Multiple In Used for Client access, RMI, services; service.snmpinfo.port Integrated White Paper 18 of 26

19 Source Source Source Transport Protocol Direction Description No Multiple 2409 Yes TCP RMI In Used for Client access, RMI, services; smon.rmi.port No Multiple 2410 Yes TCP Multiple In Used for Client access, RMI, services; nmlogin.local.port No Multiple 2411 Yes TCP Multiple In Used for Client access, RMI, services; nmlogin.remote.port No Multiple 2412 Yes TCP RMI In Used for Client access, RMI, services; nmlogin.rmi.port No Multiple 2413 Yes TCP Multiple In Used for Client access, RMI, services; llm.fileacess.port Integrated White Paper 19 of 26

20 Source Source Source Transport Protocol Direction Description No Multiple 2500 Yes TCP RMI In Used for Client access, RMI, services; smserver.rmi.port No Multiple 2330 Yes TCP RMI In Used for Client access, RMI, services; amserver.rmi.port No Multiple 2331 Yes TCP RMI In Used for Client access, RMI, services; amprocess.rmi.port No Multiple 2332 Yes TCP Multiple In Used for Client access, RMI, services; llm.amclient.port No Multiple Yes TCP RMI In Used for Client access, RMI, services; rmiport.min and rmiport.max Integrated White Paper 20 of 26

21 Source Source Source Transport Protocol Direction Description No Multiple 2546 Yes TCP RMI In Used for Client access, RMI, services; cv.jumdb.rmi.port NM Client No NM Server 1980 Yes TCP Multiple In Multi-Socket Trap Manager No NM Server 6169 Yes TCP RMI In RMI port for Trap Manager VMM Server No 162 No UDP SNMP Out Optional VMM SNMP Traps System PC No Tomcat 80 Yes TCP http In Tomcat Servlet Container PC PC PC PC PC No Apache 8080 Yes TCP http In Apache Web Server (Integrated Database) No Apache 443 No TCP https In Apache Secure Web Server (Integrated Database) No Windows Server 22 No TCP SSH In Incoming SSH access No Windows Server 23 No TCP telnet In Optional: Incoming Telnet No Windows Server 21 No TCP ftp In Optional: Incoming FTP Integrated White Paper 21 of 26

22 Source VMM, Console Console Source Source No NMS, Communication Manager and other SNMP devices No Communication Manager and other SNMP devices ASA No Voice Mail Servers (e.g. Intuity Audix) ASA No Voice Mail Servers (e.g. Intuity Audix) ASA/VAM No Customer Server Transport Protocol Direction Description 161 No UDP SNMP Bi SNMP Access for Mgmt 162 No UDP SNMP In SNMP Traps 23 No TCP telnet Out Telnet access to elements 22 No TCP SSH Out SSH access to elements 25 No TCP SMTP Out server access VAM No TN2401AP Boards and Media Gateways VAM No TN2401AP Boards 20, 21 No TCP ftp Out For file transfer of announcements to Media Gateways and TN2501AP boards 22 No TCP SFTP Out For secure file transfer of announcements to TN2501AP boards Integrated White Paper 22 of 26

23 Source Source Source VAM No Media Gateways (G250/G350) Transport Protocol Direction Description 161 No UDP SNMP Out For sending SNMP commands to retrieve announcement files Console, ASA, VAM Console, ASA, VAM No Communication Manager No Communication Manager 5022 No TCP SSH Out SAT Service ports on Voice Systems depends on voice system SAT service administration for port number Note: The value shown is for SAT access to the Linux-based Media Servers 5023 No TCP telnet Out SAT Service ports on Voice Systems depends on voice system SAT service administration for port number Note: The value shown is for SAT access to the Linux-based Media Servers ASA No Modular Messaging (non-secure) 389 No TCP LDAP Out LDAP connection to Modular Messaging for administration of subscribers ASA No Modular Messaging (secure) 636 No TCP LDAP over SSL Out Secure LDAP connection to Modular Messaging for administration of subscribers Integrated White Paper 23 of 26

24 Source Source Source Transport Protocol Direction Description HPOV Client No FPM Server 2447 ovwdb No TCP OV-API Out NMSI: HP OpenView Solaris ovwdb service daemon HPOV Client No FPM Server No TCP OV-API Out NMSI: HP OpenView GUI Map API Access (port= gui display number) HPOV Client No Master NMSI on the IMD Server 80 No TCP HTTP Out NMSI to send commands to Master NMSI server residing on the IMD Server Installation Integrated White Paper 24 of 26

25 4. Conclusion With the information in this white paper, the customer has been provided with the relevant information about the Integrated Windows-based applications. This information will allow the customer to make an assessment of the necessary protocols and services needed to run on their Windows server. 5. Additional References 1. Avaya Integrated Release 3.1 Standard Installation and Upgrade, , , Issue 2, Feb. 2006, 2. Avaya Integrated Release 3.1 Administration Tools Installation and Upgrade, , , Issue 2, Feb. 2006, 3. Avaya Integrated 3.1 Enterprise Configuration, , Issue 2, Feb. 2006, 4. Avaya Integrated Release 3.1 Enterprise Installation and Upgrade, , , Issue 2, Feb. 2006, 5. Integrated Release 3.1 Console User Guide, , Issue 4, Feb. 2006, 6. Avaya Integrated 3.1 VoIP Monitoring Installation and Upgrade, , , Issue 2, Feb. 2006, 7. Avaya VoIP Monitoring Manager Reference, , Issue 2, Feb. 2006, Integrated White Paper 25 of 26

26 Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in this White Paper is subject to change without notice. The technical data provided in this White Paper are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in this White Paper. Integrated White Paper 26 of 26