SI Administration

on

1. What is Softstop?

Ans: A soft stop of Sterling B2B Integrator allows existing processes the opportunity to complete or be saved for resumption after restart.

This can save you time by eliminating the need to manually resume processes after a restart. You can run a soft stop from either the UI or from the command line.

A soft stop provides the ability to interactively step through the shutdown process. It allows the following to happen during a shutdown:

  • The transfer of running business processes to other cluster nodes or to the database for recovery.
  • The ability to control the completion of queued business processes.
  • The ability to show the status of adapter activity and open sessions.
2. How to change BusinessProcess Queue /node?
Ans: while deploying the business process we can change the BP Queue and Node
if you want to change the Queue or Node dynamically we can pass below parameter

        <assign to="mandatoryNode">node</assign>
  using QueueWatcher we can update the Queue by dynamic

3 What is cache uses in a sterling integrator?
     The cache is used to increase /decrease disk space in the sterling integrator.

4. what is noapp.property file?
5.what are the list of the cleanup process?

list of the Cleanup process:
---------------------------
    Schedule_BackupService
    Schedule_IndexBusinessProcessService
    Schedule_PurgeService
    Schedule_BPLinkagePurgeService
    Schedule_BPRecovery
6. what is Customer_override.property file?
     Customer_override.property file is not the default property file. this is defined by us.
      if you want to override any property files using customer_override.property file.

7. How to access external databases in a sterling integrator?
    Ans:  Creating external JDBC pools in  jdbc_customer.properties.in a file and run setup files.sh/cmd then it will create JDBC pool in sterling integrator.

8. If you upgrade a sterling integrator version the existing created pools will be available or not?
Ans: No, once you upgrade the sterling integrator existing property files are updated with the latest version. 
    Define any properties in Customer_override.property file , this file will not be updated after upgrade the sterling integration version.


9.what is the use of setup files.sh/cmd command?

  When you are updating the *.properties.in files in the sterling integrator setup files update the changes in *.properties files.

10. Update property values in customer_override.property file?
Ans: you can create a customized properties file to override default property settings in the property files.

The customer_overrides.properties file is not changed during installation of upgrades or patches. To prevent having your customized settings overwritten, use overrides whenever possible rather than editing the property files.

For example, to set the value of the bp_response_timeout property in the http.properties file so that it is not affected by the bp_response_timeout property in the http.properties.in file when the setupfiles script is run, add the following line to the customer_overrides.properties file:

http.bp_response_timeout=value


Steps for Application upgrade:

A). Pre- upgrade preparations:
   1. Download the installation for SI (Media zip) and IBM Java SDK(SDK zip) for the planned version.
   2. Upload it to /sterling/data/ or /MFT  shared folders in SI or MFT linux Server respectively using winscp.
        Steps to upload files to winscp.
       1.  Login to client network firewall login client http:   with sftp login 
       2.  Open winscp and click on New session use below mentiones parameters to login 
           File Protocal : SFTP
             Host , Port,User id, Password: 
       3. Navigate to the directory where the file host used above
       4. copy the file from local file system in left pane to the directory in the linux server .
       5. wait for the file transfer to complete and validat once done in linux server
   3. Unzip the media file to a separate folder for in the directory. Use below command
         unzip fileA.zip
         or 
         unzip -d destinationDirectory fileA.zip
      
        Note: If the above unzip commnd(s) throws zip bomb error , use below  command to create a fresh zip of the zip file.
  zip --FF fileA.zip  --out fileA_new.zip -fz
        unzip fileA_new.zip 
   4. Verify below list of files/folder  is avaliable in the destionation directory. 
      common_repo.zip
      InstallationManager
      Packages
      ResponseFiles
      UpdateScript
      Unzip Common_Repo.zip as well to see below 2 additional folders.
       b2birepo 
   5. Before unzipping IBM Java zip file, move the current java sdk zip and jre bin files to a new folder to avoid file overwrite during unzip ( Ex:ibm-java)
   6. Unzip IBM java SDK as well (in same folder where the zip file is present). Below list of files/ folders will be available in the directory.
  IBM-java-sdk-8.0-7.15-ppc64-archive.bin
  Ibm-java-sdk-8.0-7.15-z86_64-archive.bin
  Ibm-java-sdk-80-win-x86_64.zip
  J864redist.8.0.0.715.bin
   7.Create responsefile
  a. copy the path of b2birepo folder from line 39 above.
  b. go to path/sterling/IM/eclipse/tools.
  c. In the list of response files in this folder, take backup of latest response file and create a copy of it and rename it to create a new response folder.
  Ex: <repository location=’/sterling/data/mft/b2bi_6.1.2.0/b2birepo/>
  d. open new reposnefile and update the path of the b2birepo folder noted above in repository location tag.
   8. Communication:
  1. Notify partners on the upgrade plan and outage schedule over email.
  2. Raise a task for DB team to take to level zero backup on the scheduled time.
  3. Raise a task to Linux team to take a snapshot of / sterling on the scheduled time. ( Not mandatory, because we are only taking backup of / sterling/sb2bi or

C : Upgrade
  Application down. If external perimeter server is also to be upgraded (in QA and Prod), the have complete outage.
  Take backup of below mentioned components.
  Java.security from/sterling/sb2bi/install/jdk/jre/lib/security into/ sterling/data/MFT (or in SI, from/sterling/SI/install/jdk/jre/lib/security
  Skin properties file skins. Properties_style_ext from/sterling/sb2bi/install/properties into/sterling/sb2bi/data/MFT( or in SI, from/ sterling/
  Take backup of key.p12 from/ sterling/sb2bi/install/liberty/wlp/usr/servers7server/resources/security into sterling/data/MFT( or in SI, from/
  Database level 0 backup
  Take backup of /sterling/SI or/ Sterling/ sb2bi
  Tar -cvzf sterlingData_22ndjune2023.tar.gz/Sterling/sb2bi
  Note steps a to d mentioned above can be performed before down application also.
D) Start Upgrade.
  Once, all the backup and pre-work is complete
  Use below command to initiate upgrade execution using response file. Run this Command in / sterling/IM/eclipse/tools folder only.
  ./imcl-input RESPONSE_FILENAME- application sVP
  Note: all the details the passes in the screen during the response file. Run this command in / sterling/IM/eclipse/tools folder only.
D) Post-upgrade.
  a. verify if there is any difference in Java.security file post upgrade( particuralry for IBM JCE parameters) and that in pre-upgrade.

 

=====
Post _upgrade:
        
        a. Verify if there is any difference in java.security file post upgrade(Particularly for IBM JCE parameters) and that in Pre-upgrade.
     if there any difference, update the value as it was in the past and save.
        b. replace new skins.properties_style_ext with the oldone 
        c. Key.p12 file with be lost , copy teh key.p12 that was taken as backup in the directory /Sterling/sb2bi/install/liberty/wlp/usr/servers/SIServer/repository
        d. Only in SI,
                  1. Uninstall old sap jar and library using below commands,
                       ./install3rdparty.sh sapjco3 3_1 2 -j /sterling/SI/install/jar/sapjco/3.1.2/ sapjco3.jar  -uninstall 
                       ./install3rdparty.sh sapjco3 3_1_2 -l /sterling/SI/install/lib/sapjco/3.1.2/linux/libsapjco3.so  -uninstall
                  2. Install New sap jar and library using below commands.
                       ./install3rdparty.sh sapjco3 3_1_2 -j /sterling/SI/install/jar/sapjco/3.1.2/ sapjco3.jar
      ./install3rdparty.sh sapjco3 3_1_2 -l /sterling/SI/install/lib/sapjco/3.1.2/linux/libsapjco3.so
        e. Install the new B2B RestAPI package ( from (/sterling /packages using below commond . only if this is executed, customization portal
                   ./InstallService.sh   .../Package/b2bi.jar (Should run this in bin directory since that where the script is present)
E).  Upgrade External PS.( Not Required in DEV)
        a. Copy the new PS jar from /sterling/sb2bi/install/packages to /sterling directory in all external PS servers and install it using below command in all
                    ./java -jar /sterling/ps_68102020.jar 
           
              Installation directories  >> /Sterling/PS_int_SI_1 , /sterling/PS_Int_SI_2. so run above command separately for these installation directories 
   Note:  Make sure SI and PS have same compatible JSK version over it.
         b. Update Perimeter properties   --gmm.maxallocation to 1024 MB to allow more connection.

 

F).Bring up the application and all other components 
        a. Execute setupfiles.sh and deployer.sh
        b. Bring up the application and all the components.
G) Validations.
     a. Perform all the validations post upgrade.
     b. Disable filegateway schedules in SI .

 

 

                   
                            .













  



. 

Comments

Post a Comment