Table of Contents

Search

  1. Preface
  2. Getting Started with Informatica Cloud Data Integration
  3. System requirements
  4. Runtime environment configuration
  5. Connection configuration
  6. Project setup
  7. Enabling source control
  8. Editing your user profile
  9. User settings
  10. Inviting users to join your organization
  11. Primary cloud data warehouse setup
  12. Switching to a different organization

Getting Started

Getting Started

Configuring the proxy settings in Linux

Configuring the proxy settings in Linux

If your organization uses an outgoing proxy server to connect to the internet, the Secure Agent connects to
Informatica Intelligent Cloud Services
through the proxy server.
The Secure Agent installer configures default proxy server settings for the Secure Agent based on settings configured in the browser. The proxy settings are stored in the proxy configuration file,
proxy.ini
, in the following directory:
<Secure Agent installation directory>/apps/agentcore/conf
The following code shows the default contents of the proxy configuration file:
InfaAgent.ProxyPassword=ZU8KjIzgtVrVmfRMUPzPMw\=\= InfaAgent.ProxyNtDomain= InfaAgent.ProxyHost=foo.bar.com InfaAgent.ProxyPasswordEncrypted=true InfaAgent.NonProxyHost=localhost|127.*|[\:\:1] InfaAgent.ProxyUser= InfaAgent.ProxyPort=12345 InfaAgent.AuthenticationOrder=
To update proxy hosts and ports, as well as the username and password to connect to the proxy server, use the command line. The command line validates the values that you enter. For more information, see Updating proxy settings through the command line.
To update other properties, edit the proxy configuration file directly. When you edit the proxy configuration file, ensure that you use the correct formats to avoid errors. For more information, see Updating proxy settings in the proxy configuration file.
To allow the Secure Agent to connect to data sources and targets, configure proxy settings through JVM Options in addition to configuring the proxy configuration file. For more information, see the help for the appropriate connector.
Some use cases require the Secure Agent to bypass the proxy server and communicate directly with the instance metadata service (IMDS), which stores temporary security credentials. For example, bypassing the proxy server is required if you use an Azure managed identity to access sources and targets in a mapping in advanced mode and if you enable the
Use EC2 Role to Assume Role
property in an Amazon S3 V2 connection. To allow the agent to communicate directly with the IMDS, edit the proxy configuration file and set the IP address of the IMDS, 169.254.169.254, in the value for the property
InfaAgent.NonProxyHost
.
Contact your network administrator for the correct proxy settings.

0 COMMENTS

We’d like to hear from you!