In addition to customizing the Gateway's homepage, there are a number of advanced features in the Gateway that you can customize, such as changing ports, changing the Java version, and changing the allocated memory size.
About Java Versions
Ignition runs on Java, and Java is always being updated to have better security or include new features. It's important to pay attention to what version of Java is being run on the computer that Ignition is installed on, especially since you can have multiple copies of Java on a computer at the same time. We recommend that you turn Java's "Automatic Updates" off since Java will sometimes remove older versions that Ignition might still be using. This is not as important on client computers since you are starting and stopping the clients much less frequently than the Gateway.
You can update which version of Java the Ignition service is pointed to from a configuration file. See Changing Gateway Java Version for more information.
About Memory Usage
The Ignition Gateway uses memory just like any other program, and the amount of memory Ignition is allowed to use can be set in a configuration file. It is important to know how much Ignition initially asks for because if you don't have enough free memory for that initial amount, the Ignition service won't start. Likewise, you can set the maximum memory that Ignition uses so it doesn't starve other programs. Of course we recommend that Ignition is installed on it's own server to it can maximize it's performance, but often Ignition is installed on a computer that is already running several other important programs. Note: on older 32bit systems (modern computers are all 64 bit these days), you cannot set the memory to be more than about 1.5Gb. If you do, the program will never be allowed to start. Learn more about setting memory at Changing Gateway Memory Allocation.
Ignition uses ports on a computer to give you access to the Gateway Webpage. The default port for any webpage is 80, and all webpages hide 80 from you in the website address. If multiple programs try to use the same port they will fail, and because many computers already use this standardized default port, Ignition defaults to 8088 instead. This means that you will access Ignition's gateway webpage with http://ipaddress:8088. Once Ignition is installed, you can change the port to whatever you like, including to 80. See Changing Gateway Ports.
An Ignition server uses many ports to manage information between itself and other Ignition servers, OPC servers, devices, and other services such as SMTP and ERP servers. The following table describes the default ports an Ignition server may use for communication. Most are configurable and some of these ports may be on a computer other than the one Ignition is installed on (that is, if MySQL is installed on a different computer, the Ignition server will not be using port 3306). This is not a complete list of TCP ports, and there are a few UDP and broadcast ports in the list. Ignition will potentially use other ports if you are connecting to additional services or devices. Setting ports may be possible for some of the following, but will depend on their respective software.
|Default port setting to access the Ignition Gateway. Also the non SSL port for the Gateway Network.|
|8043||Listening||tcp||Yes||Default SSL port setting to access the Ignition Gateway|
|8060||Listening||tcp||Yes||Default SSL port setting for the Gateway Network.|
|2222||Listening||tcp||No||Allen Bradley Drivers (Ethernet/IP I/O DMA)|
|4096||Listening||tcp||Yes||Default port for Ignition OPC-UA server|
|4446||Listening||udp/broadcast||Yes||Default receive port for a multicast messages that makes the gateway discoverable on a local network|
|5060||Listening||tcp/SIP||No||Send Voice Notification to SIP server|
|5500||Listening||tcp||Yes||Default port for OPC browse of external Tags|
|6501||Listening||tcp||No||Server fallback port|
|8000||Listening||tcp/RTP||No||Transfer/com for SIP server|
|8750||Listening||tcp||No||Port used for Redundancy/Network Configuration|
|17342||Listening||tcp||No||Receive Port for SMS with Alarming|
|45900||Listening||tcp||No||Callback port for the mobile module|
|44818||Listening||tcp||No||Allen Bradley Drivers (Ethernet/IP Symbolic/General)|
|135||Outgoing||tcp||No||Default port for DCOM communication (old OPCDA servers)|
|389||Outgoing||tcp||Yes||Default port for Active directory if this is being used|
|465||Outgoing||tcp||No||SMTP protocol used if Alarming is configured|
|502||Outgoing||tcp||Yes||Default Modbus port|
|1433||Outgoing||tcp||Yes||Default MSSQL port used for connection|
|1521||Outgoing||tcp||Yes||Default Oracle port used for connection|
|3050||Outgoing||tcp||Yes||Default Firebirdsql port used for connection|
|3306||Outgoing||tcp||Yes||Default MySQL port used for connection|
|udp/broadcast||Yes||Default send port for a multicast messaged that makes the gateway discoverable on a local network|
|5432||Outgoing||tcp||Yes||Default Postgresql port used for connection|
|17341||Outgoing||tcp||No||Send port for SMS with Alarming|
|50000||Outgoing||tcp||Yes||Default IBM DB2 port used for connection|
|1883||variable||tcp||No||MQTT Unencrypted. Outgoing port if using an external MQTT broker, Listen port on Ignition if using the Distributor module|
|8883||variable||tcp||No||MQTT SSL/TLS. Outgoing port if using an external MQTT broker, Listen port on Ignition if using the Distributor module|