bin Directory Files

There are several useful scripts and files in the bin directory of the installation directory upon installation of IBM® Sterling B2B Integrator. Additional scripts may be described in the Release Notes.

Important: Some of the files and scripts in the following table are to be used by Sterling B2B Integrator or its components only, and not run or edited by a user. The description for each of these files and scripts contains a caution statement warning that the file or script must not be used or edited. If you use or edit these scripts, Sterling B2B Integrator or various components may not work properly and errors may occur, including the loss of data.

The bin directory is located two directory levels below the installation directory path that you enter during an installation. Between the installation directory and the bin directory is an “install” directory. This is different than many previous directory structures in which the bin directory was directly below the installation directory.

The following table lists files in both UNIX/Linux and Windows installations. In general, UNIX/Linux commands end in "sh" and Windows commands end in "cmd". In some cases, the same file is used for both operating systems.

File (UNIX/Linux)

File (Windows)

 Description

AddLicenseSet.sh

AddLicenseSet.cmd

Adds a new, updated, or renewed license. You must run this command for each licensed feature.

addWorkflow.sh

addWorkflow.cmd

Compiles a flow using an input data file, and then adds it into the system.

agentserver.sh

agentserver.cmd

Starts agent processes.

AntInstallService.cmd

Runs the InstallService.cmd file from an Ant task.

Important: This script should not be called from the command line or from other .cmd or .bat files.

backup_wrapper.sh

backup_wrapper.cmd

Backs up files to an archive directory.

backUplogFile.cmd_b2b_ext

Performs logging tasks for Event Listeners, and Command Line 2 adapter.

BackupLogs.cmd

Back up log files to a directory specified in the sandbox.cfg file.

Important: Make sure that no services are running when the BackupLogs.cmd script is used or the backup will not occur.

backupScriptGen.xml (both UNIX/Linux and Windows)

Creates sample backup scripts for database tables.

backup.sh

backup.cmd

Restores data from backup files.

backupWar.sh

backupWar.cmd

Backs up WAR (web archive) files.

Base64EncodeDecode.sh

Base64EncodeDecode.cmd

Used for Base64 encoding and decoding. Can also be used to encode binary files.

bpDeadlineOfflineNotification.sh

bpDeadlineOfflineNotification.cmd

Performs an offline notification (e-mail and/or write to the file) when the application server is down. Offline notification can only be done for all deadline business processes in one e-mail or file).

buildear.sh

buildear.cmd

Runs the buildEAR.xml file.

buildjaxclient.sh

Generates and compiles the client code to generate a skeleton of a client based on wsgen technology built into the JDK. Generates a Web Services client using the wsimport tool that ships as part of the JAX-WS RI.

build.properties (both UNIX/Linux and Windows)

Used by buildwar and buildear scripts - sets information about locations for application server directory, ejb, etc.

buildrcpapplication.xml.sample (both UNIX/Linux and Windows)

Sample XML file for RCP applications.

buildwar.sh

buildwar.cmd

Builds WAR files.

cdtshell.sh

cdtshell.cmd

Starts the Configuration Deployment Tool (CDT) from the command line. See ydk.sh/cmd for GUI.

cert_util.sh

Imports system certificates.

ChangeSystemPassphrase.sh

ChangeSystemPassphrase.cmd

Changes your system password.

checkCursorLeaks.sh

checkCursorLeaks.cmd

Checks cursor leaks for one database, one individual, or one SQL statement.

checkin_einvoice.sh

checkin_einvoice.cmd

Deploys ordered schema files.

cla2client.exe (Windows only)

Used by the InstallCLA2WindowsService.cmd and uninstallCLA2WindowsService.cmd commands.

CLA2makejar.sh

CLA2makejar.cmd

(Version 5.2.4.1 and interim fix 5.2.4.1_2 or later) Used to create the CLA2RemotePackage.jar in your bin directory. This jar is then used in the remote installation process for CLA2.

CLA2_PasswordUtil.sh

CLA2_PasswordUtil.cmd

Used to decrypt the default keystore password or to encrypt a new password stored in CmdLine2server.properties.

configGSUnix.sh

Integrates Sterling B2B Integrator with IBM Sterling Gentran:Server® for UNIX. Configures Sterling B2B Integrator for trading profile view support.

ContainerService.exe (Windows only)

Used by the InstallContainerWindowsService.cmd and uninstallContainerWindowsService.cmd commands.

ControllerWorkFlow.sh

ControllerWorkFlow.cmd

Manages workflows, including terminating, restarting, stopping, and resuming. Acts on halted, waiting, and interrupted workflows.

convertWSSoaProperties.sh

convertWSSoaProperties.cmd

Removes test configuration information from soa.properties.in.

createBpmetadata.sh

Creates a bpmetadata.xml file for all business processes of a given directory. For all business processes without previously existing metadata, they will be added to the bpmetadata file with default values. If a business process already has metadata in a previously existing xml file, then those values will be used instead. Should the case arise, metadata located in a subdirectory of the source directory will be favored over metadata present in the source. If a previously existing bpmetadata file is located in the source directory, then it will be copied and timestamped so that it is not completely overwritten.

createFactSetIndex.sh

createFactSetIndex.cmd

Creates an index of fact sets in a fact model.

CreateSystemCert.sh

Creates a self-signed system certificate in order to do certain tests (like document encryption).

db_checksum_tool.sh

db_checksum_tool.cmd

Shows a granular report of what resources have changed in the system that customer-specific changes did not permit to get set as defaults.

db_einvoice.sh

db_einvoice.cmd
Sets up the database schema for Sterling B2B Integrator and e-invoicing. Tasks include:
  • Vendor-specific tasks.
  • Creation of indexes, primary key constraints, and foreign key constraints.
  • Insertion of default data.

db_execFile.sh

db_execFile.cmd

Executes an SQL file.

db_exec.sh

db_exec.cmd
Executes an SQL statement.
Note: This command does not work for the DESCRIBE statement.

db_optimization_tool.sh

db_optimization_tool.cmd
Optimizes your database by performing tasks such as analyzing tables and rebuilding indexes.
Note: The database optimization scripts can do a lot of database updates to rebuild the indexes and analyze the database tables while the database is up and running. However, if this is done while Sterling B2B Integrator is running, it might lead to database deadlocks and have an impact on the application. Therefore, it is not recommended to run the scripts while the application is running. But, if you must run these scripts while the application is running, then you must run them only during nonpeak times.

dbschema.sh

Enables you to edit database schemas.

db.sh
Sets up the database schema for Sterling B2B Integrator. Tasks include:
  • Vendor-specific tasks.
  • Creation of indexes, primary key constraints, and foreign key constraints.
  • Insertion of default data.

dbverify.sh

dbverify.cmd

Validates a database's structure. Ensures that the correct tables, columns, and rows are present in the database. During installation, dbverify compares schema of database to database schema required by Sterling B2B Integrator.

decrypt_string.sh

decrypt_string.cmd

Used by other scripts to decrypt the database and server passwords.

deleteVendorJars.sh

deleteVendorJars.cmd

Deletes third party jar files.

deployEARJBoss.xml (both UNIX/Linux and Windows)

Deploys an EAR (Enterprise Archive) file to a JBoss application server. You can also use this file to un-deploy Sterling B2B Integrator.

deployEAR.xml (both UNIX/Linux and Windows)

Deploys an EAR (Enterprise Archive) file to a WebLogic or WebSphere® application server.

deployer.sh

deployer.cmd
  • Deploys components into the application server environment during installation.
  • Deploys additional components into the application server environment through the InstallService.
  • Customizes Sterling B2B Integrator through extension of features, including the following items:
    • Database
    • Templates
    • Resource bundles

deployStandards.sh

deployStandards.cmd

Deploys the updated standards to your server.

documentFetch.sh

documentFetch.cmd

(V5.2.6.1, interim fix 2 or later)

 Saves the contents of a document in the TRANS_DATA table to a file in order to view it. Works with or without encryption.

dump_info.sh

dump_info.cmd

Displays system-related information.

For example, you can run dump_info.cmd to verify that a hot-fix was successfully installed. The successful running of dump_info.cmd will display the Sterling B2B Integrator version number of the hot-fix.

dumpLicense.sh

dumpLicense.cmd

Audit tool. Dumps all of the license files to one file under the install_dir/logs/security directory. All of the components will be listed towards the end of the file.

You can specify another directory as a parameter of this command. If you do not specify another directory, the dump file will be saved to the install_dir/logs/security directory.

dynamic_os.classpath_layer_ext (both UNIX/Linux and Windows)

Classpath information for different layers of Sterling B2B Integrator. Referenced by dynamic_os.sh/cmd.

dynamic_os.sh

Sets up dynamic env variable for supporting .sh scripts.

enccfgs.sh

enccfgs.cmd
Encrypts properties, including database passwords.
Note: Encrypting the database password twice will render Sterling B2B Integrator inoperable.

encrypt_string.sh

encrypt_string.cmd

Used by other scripts to encrypt the database and server passwords.

encryptOFTPPasswords.sh

encryptOFTPPasswords.cmd

Encrypts Odette FTP passwords.

errorQueueManager.sh

errorQueueManager.cmd

Manages error records in the error queue. Tasks include listing, moving, and purging.

exportSSHCerts.sh

exportSSHCerts.cmd

(V5.2.5, interim fix 12 or later)

 Exports the Host Identity Keys. Format is exportSSHCerts.sh <Key Name of key to be exported> <NewPassword to be set> <Filename for exported file> <Metadata file name for key details>

ExportSystemCert.sh

Exports system certificates using the UI

FeatureSet.xml (both UNIX/Linux and Windows)

Used to create the license file.

GenCSR.sh
Used to manage certificate signing requests (CSRs) in the hardware security module (HSM). For more information, refer to the topic on GenCSR parameters.
  • Displays CSRs in the HSM database.
  • Generates a key pair on an HSM and creates a PKCS10 CSR with the public key from that key pair.

generateneotree.sh

Generates the neotree.xml file that contains the dashboard menu structure and the associated permissions for each menu item.

generateTruncateTransactionData.xml (both UNIX/Linux and Windows)

Internal tool used for system testing. Sterling B2B Integrator documentation should not include this. This is not intended for customers.

getServerDetails.sh

getServerDetails.cmd

Gets list of servers registered with the JNDI.

hardstop.sh

hardstop.cmd

Stops a running instance of Sterling B2B Integrator, including the immediate halt of all business processes. Contrast with softstop.sh.

import_services.sh

import_services.cmd

Imports service instances and service definitions.

ImportCACerts.sh

ImportCACerts.cmd

Imports CA (Certificate Authority)-issued certificates.

importMAPs.sh

importMAPs.cmd

Imports map directories.

importOFTPPartnerProfile.cmd

Encrypts OFTP passwords.

ImportSystemCert.sh

ImportSystemCert.cmd

Imports system certificates, like PKCS12, Pem, and Keystore system certificates.

inppbatch (both UNIX/Linux and Windows)

Used by the setupfiles command.

inppconfig (both UNIX/Linux and Windows)

Temporary parameter supplied when the setupfiles script is run. Used to denote all configuration files used when munging files.
Important: Do not use or edit this file.

inppContainerconfig (both UNIX/Linux and Windows)

Temporary parameter supplied when configuring an adapter node.

Used to denote all configuration files used when munging the files for an adapter node.

Note: This file is not meant to be run on its own.

install3rdParty.sh

install3rdParty.cmd
  • Copies non-redistributable vendor files into the Sterling B2B Integrator system, and updates the appropriate configuration files.
  • Copies supplied resources into the Sterling B2B Integrator directory structure.
  • When the options -l, -j or -d are used, the provided jar files are appended to the global classpath. That classpath is maintained within the (UNIX/Linux path shown) install_dir/properties/dynamicclasspath.cfg file.
  • Cleanly removes third party jar files and/or libraries from the filesystem and classpath.
  • Adds the password library and the jdbc drivers to tmp scripts during installation.
  • Adds third-party components (properties, library and .jar files) to the Sterling B2B Integrator environment after installation.

Usage: (UNIX) ./install3rdParty.sh vendorName vendorVersion <-j | -l | -p | -r | -d > filelist [-targetJVM EVERY | NOWHERE | DCL | OPS | APP | AGENT | ACTIVEMQ] [-uninstall] [-nodeploy]

For Windows, change ./install3rdParty.sh to install3rdParty.cmd.

InstallContainerWindowsService.cmd

Installs an adapter container as a Windows service.

InstallExtensions.sh

InstallExtensions .cmd

Script similar to InstallService, but used for customer extension packages.

InstallService.sh_ContainerNodePatch_ext

InstallService.cmd_ContainerNodePatch_ext

The extension files which will be called from InstallService.sh and InstallService.cmd. They are used while configuring the container JVM.

Note: This file is not meant to be run on its own.

InstallService.sh

InstallService.cmd
  • Installs the Sterling B2B Integrator packages during installation.
  • Installs additional packages after installation.
  • Installs patches downloaded from the Support On Demand Web site.
  • Runs ServiceInstallerWrapper.sh script to install patches, services, and other items without running a full installation.
The usage of the script is: 
InstallService.sh packagename.jar [-tests] [-force] [-nochecksum] [-skipXAPI] [-skipJavadocs] [-skipFactorySetup] [-f <silentfile>]

The parameters definitions follow:

  • -tests - indicates that a test package is being installed (generally used by development only)
  • -force - Stands for "force package." Enables you to override license failures.
  • -nochecksum - Using this parameter prevents the script from doing a checksum. The checksum feature prevents the overriding of resources during a patch install or upgrade that have been edited by the user, or rather it prevents the system from marking a newly installed version of a resource as the default version instead of the previously edited one.
  • -skipXAPI - Determines whether to create xapi.jar file. If turned off, XAPIs are not exposed. For internal application developer use only.
  • -skipJavadocs - skip installing the javadocs for this package.
  • -skipFactorySetup - Prevents script from running factorysetup.
  • -f <silentfile> - Indicates that the script should get parameter values from the text file specified in <silentfile>.

InstallSI.sh

InstallSI.cmd
Runs installation program after following tasks have been completed:
  • Loading of license file
  • Entry of installation directory (install_dir)
  • Confirmation of available disk space for Sterling B2B Integrator and database
Important: Do not edit this script.

InstallWindowsService.cmd

Installs Windows services before you launch Sterling B2B Integrator using the startWindowsService.cmd command.

insteinv.savf (both UNIX/Linux and Windows)

Used to install the e-Invoice archive install script on an iSeries operating system.

iwfcdriver.sh

iwfcdriver.cmd

Starts the initialworkflowcontext (iwfc) file manually.

java_wrapper.sh

java_wrapper.cmd

Used by the system as a platform dependent wrapper script whenever the JVM is invoked.

Important: Do not use or edit this script.
launchWinIE.cmd

Launches Windows Internet Explorer.

loadDefaults.sh

loadDefaults.cmd

Loads factory setup settings into an installation. Enables user to update configuration through factory setup settings.

For example, you could load changes in the Sterling B2B Integrator XML by running a script that extracts the details from the XML and constructs the factorysetup to populate a database table. You would then run the loadDefaults.sh script to update the database with that table information.

loadProperties.sh

loadProperties.cmd

Converts property files into XML and loads the files into the database after installation.

localhostChangeNode1.sh

Changes the LOCALHOST property in sandbox.cfg from the default value of localhost to the actual host name.

localizedstringreconciler.xml (both UNIX/Linux and Windows)
Used to:
  • Export missing localized strings from a database.
  • Import new localized strings to the database.
  • Extract existing localized strings to a file.

makeDocEditor.sh

makeDocEditor.cmd

When creating market practices, generates a wizard to use the map in the Message Entry Workstation.

ManageCertAuthority.sh

ManageCertAuthority.cmd

Online Certificate Status Protocol (OCSP) configuration script. For more information, refer to the OCSP documentation.

ManageOCSPResponder.sh

ManageOCSPResponder.cmd

Online Certificate Status Protocol (OCSP) configuration script. For more information, refer to the OCSP documentation.

manageProperties.sh

manageProperties.cmd

Used to load customer override files and for editing properties in command line mode.

mergeLogs.sh

mergeLogs.cmd

Merges multiple logs into one file, sorting and interleaving by timestamp.

noapp.exe (Windows only)

Used by the installnoappswindowsservice.cmd command.

obscure_passphrase.sh

obscure_passphrase.cmd

Encrypts the passphrase that is being entered. If the -q flag is used, you will be prompted for the passphrase and then the passphrase will be encrypted.

Syntax:

obscure_passphrase.sh [-q or] passphrase to encrypt

OFTPPartnerManager.sh

OFTPPartnerManager.cmd

Runs the Odette FTP PartnerManager tool. For more information, refer to the documentation on Odette FTP partners.

opscmd.sh

opscmd.cmd
Uses different arguments to perform tasks like:
  • Tear down any pool connections that are idle (-cREFRESHPOOL)
  • Output an XML document listing the pools and pool sizes for all nodes (-cPOOLSTATISTICS)
  • Output an XML document listing the caches and their sizes (-cCACHESTATISTICS)

ops.exe (Windows only)

Used by the installopswindowsservice.cmd command.

osgiManager.sh

osgiManager.cmd

Manages the OSGI container. Actions include list, start, stop, install, uninstall, viewjndi, and shutdown.

OSSetup.sh

Sets up operating system-specific variables used by many scripts.

patchActiveMQ.cmd

Updates ActiveMQ by uninstalling it and then installing it with patch information.

patchContainerNodes.sh

patchContainerNodes.cmd

Patches OSGI container nodes.

patchJNLP.sh

patchJNLP.cmd

Updates JNLP (Java™ Network Launching Protocol) files. Used with an IP address.

PathQuery.cmd

Searches registry for path-related information. Writes results to tmpFile2 file in bin directory.

perfCheck.cmd

Used by setupfiles.cmd command.

print_url.sh

print_url.cmd

Prints the URL of the Sterling B2B Integrator.

Outputs include:
  • Host
  • Base port
  • Admin context path
  • Comments
  • File name to create launch (Windows script file)

prunsrv64.exe (Windows only)

Installs Sterling B2B Integrator as a Windows service for the Windows platform. For 64-bit machines.

prunsrv.exe (Windows only)

Installs Sterling B2B Integrator as a Windows service for the Windows platform. For 32-bit machines.

psDumpMaster.sh

psDumpMaster.cmd

Requests a dump of state information from a perimeter server.

psmlRestore.sh

Creates .psml files (profile files for dashboard users).

PurgeAll.sh

PurgeAll.cmd

Clears out business process data and associated documents from the Sterling B2B Integrator database.

Arguments include:
  • a - Makes every workflow in the database eligible for purge.
  • t - Truncates eligible database tables to get rid of all deleted rows. This will free space in your database tables. This will also make every workflow in the database eligible for purge.
  • d - This switch is similar to the -t switch. It also truncates the TRANS_DATA table.
    Note: If your storage is FS, manually remove documents in the install_dir/documents folder.
  • l - Lists the names of the database tables that are going to be truncated.

recalculateTuningDefaults.sh

recalculateTuningDefaults.cmd

Recalculates the tuning defaults when a new container is added.

RemoveSystemCert.sh

Displays information about certificates in the Sterling B2B Integrator database, including the object ID.

replaceJDK.sh

replaceJDK.cmd

When a new JDK is installed, this script verifies it against the system requirements and also copies its path information to the sandbox.cfg file. It also re-configures this new JVM, setting up security providers, etc.

restore_wrapper.sh

restore_wrapper.cmd

After a business process and its associated message have been archived, this command restores the archive and audits the business process and associated message.

restore.sh

restore.cmd

Restores data from backup files.

runGenerator (both UNIX/Linux and Windows)

Generates a possible DTD (document type definitions) from an XML document instance.

RunGisQuery.cmd

Runs a query using information from the install_dir\properties\servers.properties file.

runOps.cmd

Starts the Ops server.

runSAP3Class.cmd

Runs the SAP Suite Builder.

runSAPClass.sh

runSAPClass.cmd

Enables you to call any class (that has a main method) inside an SAP-related Sterling B2B Integrator environment. For more information, refer to the topic on the SAP Suite adapter.

run.sh

Starts Sterling B2B Integrator after it has been installed. Starts ActiveMQ, Command Line 2 adapter client, ops server, and noapp server. Starts ASI and all necessary extension components like BI listeners, SAP controller, and other components. To start just ASI, use the startASI.sh (UNIX/Linux) or startASIWindowsService.cmd (Windows) command.

runWMDtdGenerator.cmd

Generates a possible DTD (document type definitions) from an XML document instance.

sc_setup.sh

sc_setup.cmd

Creates system certificates.

ScheduleBackup.cmd

Schedules the usage of the BackupLogs.cmd command.

ScheduleStopOps.cmd

Schedules the usage of the stopOpsWindowsService.cmd command.

ScheduleStopWindowsService.cmd

Schedules the usage of the stopWindowsService.cmd command.

sci_ant.sh

sci_ant.cmd

Invokes ant scripts in bin directory and properties of SCI installations.

scm-package.xml (both UNIX/Linux and Windows)

When installing the IBM Sterling Community Manager, creates the forscm.jar from the Sterling B2B Integrator instance.

SearchFiles.cmd

Searches files specified in an input file. Used to search for error messages in Sterling B2B Integrator log files.

securityContext.sh

securityContext.cmd

Creates a security context for an installable bundle, which can prevent unauthorized users from creating or updating resources.

semaphoreDriver.sh

semaphoreDriver.cmd

Deletes or selects sempahores, which are used to lock resources.

sender.sh

sender.cmd

Invokes testclientsender, used for testing.

Usage is as follows:

java com.yantra.integration.adapter.client.TestClientSender <flowName/systemApiName> <is firstParameter Flow (Y/N)> <xmlFileName>

where:
  • The first argument takes the name of a service/sdf (flowName) or an API name (systemApiName)
  • The second argument (is firstParameter Flow (Y/N)) determines whether the first argument is a service or an API. Valid values are Y and N. If the first argument is a service, use Y, if it is an API, use N.
  • The third argument (xmlFileName) takes the path and name of the XML input file you want to use as input to the API or service.

ServiceInstaller.sh

ServiceInstaller.cmd

Used to install services, patches, and service packs for Sterling B2B Integrator.

ServiceInstallerWrapper.sh

ServiceInstallerWrapper.cmd

Runs ServiceInstaller command after checking for package version information and making any updates to patcher.

SetAuthorityCertsOCSPInfo.sh

SetAuthorityCertsOCSPInfo.cmd

Online Certificate Status Protocol (OCSP) configuration script. For more information, refer to the OCSP documentation.

setParmsForWinServices.cmd

Works with the prunsrv.exe and prunsrv64.exe commands.

SetSystemCertOCSPInfo.sh

SetSystemCertOCSPInfo.cmd

Online Certificate Status Protocol (OCSP) configuration script. For more information, refer to the OCSP documentation.

SetTrustedCertOCSPInfo.sh

SetTrustedCertOCSPInfo.cmd

Online Certificate Status Protocol (OCSP) configuration script. For more information, refer to the OCSP documentation.

setup_alerters.sh

setup_alerters.cmd

Loads alerter properties.

setupContainerfiles.sh

setupContainerfiles.cmd

Runs the setupfile command for container nodes.

setupContainer.sh

setupContainer.cmd

Configures one adapter container JVM.

setupEInvoiceArchive.sh

setupEInvoiceArchive.cmd

When using Sterling e-Invoicing, helps you create the necessary archive database configurations. For more information, refer to the topic on installing the e-Invoice archive install script.

setupfiles.sh

setupfiles.cmd

Applies configuration changes to an installation.

For example, you would run this command after changing a property file.

si.exe (Windows only)

Used by the installpassphrasewindowsservice.cmd command.

skinCommands.xml

Used by the unpackwar and backupwar commands.

softstop.sh

softstop.cmd

Stops a running instance of Sterling B2B Integrator, after finishing all business processes. Contrast with hardstop.sh.

softstop.vbs

Virtual Basic script that is used to soft stop Sterling B2B Integrator.

start_CLA2_console.cmd

Installs the Command Line2 adapter on a remote server as a Windows service.

start_event_console.cmd

Starts the event listener service. This command is triggered in a separate console window when you are executing the start_si_console.cmd command.

start_noapp_console.cmd

Performs a thread dump in Sterling B2B Integrator.

start_ops_console.cmd

Starts the Opsserver service. This command is triggered in a separate console window when you are executing the start_si_console.cmd command.

start_passphrase_console.cmd

Starts the passphrase service. This command is triggered in a separate console window when you are executing the start_si_console.cmd command.

start_si_console.cmd

Runs Sterling B2B Integrator in console mode.

startActiveMQ.sh

Starts the ActiveMQ server (UNIX/Linux).

startActiveMQWindowsService.cmd

Starts the ActiveMQ server (Windows).

startASI.sh

startASIWindowsService.cmd

Starts only ASI without any extension components. Can be used in place of run.sh, which starts ASI and all necessary extension components like BI listeners, SAP controller, and other components.

startCLA2WindowsService.cmd

Starts the Command Line 2 adapter.

startCluster.sh

startCluster.cmd

Configures each node of a cluster before you start running each node.

startCmdLine2.sh

startCLA2WindowsService.cmd

(Version 5.2.4.1 and interim fix 5.2.4.1_2 or later) Starts Command Line Adapter 2 (local).

startCmdLine2.sh

start_remote_CLA2_console.cmd

(Version 5.2.4.1 and interim fix 5.2.4.1_2 or later) Starts Command Line Adapter 2 (remote).

startContainer.sh

Starts one or more adapter container JVM(s).

Before running this command, you must shut down Sterling B2B Integrator, and run the command startCluster.sh 1 false.

startContainerWindowsService.cmd

Starts an adapter container Windows service.

startHealthMonitor.sh

startHealthMonitor.cmd

Starts Health Monitor.

startIntegrationServer.sh

startIntegrationServer.cmd

Starts Integration Server.

startListeners.sh

startEventListenersWindowsService.cmd

Manually starts event listeners after you manually stop them using the stopListeners.sh command or the stopEventListenersWindowsService.cmd command. For more information, refer to the topic on testing listeners.

startPerformanceLogger.sh

startPerformanceLogger.cmd

Starts the logging of performance statistics, including statistics for the engine and services.

startSAPController.sh

startSAPControllerWindowsService.cmd

Manually starts the SAP Controller Server. For more information, refer to the SAP Suite adapter topic.

startSAPIsAliveChecker.sh

startSAPIsAliveChecker.cmd

Checks for the SAP Controller Server state and the SAP Suite instances running in the controller. For more information, refer to the SAP Suite adapter topic.

startWindowsService.cmd

Starts all Windows services, including all ASI Windows services plus all adapter container(s).

stopActiveMQ.sh

Stops the ActiveMQ server (UNIX/Linux).

stopActiveMQWindowsService.cmd

Stops the ActiveMQ server (Windows).

stopASI.sh
  • Stops the ASI node of a cluster.
  • Stops the NoApp and Ops server.

stopASIWindowsService.cmd

Stops ASI Windows services, not including adapter container.

stopCmdLine2.sh

Stops the Command Line 2 adapter.

stopContainer.sh

Stops one or all adapter container JVM(s).

stopContainerWindowsService.cmd

Stops an adapter container Windows service.

stopListeners.sh

Stops the remote event listeners.

stopSAPController.sh

stopSAPControllerWindowsService.cmd

Stops the SAP Controller server. For more information, refer to the SAP Suite adapter topic.

stopWindowsService.cmd

Stops all Windows services, including all ASI Windows services plus all adapter container(s).

SwnetCorrMigrate.sh

SwnetCorrMigrate.cmd

Migrates SWIFTNet Correlation data to new database tables.

sysinfo.sh

sysinfo.cmd

Generates information for a Customer Support case.

tee.exe (Windows only)

Used for logging.

Important: Do not use or edit this file.

templateXmlGen.xml (both UNIX/Linux and Windows)

Generate sample templates when the database is extended with custom or hangoff tables.

test_db_if_active.cmd

Tests the database connection to Sterling B2B Integrator.

tmp.sh

tmp.cmd

Used by many scripts to obtain Sterling B2B Integrator environment information.

Important: Do not use or edit this script.

triggeragent.sh

triggeragent.cmd

Triggers an agent on the completion of an event.

UninstallContainerWindowsService.cmd

Uninstalls an adapter container Windows service.

UninstallWindowsService.cmd

Removes the Sterling B2B Integrator service entries associated with your Sterling B2B Integrator instance.

unpackWar.sh

unpackWar.cmd

Explodes a WAR (web archive) file to a directory.

updateJavaSecurity.sh

updateJavaSecurity.cmd

Adds the security provider list to the jdk/jre/lib/security/java.security file.

Important: Do not use or edit this script.

updateJDK.sh

updateJDK.cmd

Handles preinstallation tasks related to JDK.

Important: Do not use or edit this script.

upgradeFactModelsTo521.sh

upgradeFactModelsTo521.cmd

Upgrades the reporting services fact models to the 5.2.1 release of Sterling B2B Integrator.

upgradeJDK.sh

upgradeJDK.cmd

Upgrade major/minor level JDK.

(Version 5.2.4.1)

Usage for upgrade is:
  • upgradeJDK.sh <upgraded JDK absolutePath>
  • upgradeJDK.cmd <”upgraded JDK absolutePath”>

(Version 5.2.4.2 or later)

Usage for upgrade is:
  • upgradeJDK.sh <upgraded JDK absolutePath> <JCE Path>
  • upgradeJDK.cmd <”upgraded JDK absolutePath”> <"JCE Path">

When patching or upgrading to V5.2.6 or later, you do not need to run the upgradeJDK.sh or upgradeJDK.cmd command. The Installation Manager upgrades to the appropriate JDK version during the upgrade or patching. However, if you need to update only the JDK without updating Sterling B2B Integrator, then you must run the upgradeJDK.sh or upgradeJDK.cmd command.

workflowLauncher.sh

workflowLauncher.cmd

Launches a workflow.

xsdGenerator.xml (both UNIX/Linux and Windows)

Tool for creating DTDs for extended XML for Sterling B2B Integrator. It converts a specially-formatted XML file into a DTD and XML schema definition (XSD).

ydk.sh

ydk.cmd

Script called to start the Configuration Deployment Tool (CDT) from the GUI. Use cdtshell.sh/cmd for command line.

zenginConfigHelper.sh

zenginConfigHelper.cmd

Exports a Zengin XML configuration from the data source to a file. For more information, refer to the Zengin TCP/IP adapter topic.

zenginSecureConfig.sh

zenginSecureConfig.cmd

Obscures (encrypts) the client alias passwords and file access keys contained in the Zengin XML configuration file. For more information, refer to the Zengin TCP/IP adapter topic.