|
|
| Product | |
| Support | |
| Everything Else | |
| Helix PORT Resource Editing | |
| About Resource Editing |
This page assumes you have the basic knowledge required to edit resources in Helix using Rezilla. See this page for an overview on editing resources with Rezilla. |
| About the PORT/1 Resource |
PORT resource #1 (referred to as ‘PORT/1’ controls the TCP/IP port Helix Client/Server uses for TCP/IP communications. The default port for Helix is 10860, but this number can be changed to avoid conflict with other TCP/IP applications, to enable access to multiple Helix Servers via NAT, or to provide ‘security through obscurity.’ Your network administrator may also require that you use specific ports. Note: A Helix Client can not access a Helix Server using an alternate port unless you either a) edit the Helix Client PORT resource #1 to the same port or b) connect to the Server using the full IP Address:Port syntax (e.g. 192.168.0.100:10865) |
| Editing the PORT/1 Resource |
The PORT/1 resource is a single field, containing a 2 byte decimal value in the range of 0-65535. Simply change this value to the desired port, click Save, and close the editor. (Be sure to save the modified application when quitting Rezilla.) Editing resources is much easier if you have the corresponding templates installed. See the sections on templates on the Rezilla overview page. |
| Step by Step |
Helix applications are created in ‘package’ format, with the resources being found in a file within the package. If you are familiar with package manipulation, you can open the application package, navigate to the resource, and drag/drop it onto Rezilla. For those less technical, here are instructions for changing Helix Server 6.1.x. (The same steps apply to Helix Client.):
|