Hi Kiran,
I would add to Holm's answer that behind the hood, IntegrationServer/instances/<instance>/bin/{startup,shutdown}.(sh|bat)
scripts call theprofiles/IS_<instances>/bin/{startup,shutdown}.(sh|bat)
scripts, so choosing either way shouldn't matter.
And as said by Wayne, if you install a 11.1, you won't have to worry anymore as only the IntegrationServer/instances/<instance>/bin/{startup,shutdown}.(sh|bat)
will be present
.
However, contrary to what Zainul said, starting the IS using profiles/IS_<instance>/bin/startup.sh
does not initialize the Platform Manager. Although based on the same components (OSGi framework and Tanuki wrapper), hence the confusion, they are two different components.
------------------------------
Mathieu Aguesse
webMethods Delivery Consultant
IBM France
------------------------------
Original Message:
Sent: Thu May 08, 2025 11:31 AM
From: Holm Steinland
Subject: Starting IS from profiles folder vs Default folder
Hi Kiran, many thanks for your question. Many people do not know the difference. So no worries for asking.
First of all your question indicate that you are using a full fletch "IS - Integration Server" not only the "MSR - MicroServiceRuntime". In the later case you have no such "instance" folders because only one IS per home is started. So in this case you start it directly from the main folder. (./IntegrationServer/default/bin )
For IS the concept allows to run "instance", multiple on one server. Those are separated also in "profiles". The main folder is kind of the master and will be cloned into a new instance when you create that.
Is means that when you know you will also need libraries like for JDBC or SAP connectors, you can add them to the main folder and when create new instance they will be also applied to the same.
However you never start IS from that folder directly because your "config files", logfiles etc. pp. need to be specific per "instance". 😁
Now you might ask why those PROFILES at all, in the legacy world you could also start the IS directly with "server.sh". Absolutely yes, and you still can, but there is a ready why the "profile" was invented around it. It uses the "Tanuki wrapper" and context information to customize your IS (e.g. most people know about memory settings, JMX, class path etc.). But Tanuki does much more. It also provide a watchdog function, so that hanging IS instances are deal with automatically. It also collects all the output that (for whatever reason) not make it to the usual logs but STDOUT / ERROUT and write it into the "wrapper.log" so you have easy way to access and analyze the same. Last but not least Tanuki has the build in features for Windows / Linux to make processes auto-start on reboot as system services.
If you like to know more on TANUKI please see:
https://docs.webmethods.io/on-premises/webmethods-integration-server/en/11.1.0/webhelp/index.html#page/pie-webhelp/to-start_stop_server_26.html
or
https://wrapper.tanukisoftware.com/doc/english/integrate.html
To know more about IS Instances, please see:
https://docs.webmethods.io/on-premises/webmethods-integration-server/en/11.1.0/webhelp/index.html#page/pie-webhelp%2Fto-multi_IS_instances_8.html
Best regards,
Holm.
------------------------------
Holm Steinland
webmethods - New Product Introduction
IBM
Böblingen
Original Message:
Sent: Wed May 07, 2025 11:23 AM
From: kiran kumar
Subject: Starting IS from profiles folder vs Default folder
Hi Team,
What is the difference between starting IS from.
1. profiles/IS_default/bin/startup.sh/bat
and
2. IntegrationServer/default/bin/starup.sh/bat
3. When to start IS from profiles/IS_default/bin ?
4. When to start IS from IntegrationServer/deafult/bin directory?
Thanks,
Kiran
------------------------------
kiran kumar
------------------------------