Zero Bytes

import com.sterlingcommerce.woodstock.workflow.Document; import java.io.InputStream; import java.io.InputStreamReader; import java.io.BufferedReader; Document doc = wfc.getPrimaryDocument(); Document outPutDoc = wfc.newDocument(); ; InputStream inS = doc .getInputStream(); BufferedReader br = new BufferedReader( new InputStreamReader( inS )); String strData = “<SampleData>” ; String strLine; while ((strLine = br .readLine()) != null ) {     strData = strData.concat(strLine); } br.close(); strData = strData + “</SampleData>”; outPutDoc. setBody( strData .toString().getBytes()); wfc.putPrimaryDocument( outPutDoc );

First of all the following value has to be unique to each install of Sterling Integrator. If you accidentally used shared location for cluster installation your second node installation not going to work. So here is how we can fix this. 1. Go to user home and move $USERHOME$/IBM/IBMSHARED to new local location. 2. Update the reference in  /home/user/var/ibm/InstallationManager/installRegistry.xml           That's it. This will fix First node IBMSHARED location and we can proceed with second node installation. How to verify? 1. Go to InstallManager tools     cd /InstallationManager/IM_Linux/tools  2. ./imcl listInstalledPackages -verbose Validate the output something like below, [Shared] Shared resources directory: /opt/ibm/IBMIMShared [Package group] Name: Sterling Integrator Installation directory: /opt/ibm/sfg Translations: Architecture: 64-bit [Package] Name: IBM Sterling B2B Integrator (com.ibm.sterling.in...

Some of the IBM Sterling B2B Integrator(SI) customers wants to avoid SSH handshake using CBC Cipher as it is vulnerable. The link  http://www.kb.cert.org/vuls/id/958563  explains that CBC Ciphers are security vulnerable and the solution is to use CTR Cipher instead of CBC Cipher. However, in SI versions 5020602 and 5020603, maverick (the third party api used for SSH/SFTP) version used is 1.4.60 which mandates that CBC Cipher should be present in Client side. Hence, disabling the CBC support using the security property supportCBCCiphers=false will result in SFTP communication failure with key based authentication. To enforce the use of CTR Cipher in SI, we have introduced two new properties : SSHServerCipherList, SSHClientCipherList a) security.SSHServerCipherList is the property to restrict the list of server side ciphers. In the SFTP Server adapter, "Preferred Cipher" drop down will pick the values specified in this property list. b) security.SSHClientCipherList is...

Generate PGP Keys gpg --gen-key Enter Key details, Email, Expiration etc., Export Secret Key gpg --export-secret-key -a MY_PGP_KEY >> /tmp/MY_PGP_KEY.key Export Public Key gpg --export -a MY_PGP_KEY >> /tmp/MY_PGP_KEY.asc Import Secret Key gpg --import /tmp/MY_PGP_KEY.key Import Public Key gpg --import /tmp/MY_PGP_KEY.asc Update Key Trust Trust after importing the Key gpg --edit-key $trust $5 $save

Active Worksflows in Sterling Integrator select DISTINCT NAME , WC2.WORKFLOW_ID, sysdate - START_T AS TIMEDIFF From WORKFLOW_CONTEXT WC, ( SELECT MAX(STEP_ID) STEP_ID , MIN(START_TIME) START_T, WORKFLOW_ID FROM WORKFLOW_CONTEXT GROUP BY WORKFLOW_ID ) WC2, WFD WHERE WC.WORKFLOW_ID = WC2.WORKFLOW_ID AND WC.STEP_ID = WC2.STEP_ID AND WC.NEXT_AI_ID != -1 AND WC.WFD_ID = WFD.WFD_ID AND WC.WFD_VERSION = WFD.WFD_VERSION AND BASIC_STATUS = 0 Sterling Integrator User & User Associated Groups List  select YFS_USER.LOGINID, YFS_USER_GROUP.USERGROUP_NAME from YFS_USER, YFS_USER_GROUP, YFS_USER_GROUP_LIST where YFS_USER.USER_KEY=YFS_USER_GROUP_LIST.USER_KEY and YFS_USER_GROUP.USERGROUP_KEY=YFS_USER_GROUP_LIST.USERGROUP_KEY

http://www-01.ibm.com/support/docview.wss?uid=swg21628336 Sometimes SSHKeyGrabber don't work when we trying to extract Known Host Key from Sterling Integrator UI. The work around for this is disable StrictHostKeyChecking and download the Key from Linux/Windows and Check in the key to Sterling Integrator. $ssh -o StrictHostKeyChecking=no user@sftp.host.com -p 22 Above command will save host key to known_hosts file located .~/.ssh/known_hosts Note: Remove excess content from host key and just keep the key from ssh-rsa followed the key. 

asset.jar b2b_aee.jar b2b_base.jar b2b_oba.jar ebics.jar entities.jar gis.jar install_foundation.jar mailbox.jar maverick-all.jar perimeter.jar platform_activemq.jar platform_activity.jar platform_afc.jar platform_afc_security.jar platform_aop.jar platform_asi.jar platform_baseutils.jar platform_dv.jar platform_ifcbase.jar platform_ifcui.jar platform_osgi.jar platform_security.jar platform_services.jar resources.jar soap.jar standards.jar translator.jar

Navigate to IBM JDK bin directory and execute the following command, C:\Sirish\Softwares\ibm_sdk80\bin>java com.ibm.gsk.ikeyman.Ikeyman

If we want to install external JARs (3rdParty JARs) on Sterling Integrator here are the steps, 1. Stop B2BI Cluster (All Nodes) by running hardStop.sh/cmd. 2. install3rdParty.sh -j          -j = JAR          -l = Library File 3. Run setupfile.sh 4. Repeat Step 2 and 3 on all Nodes. 5. Restart B2BI Cluster. Validation Procedure: If installation was successful then you will see an entry for your new JAR file in dynamicclasspath.cfg file.  

Here is how IBM Sterling B2B Integrator map editor translator controller parse and executes the Rules. Pre-Session (Variable Declarations & Hard Coded Values) Root On Begin    Root Exedend Rules Record On Begin Standard Rule & Exedend Rule Record On End Root On Begin Post-Session (Executes before end of map)

soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:mesa="http://www.sterlingcommerce.com/mesa"    soapenv:Header/    soapenv:Body       mesa:DEMO_WEB_SERVICE xmlns:mesa="http://www.sterlingcommerce.com/mesa" Payload goes here....       /mesa:DEMO_WEB_SERVICE    /soapenv:Body /soapenv:Envelope Need to add namespace xmlns:mesa="http://www.sterlingcommerce.com/mesa under soapenv:Body.

1. Download  VisualVM      https://java.net/projects/visualvm/downloads/download/release138/visualvm_138.zip 2. Find the value of the property called  ACTIVEMQ_JMX_PORT from sandbox.cfg. 3. Add Remote Host First and under Remote Host add Add JMX Connection.      < SI HOST Name >:< ACTIVEMQ_JMX_PORT >     No need of providing user credentials and Save the connection. 

Starting an External Purge Procedure If you have a cluster installation, make sure that you are not running the external purge on another node of the cluster. If you are running the external purge on more than one node, it will cause database locks. For more information, see  Monitoring an External Purge . Important:  It is the customer's responsibility to keep exactly one of these external purge processes running in the cluster. If you need to shut down the hardware that is running the external purge, you must run the external purge on a different node. Disable the default Purge service. Click  Deployment  >  Schedules , search for PurgeService, and then clear the  Enabled  checkbox for PurgeService. Note:  If you have customized the Schedule_PurgeService business process, you need to add your customized code to the new Schedule_PurgeService business process. The new Schedule_PurgeService business process includes a warning mess...

http://www.cyberciti.biz/faq/lftp-mirror-example/ $lftp user@my.ftp.com $ mirror -c source target Reverse Sync to Server: Change local directory to  where you saved the files /home/somedirectory $ lcd /home/somedirectory $ mirror -R

There was bug in SFG (old versions) where it leaves some orphan entries in DB when you try to remove the trading partner from SFG UI. To solve the problem here are steps to do hard delete of partner profile. Attempt to delete from SFG in regular way and then remove from Dashboard --> Trading Partner (All Contracts, Document Exchange, Profile, Routing Channels, Mailbox Virtual Roots if any etc.) Make sure the following table should not return any entry for Trading Partner, If it returns then remove the entry manually... This example Partner Name is : EDI select 'YFS_USER' from YFS_USER where UPPER(USERNAME) like '%EDI%'  UNION select 'YFS_ORGANIZATION' from YFS_ORGANIZATION where UPPER(ORGANIZATION_KEY) like '%EDI%'  UNION select 'MBX_ACTION'  from MBX_ACTION where UPPER(USER_ID) like '%EDI%'  UNION select 'MBX_MAILBOX'  from MBX_MAILBOX where UPPER(PATH) like '%EDI%'  UNION select 'SCI_CONTRACT' fro...

Integration Patterns:    Enterprise Integration Patterns    Self Managing      Minimize the dependency between components.      John Prosul Robust principle      Be liberal with what you receive and be specific with what you send out.      Always support previous versions (Backward compatibility). It's always hard to support backward compatibility but it's matter of discipline.      Software is craft not a science.      Be wise on Technical Decision vs Business Decision.      InfoQ.com      gotoconferences    Twitter University    Emerging Techologies for Enterprise (Conference hosted in Philly)      Agile Stuff      hackernews.com (YCombinator)      HighScalability.com      Netflix Engineering      Thoughtworks Tech Rada...

import java.io.InputStream; import java.lang.StringBuilder; import com.sterlingcommerce.woodstock.workflow.Document; import com.sterlingcommerce.woodstock.util.Base64; Document doc = wfc.getPrimaryDocument(); InputStream in = doc.getInputStream(); StringBuilder sb = new StringBuilder(); for (int i = 0; i < in.available(); i++) {    sb.append(in.read()); } byte data[] = sb.toString().getBytes(); byte newdata[] = Base64.encode(data); doc.setBody(new String( " "+ new String(newdata)+" ").getBytes()); return new String(sb.toString());

1.  EDI_COMPLIANCE_RPT 2.  EDI_DOCUMENT_STATE 3.  WF_INST_S 4.  WORKFLOW_CONTEXT 5.  WORKFLOW_LIFESPAN 6.  WORKFLOW_DATA 7.  EDIINTDOC 8.  MSGMDNDUP 9.  MSGMDNCORRELATION 10. WEBX_MINED_DATA 11. WF_INACTIVE 12. GENERIC_ACK 13. CORRELATION_SET 14. ACT_SESSION 15. ACT_AUTHENTICATE 16. ACT_AUTHORIZE 17. ACT_XFER 18. ACT_NON_XFER 19. DATA_FLOW 20. DMI_ROUTE 21. DMI_ROUTE_FACT 22. MBX_MESSAGE 23. TRANS_DATA

https://edigkim.wordpress.com/ http://i2b2b.blogspot.com/

The actual error we see in the logs is just the way SFTP in SI detects duplicate files and since you have the option in the mailbox.properties set to: disallowDuplicateMessages=false This means that duplicate files are allowed and therefore SFG processed those duplicate uploads. So the partner should investigate why did their application trigger a duplicate upload of the same file. If you want to avoid duplicate uploads, you should consider setting the option disallowDuplicateMessages to true in both nodes, this will stop SI from accepting duplicate files. If you want to make that change, you will need to modify\create your customer_overrides.properties on both nodes and add the following line: mailbox.disallowDuplicateMessages=true Both nodes need to be restarted for the change to take effect.