B2B Integration

 View Only

  • 1.  Hardware/System replacement with current B2Bi/SFG settings and configuration

    Posted Thu April 15, 2021 07:33 PM
    Hi,
    Currently we are running B2Bi/SFG 6.0.3.4. using RHEL 7.8
    It is running in old hardware that need to be replaced with new hardware. This is cluster environment.

    Any one went through this process?
    What steps we need to take to keep current B2Bi/SFG settings?

    Thanks for your help.
    Asim

    ------------------------------
    Asim Mondal
    ------------------------------

    #B2BIntegration
    #SupplyChain


  • 2.  RE: Hardware/System replacement with current B2Bi/SFG settings and configuration

    Posted Fri April 16, 2021 08:15 AM
    Edited by System Wed March 22, 2023 11:55 AM
    Hi Asim,

    There are several options.

    1.) You can mount the SFG file system that was on your old hardware to your new hardware. Modify the SFG configurations to use new IPs/hostnames. Thoroughly, do a regression testing.
    2.) You can do a fresh install and migrate all the resources.

    Kishore

    ------------------------------
    KALYAN PAVAN KISHORE CHAKRAVARTHULA
    ------------------------------

    Original Message


  • 3.  RE: Hardware/System replacement with current B2Bi/SFG settings and configuration

    Posted Fri April 16, 2021 09:38 AM
    Asim

    These are the high level steps from memory assuming your DB didn't change and you have connectivity in place from the new hardware to DB and all other components connected to SFG:
    1. Stop the application on the old servers
    2. Bring the file systems including ~/etc and ~/var folders if applicable to the new servers. 
    3. Mount any shared file systems on the new servers if applicable
    4. Assuming the new servers have new host names and Ips, take a backup and update sandbox.cfg with the new hostnames for each host in the cluster
    5. Run setupfiles script
    6. Run deployer script (Not required these days, but has solved some issues even recently)
    7. Run startCluster script with true for primary token and false for the rest of the nodes
    8. Run run script with restart flag on the primary / token node
    9. Start the rest of the nodes normally
    10. Your cluster should be up on the new hardware.
    11. Verify API services
    12. Verify cluster status
    13. Verify queueWatch
    14. Send some test files
    15. If you have any startup/shutdown management scripts, put them in place as well. You could refer to this open source python modules to setup start/stop/status/restart processes across your sterling portfolio using this: https://github.com/openmft/amf-svc-py

    --
    Regards,
    Srinivas Ganti




    Original Message


  • 4.  RE: Hardware/System replacement with current B2Bi/SFG settings and configuration

    Posted Fri April 16, 2021 10:40 AM
    Hi Kishore and Srini,
    Thanks for your input.
    I wanted to mention  few more things in this context.
    All hardware's need to be replaced. 
    Database server with RAC storage. Mounted file system for SFG.
    Also, currently we have three node cluster. In new hardware set it will be two node cluster.  We are taking very powerful  IBM Power System with RHEL.

    Looks to me Kishore's option 2 is only way to go. 

    Thanks,
    Asim Mondal

    ------------------------------
    Asim Mondal
    ------------------------------

    Original Message