A personal firewall, or intrusion detection/prevention software (IPS or IDPS), can cause
Unwired Platform components to malfunction or not function
at all. Unwired Platform uses regular IP communication between components on
the primary network interface of a computer,
even when all components are installed on the same host.
If the local network interface is secured by intrusion detection/prevention software (IPS or IDPS, for example, McAfee Host Intrusion Prevention software or equivalent), the security software must be configured to allow all network communication between Unwired Platform components.
For a single node installation of all of the Sybase Unwired Platform components, try one of these options to work around the limitations imposed by the host intrusion prevention software and policy settings, without violating any security policy, until the settings of your security software are adjusted to the needs of Unwired Platform to operate correctly.
- Option One: Remove the host machine from the network.
Note: This local-only mode is especially suitable when you use your laptop in a network other than your corporate network, and want to demonstrate a mobile solution using a simulator or emulator with all components running on the same machine.
- Stop the Sybase Unwired Platform services in the correct order. See the Starting and Stopping Unwired Platform Server Services topic in the Release Bulletin.
- Disconnect the host from all networks.
- Restart Sybase Unwired Platform services in the correct order.
- Change the Sybase Control Center URL link to use "localhost" or <yourhostname> as the host name, instead of the original fully qualified host name of the machine that included the domain name (for example: https://localhost:8283/scc, or https://yourhostname:8283/scc). Accept any security warnings to connect to Sybase Control Center.
This ensures that all interconnections between Sybase Unwired Platform components are treated as local traffic and will not be flagged as incoming connections from external sources causing connection failures due to security policy setting.
- Option Two: Connect the host to the corporate network.
Note: The option of connecting to corporate network through VPN is especially suitable when you use your laptop in a network other than your corporate network, and want to demonstrate a mobile solution using your physical devices, and need outgoing connections to a backend Enterprise Information System (EIS) or Relay Server (Sybase Hosted Relay Server or otherwise).
- Stop the Sybase Unwired Platform services in the correct order. See the Starting and Stopping Unwired Platform Server Services topic in the Release Bulletin.
- Reconnect the host to your corporate network directly or through corporate VPN, to ensure that the corporate network security policy applies.
- Restart Sybase Unwired Platform services in the correct order.
- Change the Sybase Control Center URL link to use "localhost" or <yourhostname> as the host name, instead of the original fully qualified host name of the machine that included the domain name (for example: https://localhost:8283/scc, or https://yourhostname:8283/scc). Accept any security warnings to connect to Sybase Control Center.
This ensures that all interconnections among Sybase Unwired Platform components are internal to your corporate network and validated against the corporate network related security policy.