StarQuest Technical Documents
StarPipes for Windows Frequently Asked Questions
Last Update: 12 May 2011
Product: StarPipes for Windows
Version: 4.0 & later
Article ID: SQV00SW001
The following FAQs are designed to answer some of the common questions regarding StarPipes for Windows.
General
Installation
Usage
- How do I remotely manage StarPipes?
- How do I configure StarSQL to use StarPipes?
- How do I view the usage statistics that StarPipes records?
StarPipes is a software product that operates on a Windows system as a service. StarPipes listens on one or more configured ports for incoming requests from DB2 users of software such as StarSQL; the incoming requests can use either TCP/IP or SSL connections. It then transfers the messages to DB2 servers using either TCP/IP, SSL, or SNA-APPC conversations.
When used for SSL communications, StarPipes provides secure communications without the need to update older DRDA clients or DB2 hosts. It also avoids the complex configuration required to set up SSL on some DB2 platforms, as well as offloading the processing required for encryption and decryption to lower cost hardware.
When used as a TCP/IP to SNA gateway, StarPipes eliminates the need for Microsoft Host Integration Client or IBM Communications Server Client on individual workstations.
StarPipes can also be used as a diagnostic aid to capture DRDA traces; it is especially useful for problem determination of applications that run as a Windows service such as StarQuest Data Replicator and SQL Server Linked Servers.
Can I use StarPipes to connect to more than one DB2?
Yes, you can configure StarPipes to access multiple DB2 systems. StarPipes routes requests based on the RDB (Database Server) name. For each DB2 system you wish to connect to, you must create a routing entry, using either TCP/IP, SSL, or APPC connectivity; the latter requires Microsoft Host Integration Server or IBM Communications Server.
You need to be an administrator on the machine where you wish to install the StarPipes service. Run the setup.exe installation program to install StarPipes. You can choose to install both the StarPipes service and the Management Console, or just the Management Console if you only want to use StarPipes to remotely manage another computer.
StarPipes may be installed on the Host Integration Server (or Communications Server) or a client of Host Integration Server (or Communications Server).
Note: Reboot your Windows server or workstation after installing Microsoft Host Integration Server, including service packs.
Do I need a validation code (license)?
Yes - the StarPipes service requires an "SP" license to accept requests from clients. In addition, it can optionally manage "SQ" licenses on behalf of StarSQL and StarSQL for Java clients, eliminating the need to configure licensing on individual workstations.
How do I remotely manage StarPipes?
To use the Management Console, you need administrator level privileges on the machine where the StarPipes service is installed. On the remote machine, install only the StarPipes management tools. In the StarPipes Management Console, define a service on the remote machine where the StarPipes service is installed.
How do I configure StarSQL to use StarPipes?
Configure your StarSQL data source as usual for your DB2. Make sure that the Database Server Name of your StarSQL data source matches an entry in the StarPipes SNA or TCP/IP Routing entries.
In the StarSQL data source, on the "Network" page , select "TCP/IP" and for Host Name, specify the name or IP address of the Windows computer where the StarPipes service is installed. For the port, specify the port on which StarPipes listens for requests (the default is 446).
How do I view the usage statistics that StarPipes records?
In the StarPipes Configuration Logging properties, enable "Accounting Statistics". StarPipes will log usage information in two comma delimited text files which can be imported into a spreadsheet for sorting and analysis. Information recorded includes the IP address of the client requester, the DB2 user name, the length of time the connection was open and the average turnaround time of StarPipes. For more information on logging, refer to the StarPipes help.