Deleting the logger data from Integrator caused a reset of the logger_id's used.

 

But the loggerids are used in Interchange to check duplicates.

So Integrator started using old loggerids that still existed in Interchange db and the messages were rejected by interchange resulting in a trace message on integrator side like:

"Pluggable server rejected..."

 

The loggerid usage must be in sync between Interchange and Integrator.

 

How to avoid this:

 

After cleaning up Integrator increase the logger id to a value that is greater than the last used loggerid using the logger_raisehighestlogid.x4 tool available in Integrator before resuming message processing.

Or also delete all messages from Interchange.

1) Use the tool logger_raisehighestlogid.x4 located in $CORE_ROOT/4edi/pgm

 

2) Stop the Trading Engine node (Integrator Tasks will stop)

 

3) Use the Copilot to start only logger tasks  (from task monitor)

B2Bi Logger 1

B2Bi Logger 2

 

4) Go to %CORE_ROOT% and execute profile.bat

 

5) Go to %CORE_ROOT%/4edi/pgm

Execute : 

r4edi porter_list.x4 -LP -a %CORE_LOCAL%/config/passwd -s %CORE_PORTER_PORT%

 

Example :

C:\Axway_B2Bi150\Synchrony\Integrator\4edi\pgm>r4edi porter_list.x4 -LP -a %CORE_LOCAL%/config/passwd -s %CORE_PORTER_PORT%

LOGICAL NAME    PORT

logger_5300     Integratorpool1

logger_5301     Integratorpool2

 

 

6) Execute : r4edi logger_raisehighestlogid.x4 -s <logger_port> <Number_to_raise>

 

Example: 

C:\Axway_B2Bi150\Synchrony\Integrator\4edi\pgm>r4edi logger_raisehighestlogid.x4 -s Integratorpool2 0000000000100000

In the above example logger_5301 is "Integratorpool2"

 

7) Start the Trading Engine node (Integrator Tasks will start)

 

8) Message should appear in Message Log : "Log ids have been skipped"