Secure Agent
This section describes changes to the Secure Agent for the Spring 2017 release.
Independent Services for the Secure Agent
Effective in the Spring 2017 release, the Secure Agent can run multiple services independently. You can configure each service independently from other services.
For example, the Data Integration Server runs as an independent service to run all data integration jobs. The Process Server runs as an independent service to run application integration and process orchestration.
Each service has a unique set of configuration properties, such as Tomcat and Tomcat JRE settings.
The ability to run services independently provides the following benefits:
- •The Secure Agent does not restart when you add a connector or package.
- •The Secure Agent does not restart during Informatica Cloud upgrades.
- •No service is impacted when another service restarts. For example, a long standing process continues to run even if the Data Integration Server service is restarted.
Reduced Downtime During Upgrades
Effective in the Spring 2017 release, the upgrade process is optimized to significantly reduce Secure Agent downtime. This functionality addresses the problem of Secure Agent availability during upgrades for customers who cannot afford downtime for data integration jobs or who prefer that the upgrade process be transparent.
The upgrade process installs a new version of the Secure Agent, updates to connector packages, and configuration changes for the Data Integration Server. To minimize downtime, the old agent remains available and continues to run data integration jobs during the upgrade. The new version of the Secure Agent runs jobs that start after the upgrade process completes.
Previously, the Secure Agent was not available to run jobs during the entire upgrade process.
Secure Agent Configuration Properties
Effective in the Spring 2017 release, the Secure Agent can run multiple services. You set the configuration properties separately for each service. Because of this change, some properties associated with previous versions of the Secure Agent are replaced or removed, and other properties are added for the Data Integration Server service.
Replaced Configuration Properties
The following configuration properties are obsolete but are replaced with alternate configuration properties:
- Tomcat configuration properties
The following Tomcat configuration properties are replaced with alternate Tomcat properties for the Data Integration Server:
Obsolete Property | Replacement Property | Description |
|---|
TunnelTimeoutPeriod | NetworkTimeoutPeriod | Controls the length of time, in seconds, that the Secure Agent tries to reestablish communication with Informatica Cloud after a network interruption. Default is 300 seconds. |
TunnelRetryInterval | NetworkRetryInterval | Determines the frequency with which the Secure Agent tries to contact Informatica Cloud within the specified timeout period. Default is five seconds. |
If you changed the value of a Tomcat configuration property that has been replaced, the changes are preserved after the upgrade. For example, if you changed TunnelTimeoutPeriod from 300 to 600 seconds, the NetworkTimeoutPeriod is set to 600 seconds. You do not need to update the replacement properties after the upgrade.
- Tomcat Log4J properties
If you ran a Secure Agent earlier than version 30.0, some Tomcat Log4J configuration properties are replaced.
The following Tomcat Log4J configuration properties are replaced with alternate Tomcat Log4J properties for the Data Integration Server:
Obsolete Property | Replacement Property |
|---|
log4j.rootLogger | log4j_rootLogger |
log4j.logger.org.apache | log4j_logger_org_apache |
log4j.logger.org.springframework | log4j_logger_org_springframework |
log4j.appender.tomcatLog | log4j_appender_tomcatLog |
log4j.logger.com.informatica.saas.tunnel. TunnelClientHttpCommonsImpl | log4j_logger_com_informatica_saas_tunnel_ TunnelClientHttpCommonsImpl |
log4j.appender.tomcatLog.layout. ConversionPattern | log4j_appender_tomcatLog_layout_ ConversionPattern |
log4j.logger.httpclient.wire | log4j_logger_httpclient_wire |
log4j.appender.tomcatLog.File | log4j_appender_tomcatLog_File |
log4j.logger.org.apache.commons. httpclient.auth.AuthChallengeProcessor | log4j_logger_org_apache_commons_ httpclient_auth_AuthChallengeProcessor |
log4j.logger.org.apache.commons. httpclient | log4j_logger_org_apache_commons _httpclient |
log4j.logger.org.hibernate | log4j_logger_org_hibernate |
org.apache.axis.utils.JavaUtils | org_apache_axis_utils_JavaUtils |
log4j.logger.net.sf | log4j_logger_net_sf |
log4j.logger.com.informatica.saas | log4j_logger_com_informatica_saas |
log4j.appender.tomcatLog.layout | log4j_appender_tomcatLog_layout |
log4j.logger.com.informatica.saas.tunnel. TunnelClientImpl | log4j_logger_com_informatica_saas_tunnel_ TunnelClientImpl |
log4j.appender.tomcatLog.MaxFileSize | log4j_appender_tomcatLog_MaxFileSize |
log4j.appender.tomcatLog. MaxBackupIndex | log4j_appender_tomcatLog_ MaxBackupIndex |
If you changed the value of a Tomcat Log4J configuration property that has been replaced, the changes are preserved after the upgrade. For example, if you changed log4j.appender.tomcatLog.MaxFileSize from '10MB' to '20MB,' the log4j_appender_tomcatLog_MaxFileSize is set to '20MB.' You do not need to update the replacement properties after the upgrade.
Removed Configuration Properties
If you ran a Secure Agent earlier than version 30.0, some configuration properties are removed.
The following configuration properties are obsolete and are removed from the Edit Secure Agent Page:
- •All Agent Core properties
- •All Agent Manager properties
- •DTM $PMRootDir, JVMLibPath, and MappingImportLogDir properties
- •All Agent Core JRE properties
- •All Agent Core Log4J properties
- •Tomcat Log4J log4j.logger.com.informatica.ics.adapters.relational.writeback.WriteBack property
- •All Agent Manager Log4J properties
These properties are no longer needed. You do not need to configure alternate properties for any configuration property that was removed.
New Configuration Properties
New configuration properties are added for the Data Integration Server. Do not change the property values unless Informatica Global Customer Supports instructs you to do so.
Secure Agent Proxy File
Effective in the Spring 2017 release, the proxy.ini file is moved to a different directory.
The proxy.ini file is preserved after the upgrade and is copied to the following directory:
<Secure Agent installation directory>/apps/agentcore/conf
For Secure Agents earlier than version 30.0, the proxy.ini file was in the following directory:
<Secure Agent installation directory>/main
User-Defined Parameter Files
Effective in the Spring 2017 release, the directory where you store user-defined parameter files for integration templates and Mapping Configuration tasks is changed.
User-defined parameter files are preserved after the upgrade and are copied to the following directory:
<Secure Agent installation directory>/apps/Data_Integration_Server/data/userparameters
For Secure Agents earlier than version 30.0, user-defined parameter files were stored in the following directory:
<Secure Agent installation directory>/main/rdtmDir/userparameters
PowerCenter Source and Target Files
Effective in the Spring 2017 release, the directory where you store PowerCenter source and target files when the workflow uses the $PMSourceFileDir or $PMTargetFileDir variable is changed.
PowerCenter source and target files are preserved after the upgrade and are copied to the following directory:
<Secure Agent installation directory>/apps/Data_Integration_Server/data
For Secure Agents earlier than version 30.0, PowerCenter source and target files were stored in the following directory:
<Secure Agent installation directory>/main/rdtmDir
Secure Agent Directory Changes
Effective in the Spring 2017 release, some Secure Agent directories are changed.
The following directories are changed:
- Connection log files directory
Each time a user selects a connection for use in a task, Informatica Cloud creates a connection log named <PluginShortName>_<connection_timestamp>.log. The connection logs are in the following directory:
<Secure Agent installation directory>/apps/Data_Integration_Server/<version>/ICS/main/tomcat/log
For Secure Agents earlier than version 30.0, Informatica Cloud created connection logs in the following directory:
<Secure Agent installation directory>/main/tomcat/log
- Connection properties storage directory
The default directory for the connection properties that you store with a local Secure Agent is the following directory:
<Secure Agent installation directory>/apps/Data_Integration_Server/data
For Secure Agents earlier than version 30.0, the default connection properties storage directory was the following directory:
<Secure Agent installation directory>/main/data
- Console agent manager file directory
The console agent manager files consoleAgentManager.bat and consoleAgentManager.sh are in the following directory:
<Secure Agent installation directory>/apps/agentcore
For Secure Agents earlier than version 30.0, the console agent manager files were in the following directory:
<Secure Agent installation directory>/main/agentcore
- Default data masking rules directory
You can view the default_rules.xml, fields.properties, and salesforce_default_values.properties files in the following directory:
<Secure Agent installation directory>/apps/Data_Integration_Server/$version/ICS/main/dmask
For Secure Agents earlier than version 30.0, the default data masking rules were packaged in the following directory:
<Secure Agent installation directory>/Informatica Cloud Secure Agent/main/dmask
- Default flat file target directory for PowerCenter tasks
If you create a PowerCenter task with an FTP/SFTP target connection and the IS_STAGED option is enabled for the underlying PowerCenter session, Informatica Cloud writes the flat file to the remote machine and the following local directory:
<Secure Agent installation directory>/apps/Data_Integration_Server/data
For Secure Agents earlier than version 30.0, Informatica Cloud wrote the flat file to the remote machine and the following local directory:
<Secure Agent installation directory>/main/rdtmDir
- Dictionary file directory for the Data Masking task
When you install or upgrade the Secure Agent in a runtime environment, the Data Masking task downloads and saves the dictionary files to the following directory:
<Secure Agent installation directory>/apps/Data_Integration_Server/data
For Secure Agents earlier than version 30.0, the dictionary file directory was the following directory:
<Secure Agent installation directory>/main/rdtmDir
- Error rows file directory
Informatica Cloud generates target error rows files in the following directory:
<Secure Agent installation directory>/apps/Data_Integration_Server/data/error
For Secure Agents earlier than version 30.0, Informatica Cloud generated target error rows files in the following directory:
<Secure Agent installation directory>/main/rdtmDir/error
- Secure Agent process directory on Linux
To start or stop the Secure Agent on Linux, run the infaagent startup or infaagent shutdown commands from the following directory:
<Secure Agent installation directory>/apps/agentcore
For Secure Agents earlier than version 30.0, you ran these commands from the directory where you installed the Secure Agent.
- Session log file directory
Informatica Cloud generates session logs in the following directory:
<Secure Agent installation directory>/apps/Data_Integration_Server/logs
For Secure Agents earlier than version 30.0, Informatica Cloud generated session logs in the following directory:
<Secure Agent installation directory>/main/rdtmDir/logs
- Staging directory for the Data Masking task
You can run the startup script for the staging database manually from the following directory:
<Secure Agent installation directory>/apps/Data_Integration_Server/$version/ICS/main/tomcat/cmask
For Secure Agents earlier than version 30.0, the Data Masking task used the following directory:
<Secure Agent installation directory>/Informatica Cloud Secure Agent/main/database