B2B Integration

Sterling B2B Integration

Come for answers, stay for best practices. All we're missing is you.

 View Only
  • 1.  Order of export & import resources - migration from 5.2.6.3 to 6.0.3

    Posted Mon March 09, 2020 02:33 PM
    We are upgrading our B2B to 6.0.3. Since the database schemas changed from 5.2.6.3 to 6.0.3, we were advised to do export resources from 5.2.6.3 and then import to 6.0.3.  Question is, is there any specific order to follow like Communities first, groups, partners etc...?

    Any one who has upgraded to 6.0.3 , can you please share your experiences?

    Thanks
    Srini

    ------------------------------
    Srini Parise
    ------------------------------

    #SupplyChain
    #B2BIntegration


  • 2.  RE: Order of export & import resources - migration from 5.2.6.3 to 6.0.3

    Posted Tue April 14, 2020 02:50 PM
    Hi Srini,

    Export all the resources in one single XML and then import in new system in one shot. The system will take care of the referencing the configuration automatically.

    But yes, better if someone can share their experiences as well.

    Regards,

    ------------------------------
    BHARAT BALOTHIA
    ------------------------------



  • 3.  RE: Order of export & import resources - migration from 5.2.6.3 to 6.0.3

    Posted Thu April 16, 2020 01:32 AM
    Bharat -

    The issue we usually face is the size of the single export. Even when we try to import via Unix script for import rather than dashboard option, it errors out with timeouts. Hence we probably want to understand if any sequence has to be followed in case we need to chunk the export into individual resources, e.g. when we try to import user acnts with permissions on mailbox, definitely mailboxes has to be imported before that or it errors out..

    Let us see if anyone has any specific suggestions or experience.

    Thanks,
    Pranjit​

    ------------------------------
    Pranjit Biswas
    ------------------------------



  • 4.  RE: Order of export & import resources - migration from 5.2.6.3 to 6.0.3

    Posted Thu April 16, 2020 06:08 AM
    Edited by System Admin Wed March 22, 2023 11:49 AM
    Hi Pranjit,

    The Sterling B2B Integrator is used by different customers in different way for different purpose so one shoe will not fit for all. There are customers with EDI use cases for them they can export / import the Trading Partner configuration and can export import the EDI maps before or after.

    You can import the things in parts there is no issue. To reduce the export XML file size first export the Translations Maps alone.. Because Translation Maps can occupy quite a lot space specially if there are large XML Schema based Maps. If you have too many Business Processes then export the Business Processes as well in a separate export XML file. There are customers having 1000's of Mailboxes if that is the case then do the export / import of those also using a separate file. Even though you do it in parts but each part should be a unit, for example while exporting importing mailboxes, you have to export import users and associated user permissions as well.

    Don't edit and execute anything before you import all the required assets.

    If you are a SFG customer then File Gateway Configuration can be done separately by following the below steps:
    1. Sterling B2B Integrator Managed Resources – Sterling B2B Integrator Managed Resources can be migrated at anytime (before, after, or with the Sterling File Gateway Community). However, depending on the resources being imported, some may need to be imported after the Sterling File Gateway Community is imported (such as an AS2 Partner). Relationships and dependencies must be considered when determining when and if anSterling B2B Integrator Managed resource should be imported before or after the import of the Sterling File Gateway Community.
    2. Custom Protocols – Custom Protocols must be migrated prior to the Sterling File Gateway Community migration.
    3. Sterling File Gateway Community – The Sterling File Gateway Community must be migrated before Partner Groups (within Sterling File Gateway Configuration) and some Sterling B2B Integrator Managed Resources such as Sterling B2B Integrator managed partners. The Sterling File Gateway Community must be migrated after the migration of any required Custom Protocols.
    4. Sterling File Gateway Configurations – Partner Groups, within Sterling File Gateway Configurations, must be migrated after the Sterling File Gateway Community has been migrated.

    I hope this helps.

    Regards,

    ------------------------------
    BHARAT BALOTHIA
    ------------------------------



  • 5.  RE: Order of export & import resources - migration from 5.2.6.3 to 6.0.3

    Posted Fri April 17, 2020 01:19 AM
    Thanks Bharat. My bad that I was not more specific. I was talking about SFG related components movement predominantly for the particular client.

    ------------------------------
    Pranjit Biswas
    ------------------------------



  • 6.  RE: Order of export & import resources - migration from 5.2.6.3 to 6.0.3

    Posted Mon April 20, 2020 01:32 AM
    I would like to add one more point on Bharat's message, while doing  SFG artifacts export it would be good to lift as resource tag and import into next environment.

    Regards,
    Ahmed

    ------------------------------
    Peer Ahmed Shaik
    ------------------------------



  • 7.  RE: Order of export & import resources - migration from 5.2.6.3 to 6.0.3

    Posted Wed April 15, 2020 10:29 AM
    I believe you are talking about migrating SFG components. If that's the case then you must follow an order in order to make sure that everything works fine, it's applicable for all versions and/or environments. This is documented in IBM documentation - Refer: https://www.ibm.com/support/knowledgecenter/en/SS4TGX_2.2.0/com.ibm.help.sfg_sys_admin.doc/sfg_migratingacommunitywithimportexport.html. Also, coming to B2Bi migrations just make sure that depend configurations are imported together. Assume that you are importing SFTP server configuration, it refers/links to a known host key. So, it's good that they two go together or key first then sftp config. Also, I believe it's easy to track migrations by export and import them as batches and relevant configurations together.

    I have migrated earlier versions, and we are about to go to v6.0.3

    ------------------------------
    Rajasekhar Muthamsetty
    ------------------------------