Installing Connection Manager Server for UNIX and Linux

Connection Manager server can be installed and used with RF Design Environment (RFDE) and Advanced Design System (ADS). Follow these instructions to install the Connection Manager server and configure the server IO.

Obtaining the Software

The ADS 2008 release does not include installation for Connection Manger Server. To use Connection Manager Server with ADS 2008, install Connection Manger Server from ADS 2006 Update 3 installation media. You could also download the Connection Manger Server shipped with ADS 2006 Update 3 from Agilent EEsof Knowledge Center at:
https://edasupportweb.soco.agilent.com/page/show_add_on?id=300789&ref=browse

You may need to have Agilent EEsof Knowledge Center login to access the above link. Please follow the remaining instruction in this document to install Connection Manager Server.

Before You Begin

To communicate with instruments, you must install the Connection Manager server. Before installing the server, ensure that your PC workstation and your EDA software licensing meet the following requirements.

System Requirements

The server must be installed on a Windows PC connected to the same network as the EDA software network server or local installation.

Note Connection Manager Server cannot be installed on 64-bit machines.

Requirement	Description
Processor	Pentium III 450 MHz or higher
RAM	256 MB
Hard Disk Space	500 MB on system drive
Operating System	Windows XP Professional (Service Pack 1)
Network Configuration	TCP/IP
Supported Media Type	CD-ROM required for program installation.

Caution If you have Toshiba Bluetooth Stack installed on your System then please uninstall it before installing Connection Manager Server. Installing Toshiba Bluetooth Stack and Connection Manager Server on the same system may cause undesirable effects including System Crash. You could uninstall Toshiba Bluetooth Stack using following link on Windows: Start->Control Panel->Add or Remove Programs You could install Windows native Bluetooth drivers to use Bluetooth devices.

Licensing Requirements

Although the Connection Manager client requires a license, Connection Manager server does not require a license regardless of where it is installed.

Note The Connection Manager client is installed during the main software installation. The link_connect_mgr license is required to run the client from a schematic page. Connection Manager client and server installations are not related to the client-server installation of the EDA software.

EDA Software Version Requirements

The Connection Manager client and server software must be from the same or compatible release. If you have been using an older release of Connection Manager, then you install ADS 2008 on a client system, you also must install a compatible release of the server software. Since the Connection Manager server was not updated for ADS 2008, the compatible release for ADS 2008 is 2006 Update 3.

Installation Package Overview

The Connection Manager server installation installs all the software necessary to enable the EDA software-supplied measurements. This includes:

• Run-time versions of the Agilent Test and Measurement Programmer's Toolkit. This includes the most recent version of VISACom available when the Toolkit was released. The latest version is available from the Agilent Developer Network at:
  http://adn.tm.agilent.com
• The Agilent IO Libraries
• ADS Measurement Libraries
• Run-time versions of Microsoft .NET, suitable for running .NET application
• The Connection Manager server

Installation Types

Complete

The Complete installation installs all program features in the default installation directory C:\Program Files\Agilent\Connection Manager Server.

Custom

The Custom installation lets you define the installation directory and choose the optional program features, such as the ADS Measurement Library, Connection Manager documentation, Ptolemy VEE Link Server, and VEE Service Control Panel Application.

Installing the Server

1. Ensure that your PC workstation meets the system requirements.
2. Insert the Connection Manager Server 2006 Update 3 Installation Disc into the workstation CD-ROM drive.
3. When the installation wizard prompts you, choose the type of installation.
4. Follow the command prompts to complete the installation.

For Windows XP Service Pack 2 Systems Only

1. When the system reboots, Connection Manager Server starts and the Windows Security Alert dialog appears.
   
2. In the Windows Security Alert dialog, click Unblock.
   This creates an exception in the Windows Firewall that allows network connections through the firewall to the Connection Manager server.

This completes the installation process. To connect instruments to the server workstation, complete the steps in Configuring the Server IO on the PC.

Configuring the Server IO on the PC

Prior to using Connection Manager for the first time, you must configure the IO on the server workstation.

This section provides instructions for automatically configuring common LAN and GPIB interfaces, and for manually configuring other interfaces such as LAN/GPIB gateways.

To Configure Common LAN or GPIB Interfaces provides simplified instructions to configure a common LAN or GPIB interface.

To manually configure an available interface (for example, the Agilent E5810A LAN/GPIB gateway), see To Manually Configure Other Interfaces.

Additional Resources

For detailed information on IO configuration, refer to the documentation for the IO libraries.

Choose the IO icon in the tool bar, then choose View Documentation.

Also, see "Configuring IO Interfaces" in Agilent IO Libraries Installation and Configuration Guide for Windows, available in PDF format at: http://www.agilent.com/find/iolib.

Note Connection Manager server does not support the use of National Instruments IO connectivity products. The Connection Manager server relies entirely on the Agilent IO libraries to provide instrument connectivity, and cannot offer support for National Instruments IO products.

To Configure Common LAN or GPIB Interfaces

To auto-configure the I/O and connect instruments to the server using a LAN or GPIB interface:

1. In the server's Windows system tray, select IO > Run IO Config.
   This opens the IO Config dialog. The Available Interface Types group box lists the IO types supported by the Agilent IO Libraries. List entries with and asterisk can be automatically configured in step 2.
2. To automatically configure common LAN and GPIB interfaces in the IO Config dialog, select Auto Config.
   Auto-configured interfaces appear in the Configured Interfaces group box, as shown.
   

If you encounter a problem

For GPIB interfaces, ensure that the GPIB interface is installed/connected to the server.

For LAN interfaces, the IO auto-configuration routine creates a TCPIP network tunnel and displays TCPIP lan in the Configured Interfaces group box. The routine creates only one TCPIP interface regardless of the number of LAN cards installed on the server workstation.

Follow the steps in To Connect Instruments to the Server through the LAN to complete the LAN interface configuration.

To Connect Instruments to the Server through the LAN

Unlike GPIB interfaces where instruments communicate directly with the server via an exclusive bus, the Agilent IO libraries do not dynamically discover instruments connected to the server via LAN. You must manually add LAN devices to the server IO.

To add LAN devices:

1. In the IO Config dialog, highlight TCPIP0 in the Configured Interface group box and click Edit.
2. In the LAN Client dialog, click Edit VISA Config.
3. In the TCPIP devices dialog, click Add device.
4. In the Add a TCPIP device dialog Machine Name/IP field, enter the IP address of the instrument you would like to connect to the server and click OK.
   
5. In the TCPIP devices dialog, click OK.
   
6. In the LAN Client dialog, click OK.
7. In the IO Config dialog, click OK.

If you encounter a problem

Ensure the following conditions are met:

• The server is connected to the LAN.
• The instrument is connected to the LAN.
• The instrument line power is switched on.
• The LAN is operational.

To Manually Configure Other Interfaces

This section explains how to manually configure an IO that cannot be auto-configured by the Agilent IO Library. This section explains how to configure a LAN/GPIB gateway, such as the Agilent E5810A.

To manually configure a LAN/GPIB gateway.

1. In the Windows system tray, select IO > Run IO Config.
2. In the Available Interface Types group box, highlight VISA LAN Client Interface (E5810A) and click Configure.
3. In the VISA LAN Client Interface (LAN to GPIB) dialog Local Settings group box, use the scroll box to choose a VISA Interface Name.
4. In the Remote Settings group box, enter the hostname or IP address of the LAN/GPIB gateway.
5. In the Remote Settings group box, enter the SICL interface name assigned to the LAN/GPIB gateway (or other network interface device) and click OK.
   During the process of configuring the LAN/GPIB gateway, you must assign a SICL interface name to the device. You must enter the same SICL interface name in the Remote SICL Interface Name data entry field.
   
6. In the VISA LAN Client Interface (LAN to GPIB) dialog, click OK.

To exit the IO configuration without connecting instruments to the server, in the IO Config dialog click OK. To connect instruments to the server, follow the steps in To Connect Instruments to the Server through the LAN.

If you encounter a problem

Ensure the following conditions are met:

• The server is connected to the LAN.
• The LAN is operational.

Using Connection Manager with Windows XP Service Pack 2

By default, computers using Windows XP Service Pack 2 will not allow access to the Connection Manager server and VEE Service through the firewall.

If you have upgraded from another operating system version to Windows XP Service Pack 2, you must enable connections to the PC hosting the Connection Manager server and/or VEE Service by listing them as exceptions to the firewall.

To enable network connections to Connection Manager server (and VEE Pro, if necessary) through the firewall:

1. In the Windows menu bar, choose Start > Settings > Control Panel.
2. In the Control Panel dialog, click Windows Firewall.
   
3. In the Windows Firewall dialog, ensure that the Don't allow exceptions checkbox is unchecked.
   
4. In the Windows Firewall dialog, click the Exceptions tab.
   
5. In the Exceptions tab, click Add Program.
6. In the Add a Program tab, click Browse.
7. Use the Browse dialog to enter the Connection Manager Server installation directory (by default, <installation drive>\Program Files\Agilent\Connection Manager Server).
8. From the Connection Manager Server installation directory, choose MsmtSrvr.exe and click Open.
   
9. In the Add a Program tab, click OK.
   The Windows Firewall dialog Exceptions tab shows the MsmtSrvr.exe exception.
   
10. If you are using VEE Service, in the Exceptions tab, click Add Program....
11. In the Add a Program tab, click Browse.
12. Use the Browse dialog to enter the VEE Pro installation directory (by default, <installation drive>\Program Files\Agilent\VEE Pro 7.0).
13. From the VEE Pro installation directory, choose veesm.exe and click Open.
14. In the Add a Program tab, click OK.
15. In the Windows Firewall dialog, click the OK.

Connections to the PC hosting the Connection Manager server and/or VEE Service are now enabled as firewall exceptions.

Running the CM Server as a Windows Service

By default, the Connection Manager server runs as a Windows application. If preferred, the server can run as a Windows service.

For instruction on configuring the server to run as a Windows service, see Running the Server as a Windows Service in the Connection Manager documentation.