Welcome Guest! Log in
×

Notice

The forum is in read only mode.
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

Topic-icon Question Designer overwrites embedded runtime scripts on every startup

More
03 Apr 2017 20:30 #1 by craigacgomez
Designer Version: S18.3.1_20170217_092932
Operating System: Linux x64

If I change any of the runtime scripts of the embedded runtime, for example initvariables.sh, the changes are overwritten with the packaged defaults the next time I start up the designer.

Steps:
1. Start up the designer. If this is the first time, the runtime directory (stambiaRuntime) is created and the runtime is extracted here
2. Exit the designer and modify one of the runtime scripts in the runtime directory. For example, edit initvariables.sh and change the value of STAMBIA_MAX_MEMORY to 2048m (default is 512m).
3. Start up the designer.
4. Open the initvariables.sh.

Expected:
The changes to initvariables.sh should remain

Actual:
initvariables.sh is reverted back to the default state (STAMBIA_MAX_MEMORY is reset to 512m)
More
04 Apr 2017 12:31 #2 by Thomas BLETON
Hi, thank you for your message.

The actual behavior is the intended one.
The Runtime provided inside the Designer is indeed re-initialized at each Designer startup. This provides a way to keep a "clean" Runtime somewhere for you to test.

Most often, users setup a Runtime out of the Designer folder (or some server), and they customize it at will.
That being said, as we know that some users prefer to work with their local Runtime-of-the-Designer, we provide a mechanism for preventing the reset. Please read this article for more information.