Custom INI file for IG-FTP agent

[Michael A. Lowry]

The documentation on installing the Integration FTP agent states that the INI file must be named ucxjcitx.ini. 

Is there no way to tell the agent to load an INI file with a different name?

We have eighteen (18) of these FTP agents, and each one has slightly different options defined in the INI file. We would prefer not to have to maintain eighteen different files with identical names.

-------------------------------------------

[Cristian Suciu]

You should be able to rename them and change the names of each agent that the Service Manager needs to start in the uc4.smd and uc4.smc files. 

-------------------------------------------

[Christoph Rekers at Tricise]

Hi @Michael A. Lowry

normally agents look for an INI file that has the same name as themselves (i.e., the agent executable). This obviously no longer applies to the IG_ agents.

With -i, you can specify any other name.


-imy_agent.ini does the trick:



Cheers

Christoph 

------------------------------
--------------------------------------------------------
Automic Consultant and Trainer since 2000
--------------------------------------------------------
now Tricise
------------------------------

[Michael A. Lowry]

I confirmed that the -i option does work as expected. I thought it didn't work for three reasons:

1. For some reason, the -i option is not documented in Integration FTP - Agent Guide.
2. the -i option did not work in earlier versions. This bug was fixed in v21.2.0 and v24.1.0. The defect is DE129818: "FTP integration agent does not start when using a non-default ini file name."
3. Even though I am running a version with the fix, it was still not working because I was running into an also-undocumented 512-character limit for DEFINE statements in Service Manager SMD files. @Eric Lontz documented this (along with several other quirks of the FTP agent) in his forum post entitled Automic IG FTP Agent Deployment Notes.

Thanks to all who replied.

[Eric Lontz]

Michael,

I did find something to alleviate using so much of the character limit with the switches in the smd file.

You can put a file(s) in the agent bin directory which contains the switches used by the command line and reference them with @<filename>.  I have two files, options and encryption.

options contains
--add-opens=java.base/sun.security.ssl=ALL-UNNAMED
--add-opens=java.base/sun.security.util=ALL-UNNAMED

encryption contains
-Djsch.dhgex_min=1024
-Djsch.dhgex_preferred=1024
-Djsch.server_host_key=rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ssh-rsa 
-Djsch.client_pubkey=rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ssh-rsa 
-Djsch.kex=diffie-hellman-group14-sha1,ecdh-sha2-nistp256,diffie-hellman-group-exchange-sha256,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group-exchange-sha1 
-Djsch.cipher=aes128-ctr,aes256-cbc,aes256-ctr

The smd command we are using has been greatly simplified.

DEFINE IGFTPAGENT_1;*JV_PATH @options -jar -Xrs -Xmx2G @encryption ucxjftp.jar;*OWN\..\..\Agents\rapidautomation\IGFTP\bin

 

-------------------------------------------

[Michael A. Lowry]

Great minds think alike, @Eric Lontz. I implemented an almost identical solution yesterday. 😀