How to troubleshoot a client connection to AIA with an ABL program.

How to troubleshoot a client connection to AIA with an ABL program.
Troubleshooting where the connection to a deployed application using an AIA adapter fails
Client Connection fails after AIA has been deployed on Tomcat's default port 8080 
Client Connection fails after AIA has been deployed using the AppServer broker (asbroker1)

To resolve AIA Adapter connection issues

Four basic tests to a state-free AppServer are described in Article:

•  Troubleshooting an AIA using ABL test programs.  

This Article expands on troubleshooting AIA connection problems with further connection examples to used to test the different components required.

Additional logging can be enabled with: AiaDefault; AiaMgmt; AiaProp; AiaRqst; AiaUbroker described in Article:

•  What are the possible values for the -logentrytypes startup parameter in OpenEdge

Setup ABL programs for AIA connection tests

This test uses two sample programs and a .pf file with the required connection parameters to the different components. When the connect succeeds, it returns the host name where the AppServer is running on the client . 

Download the attached AIA_tests.zip file.

1.  Compile Apps_prog.p (with no database connection) and place the r-code file on the same host as the AppServer.

2.  Compile Apps_cli.p (with no database connection) and place the r-code file at the client side of the test, first for localhost and thereafter specific-host remote connections to the AppServer.

3.  Place file Apps_cli.pf at the client side.

This example .pf file contains some examples of the required servhdl:CONNECT parameters for each test:

ASSIGN ret = servhdl:CONNECT("-pf Apps_cli.pf").

In these localhost connect examples, the following need to me modified for the environment under test:

• To test a direct connection to AppServer broker (asbroker1) which runs on portnumber 3090
• To test the connection using the NameServer (NS1) which runs on portnumber 5162

Edit the .pf by adding further connect examples below and modified for your test environment as required:

• localhost with your hostname or IP
• /localhost:8080 with your hostname or IP and JSE port

For each test connect:

• Uncomment one of the connections strings by removing the # character in the first column 
• Leave just one line uncommented and run the connection test using the command: pro -p Apps_cli.p

Troubleshooting and AIA adapter using ABL test programs.

First test localhost connections, then change parameters accordingly for remote connections and finally for the production environment in the Apps_cli.pf

To test a client  localhost State-Aware or State Reset Appserver connection through the NameServer:
To try the AIA using a State-Aware or State Reset Appserver:  
To try the AIA using a State-Aware or State RESET direct connection to the Appserver:
To test a client localhost stateless or session-free Appserver connection through the NameServer
To try the AIA using the session-free Appserver:
To test a client localhost stateless or session-free direct Appserver connection
To try the AIA using a Session-Free direct connection to the Appserver:

Progress Article:

 A deployed OpenEdge Web Service always tries to connect to the AppServer through localhost instead of the remote AppServer host