XFB Connector in Integrator

Published in November 10th, 2008

So we have issues lately where files just pile up in integrator, and we have to restart to get them to all go through. Meanwhile, we are receiving anywhere from hundreds to thousands of trace entries a day that say the following -

procengine(procengine(ta_xfb)) XFB.CancelTransfer: GIK error

We’ve been told that this was related to the XFB connector, and that it is a known weak-spot, but I’m really hoping to do something about it. Has anybody else battled issues with the XFB connector failing on you? An example of one of our flows would be an XFB Receive from Gateway, A Decrypt and rename, and then an XFB Send method back to gateway. What frequently happens though is that the XFB receive method gets the file, and then nothing happens with it.

Any thoughts?

T.Lloyd

Copy and Paste of objects in Composer

Published in November 10th, 2008

Posted by Tony in Axway Forum Syndicate

No Comments

Howdy ya’ll,

I’m curious as to whether or not the issues I have with copying and pasting objects is universal for users. It seems as though copying a copy of an object in a dashboard just wrecks you. I’d assume this is something universal related to the java interface, but I figured I’d ask before we actually mentioned it to Axway.

Anybody?

Hasta,

Tony

Removing Carriage Return Line Feeds in Integrator

Published in November 10th, 2008

Posted by Tony in How-To, Synchrony Gateway, Synchrony Integrator

No Comments

So we recently encountered an issue where when we use Gateway 6.9.1 with Integrator 2.1.1, we experience an issue with filenames that come in from Gateway with a CRLF that we then want to route internally with integrator, Integrator chokes on the FTP send. Somebody suggested the following as a workaround, which I haven’t had [...]

Can Integrator remove trailing CRLF?

Published in November 7th, 2008

Posted by Tony in Axway Forum Syndicate

No Comments

Hi there, using XFB to route a file to XIB that we pull using a Transfer model/decision rule that parses the names from a DIR listing and then pulls them, we encounter an issue with the files being pulled with a CRLF appended to the filename. It routes to integrator and processes without difficulty, but when integrator attempts to route it to an internal FTP site, it chokes because of the CRLF at the end.

Does anybody know a way to trim this?

Thanks,
Tony

Keep up-to-date using RSS feeds

Published in November 7th, 2008

Posted by Tony in Axway Forum Syndicate

No Comments

Hello Axway Community !

Have you noticed that RSS feeds are available to keep you up-to-date on your favorite forums ?

The RSS feeds are not available for all forums at that time, but do not worry, each time the activity increases on a forum, a dedicated RSS feed will be added.

Do not hesitate to post any RSS feed request in the “Feedback & Suggestions” forum.

Best regards,

Your Community Admin

B2Bi Express

Published in November 7th, 2008

Posted by Tony in Axway Forum Syndicate

No Comments

Hello

Can you please add the B2Bi Express product? I don’t see it listed here.

Thanks!

Multiple Next Activities in custom MBC

Published in November 6th, 2008

Posted by Tony in Axway Forum Syndicate

No Comments

Just to kick off some tips & hints sharing between XIB/Integrator users/developers:

When using the code-examples Axway supplies (in the $CORE_ROOT/example/hierch directory) you’ll notice
that it’s possible to configure multiple next-activities in the GUI of the custom MBC, but only the FIRST next-activity
get triggered. Here’s why:

Look in the code (for example the “procmbc_examplecreator.s4″) for the following line:

CODE

$Config.$NextActivityId = $StageConfiguration.$NextActivityIds[1];

As you can see $Config.$NextActivityId gets filled by the first ([1]) next-activity of the Stageconfiguration.

A bit further the variable $Config.$NextActivityId is used in the following code:

CODE

/*
* Set message destination
*/
MBC_HIERCHMSGENV.SetActivityBranch $SessionId
MessageId $newMessageId
ActivityBranchId $Config.$NextActivityId;

To make it possible to actually use multiple next-activities, do the following:
(i’m ignoring het variable $Config.$NextActivityId completely here)

CODE

/*
* Copy input message for each new activity configured
*/
FOR $i = 1 to ARRAYSIZE($StageConfiguration.$NextActivityIds) # The magic starts here
{
$newMessageId = MBC_HIERCHMSGENV.CreateMessage($SessionId, $MessageId);

   /*
   * Attach the data to the new message
   */
   MBC_HIERCHMSGENV.AttachData $SessionId MessageId $newMessageId Data $newDataIOHandle;

   /*
   * Pass all attributes to new message
   */
   FOR $i_Attribute = 1 TO ARRAYSIZE($AttributeNames)
   {
      $AttributeValue = MBC_HIERCHMSGENV.GetAttribute($SessionId, $MessageId, $AttributeNames[$i_Attribute]);

      MBC_HIERCHMSGENV.SetAttribute $SessionId
         MessageId $newMessageId
         Name $AttributeNames[$i_Attribute]
         Value $AttributeValue;
   }

   /*
   * Set message destination
   */
   MBC_HIERCHMSGENV.SetActivityBranch $SessionId
      MessageId $newMessageId
      ActivityBranchId $StageConfiguration.$NextActivityIds[$i]; # The magic happens here

   /*
   * Log new message
   */
   LogSuccess $SessionId
      LoggerId   MBC_HIERCHMSGENV.GetLoggerId($SessionId, $newMessageId)
      ActivityId MBC_HIERCHMSGENV.GetActivityBranch($SessionId, $MessageId)
      ParentId   MBC_HIERCHMSGENV.GetLoggerId($SessionId, $MessageId)
      Nbr        $NbrCharacters
      Replace    $Config.$Replace;

} # FOR ActivityIds

/*
* Done!
*/
MBC_HIERCHMSGENV.ProcessMessageDone $SessionId MessageId $MessageId;

I hope you get the point!

Good luck programming your multiple-next-activities-custom-MBC’s !

P.S. It would be nice if Axway incorporates this small change in the examples they supply…

Problem starting up XWS (2.2.x) with embedded XMS

Published in November 6th, 2008

Posted by Tony in Axway Forum Syndicate

No Comments

XWS has been installed on LINUX with embedded messaging. Upons starting up the xws server it throws below error

elcomxws@ebdmz11</data/elcomxws/xws/Synchrony_V4.0># startxws

Starting the Synchrony WebServices server

2008-11-06 07:36:46,671 INFO l.127 XwsServer.serverStart - Starting Synchrony WebServices server

2008-11-06 07:36:46,678 DEBUG l.616 XwsServer.runXmsAdminCommand - Operating Synchrony Messaging System at runtime path << /data/elcomxws/xws/WebServices/products/xms/runtime >>

2008-11-06 07:36:46,712 DEBUG l.672 XwsServer.runXmsAdminCommand - Created temporary Synchrony Messaging System script << /data/elcomxws/xws/Synchrony_V4.0/./temp_script19605.cmd >>

2008-11-06 07:36:46,714 DEBUG l.682 XwsServer.runXmsAdminCommand - # XMS user environment profile script - Version 5.1.2

2008-11-06 07:36:46,714 DEBUG l.682 XwsServer.runXmsAdminCommand - # Date : Tue Nov 4 13:05:22 2008

2008-11-06 07:36:46,714 DEBUG l.682 XwsServer.runXmsAdminCommand -

2008-11-06 07:36:46,715 DEBUG l.682 XwsServer.runXmsAdminCommand -

2008-11-06 07:36:46,715 DEBUG l.682 XwsServer.runXmsAdminCommand - # XMS users have to load these environment variables.

2008-11-06 07:36:46,716 DEBUG l.682 XwsServer.runXmsAdminCommand - # Insert the following line:

2008-11-06 07:36:46,716 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,716 DEBUG l.682 XwsServer.runXmsAdminCommand - # . this_file

2008-11-06 07:36:46,717 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,717 DEBUG l.682 XwsServer.runXmsAdminCommand - # in their user profile.

2008-11-06 07:36:46,718 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,718 DEBUG l.682 XwsServer.runXmsAdminCommand -

2008-11-06 07:36:46,719 DEBUG l.682 XwsServer.runXmsAdminCommand -

2008-11-06 07:36:46,719 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,719 DEBUG l.682 XwsServer.runXmsAdminCommand - # Machine type

2008-11-06 07:36:46,720 DEBUG l.682 XwsServer.runXmsAdminCommand - # ————

2008-11-06 07:36:46,720 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,721 DEBUG l.682 XwsServer.runXmsAdminCommand - x_machine=”linux”

2008-11-06 07:36:46,721 DEBUG l.682 XwsServer.runXmsAdminCommand - export x_machine

2008-11-06 07:36:46,721 DEBUG l.682 XwsServer.runXmsAdminCommand -

2008-11-06 07:36:46,722 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,722 DEBUG l.682 XwsServer.runXmsAdminCommand - # Home directory of XMS

2008-11-06 07:36:46,723 DEBUG l.682 XwsServer.runXmsAdminCommand - # ———————

2008-11-06 07:36:46,724 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,724 DEBUG l.682 XwsServer.runXmsAdminCommand - x_home_dir=”/data/elcomxws/xws/WebServices/products/xms”

2008-11-06 07:36:46,725 DEBUG l.682 XwsServer.runXmsAdminCommand - export x_home_dir

2008-11-06 07:36:46,725 DEBUG l.682 XwsServer.runXmsAdminCommand -

2008-11-06 07:36:46,726 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,726 DEBUG l.682 XwsServer.runXmsAdminCommand - # RunTime directory of XMS

2008-11-06 07:36:46,726 DEBUG l.682 XwsServer.runXmsAdminCommand - # ————————

2008-11-06 07:36:46,727 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,727 DEBUG l.682 XwsServer.runXmsAdminCommand - x_runtime=”/data/elcomxws/xws/WebServices/products/xms/runtime”

2008-11-06 07:36:46,728 DEBUG l.682 XwsServer.runXmsAdminCommand - export x_runtime

2008-11-06 07:36:46,728 DEBUG l.682 XwsServer.runXmsAdminCommand -

2008-11-06 07:36:46,729 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,729 DEBUG l.682 XwsServer.runXmsAdminCommand - # Backup directory of XMS

2008-11-06 07:36:46,729 DEBUG l.682 XwsServer.runXmsAdminCommand - # ———————–

2008-11-06 07:36:46,730 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,731 DEBUG l.682 XwsServer.runXmsAdminCommand - x_backup_path=”/data/elcomxws/xws/WebServices/products/xms/runtime/backup”

2008-11-06 07:36:46,731 DEBUG l.682 XwsServer.runXmsAdminCommand - export x_backup_path

2008-11-06 07:36:46,732 DEBUG l.682 XwsServer.runXmsAdminCommand -

2008-11-06 07:36:46,732 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,733 DEBUG l.682 XwsServer.runXmsAdminCommand - # LOCAL qmgr name

2008-11-06 07:36:46,733 DEBUG l.682 XwsServer.runXmsAdminCommand - # —————

2008-11-06 07:36:46,733 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,734 DEBUG l.682 XwsServer.runXmsAdminCommand - x_local_qmgr=”XWS”

2008-11-06 07:36:46,734 DEBUG l.682 XwsServer.runXmsAdminCommand - export x_local_qmgr

2008-11-06 07:36:46,735 DEBUG l.682 XwsServer.runXmsAdminCommand -

2008-11-06 07:36:46,735 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,735 DEBUG l.682 XwsServer.runXmsAdminCommand - # Frontend port

2008-11-06 07:36:46,736 DEBUG l.682 XwsServer.runXmsAdminCommand - # —————

2008-11-06 07:36:46,736 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,738 DEBUG l.682 XwsServer.runXmsAdminCommand - x_frontend_port=”4570″

2008-11-06 07:36:46,738 DEBUG l.682 XwsServer.runXmsAdminCommand - export x_frontend_port

2008-11-06 07:36:46,739 DEBUG l.682 XwsServer.runXmsAdminCommand -

2008-11-06 07:36:46,739 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,740 DEBUG l.682 XwsServer.runXmsAdminCommand - # Name of configuration file

2008-11-06 07:36:46,740 DEBUG l.682 XwsServer.runXmsAdminCommand - # —————————

2008-11-06 07:36:46,741 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,741 DEBUG l.682 XwsServer.runXmsAdminCommand - x_config_file=”$x_runtime/etc/conffile”

2008-11-06 07:36:46,742 DEBUG l.682 XwsServer.runXmsAdminCommand - export x_config_file

2008-11-06 07:36:46,742 DEBUG l.682 XwsServer.runXmsAdminCommand -

2008-11-06 07:36:46,743 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,745 DEBUG l.682 XwsServer.runXmsAdminCommand - # messages, task trace, database and arc directory

2008-11-06 07:36:46,745 DEBUG l.682 XwsServer.runXmsAdminCommand - # ————————————————

2008-11-06 07:36:46,747 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,748 DEBUG l.682 XwsServer.runXmsAdminCommand - x_nltpath=”$x_home_dir/nlt/english”

2008-11-06 07:36:46,749 DEBUG l.682 XwsServer.runXmsAdminCommand - export x_nltpath

2008-11-06 07:36:46,749 DEBUG l.682 XwsServer.runXmsAdminCommand - x_trace_pathname=”$x_runtime/tmp/TRACE”

2008-11-06 07:36:46,751 DEBUG l.682 XwsServer.runXmsAdminCommand - export x_trace_pathname

2008-11-06 07:36:46,751 DEBUG l.682 XwsServer.runXmsAdminCommand - x_xmsadm_archive=1

2008-11-06 07:36:46,752 DEBUG l.682 XwsServer.runXmsAdminCommand - export x_xmsadm_archive

2008-11-06 07:36:46,752 DEBUG l.682 XwsServer.runXmsAdminCommand - x_database=”$x_runtime/data”

2008-11-06 07:36:46,752 DEBUG l.682 XwsServer.runXmsAdminCommand - export x_database

2008-11-06 07:36:46,753 DEBUG l.682 XwsServer.runXmsAdminCommand - x_arc_path=”$x_runtime/arc”

2008-11-06 07:36:46,753 DEBUG l.682 XwsServer.runXmsAdminCommand - export x_arc_path

2008-11-06 07:36:46,753 DEBUG l.682 XwsServer.runXmsAdminCommand -

2008-11-06 07:36:46,753 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,754 DEBUG l.682 XwsServer.runXmsAdminCommand - # PATH for the shell to find XMS commands

2008-11-06 07:36:46,754 DEBUG l.682 XwsServer.runXmsAdminCommand - # —————————————

2008-11-06 07:36:46,754 DEBUG l.682 XwsServer.runXmsAdminCommand - #

2008-11-06 07:36:46,755 DEBUG l.682 XwsServer.runXmsAdminCommand - PATH=$x_home_dir/bin:$x_runtime/etc:$PATH; export PATH

2008-11-06 07:36:46,755 DEBUG l.682 XwsServer.runXmsAdminCommand - LD_LIBRARY_PATH=$x_home_dir/lib:${LD_LIBRARY_PATH-”"}; export LD_LIBRARY_PATH

2008-11-06 07:36:46,755 DEBUG l.682 XwsServer.runXmsAdminCommand -

2008-11-06 07:36:46,756 DEBUG l.697 XwsServer.runXmsAdminCommand - Running the temporary Synchrony Messaging System admin script

2008-11-06 07:36:46,777 DEBUG l.703 XwsServer.runXmsAdminCommand - Waiting for the temporary Synchrony Messaging System admin script to terminate…

2008-11-06 07:36:46,802 DEBUG l.720 XwsServer.runXmsAdminCommand - Deleting the temporary Synchrony Messaging System admin script…

2008-11-06 07:36:46,805 DEBUG l.725 XwsServer.runXmsAdminCommand - Script file for XMS admin command: /data/elcomxws/xws/Synchrony_V4.0/./temp_script19605.cmd

2008-11-06 07:36:46,806 DEBUG l.747 XwsServer.runXmsAdminCommand - Script file for XMS admin command: /data/elcomxws/xws/Synchrony_V4.0/./temp_script19605.cmd

2008-11-06 07:36:46,806 DEBUG l.763 XwsServer.runXmsAdminCommand - 500209-Failed to start the embedded Synchrony Messaging System

2008-11-06 07:36:46,807 ERROR l.34 XwsException.<init> - 500209-Failed to start the embedded Synchrony Messaging System

2008-11-06 07:36:46,808 DEBUG l.36 XwsException.<init> - 500209-Failed to start the embedded Synchrony Messaging System

500231-Failed to start the Synchrony WebServices server

Press any key to exit …

elcomxws@ebdmz11</data/elcomxws/xws/Synchrony_V4.0># <mailto:elcomxws@ebdmz11%3C/data/elcomxws/xws/Synchrony_V4.0%3E#>

has anyone come across this before ?

What Integrator/XIB version are you running?

Published in November 6th, 2008

Posted by Tony in Axway Forum Syndicate

No Comments

Hello

I’m just curious to know how many run XIB (that is integrator v2) and how many run integrator v3, v4?

Cheers!

Dashboard Tables

Published in November 6th, 2008

Posted by Tony in Axway Forum Syndicate

No Comments

Hi All,
Someone knows how many elements I can have diplayed on a dashboard’s table, I have 100 elements on Page 1 but my list has more elements and I haven’t see any Page 2 or 3 and so on…
Giorgio