Extended Network Connectivity (ENC) › Restrictions on Using Client Automation Through ENC Gateway

Restrictions on Using Client Automation Through ENC Gateway

There are a number of restrictions on the features in CA Client Automation (Client Automation) when used through an ENC Gateway connection. These restrictions include:

• Wake-on-LAN (WOL) cannot work through the ENC Gateway because the ENC Gateway supports only TCP connections, whereas WOL uses UDP.
• Some features of Instant diagnostics do not work because they rely on non-ENC Gateway-aware components provided with the operating system, for example, FTP.
• Service location cannot work because it uses UDP.
• Reporter cannot work as it accesses the MDB directly.
• Software delivery (SD) jobs through the ENC Gateway may take up to 10 minutes to be triggered. This is because SD will try to use the IP address of the target when it registered, but this will fail because IP addresses are not valid over different networks. The SD scalability server will retry the job every 10 minutes, alternating between the FQN and IP of the target. The FQN will work with the ENC Gateway because it uses the FQN of ENC Gateway-enabled computers to uniquely identify them.
• Some components within Client Automation use SQL Server or Oracle client side components to make direct management database (MDB) connections. These connections are not ENC-enabled, hence, if these connections pass over firewalls, you should use the recommended Microsoft or Oracle method of traversing the firewall.

  The following list provides details of scenarios and DSM components where direct MDB access is made; additionally, the specific client side components used for SQL Server and Oracle are given:

  • Domain manager to and from the enterprise manager

    MDB replication between the domain manager and the enterprise manager uses direct connections and bulk copy.

    Client side components:

    For SQL Server: SQL Native Client and bcp Utility

    For Oracle: OCI API and SQL*Loader

  • Engine to the domain manager and the enterprise manager

    The engine makes direct database connections when communicating with the domain manager and the enterprise manager.

    Client side components:

    For SQL Server: SQL Native Client and bcp Utility

    For Oracle: OCI API and SQL*Loader

  • Reporter to the domain manager or the enterprise manager

    The reporter makes direct database connections to generate reports.

    Client side components:

    For SQL Server: SQL Native Client and bcp Utility

    For Oracle: OCI API and SQL*Loader

  • Web Console to the domain manager or the enterprise manager

    The Web Console component makes a JDBC connection to the database.

    Client side components:

    For SQL Server: JDBC

    For Oracle: JDBC

  • Contents Import/Export Utility

    The Contents Import/Export Utility makes direct database connections when synchronizing DSM data with a remote Oracle or SQL Server MDB.

    Client side components:

    For SQL Server: SQL Native Client and bcp Utility

    For Oracle: OCI API and SQL*Loader