When we start Semarchy xDI designer, there is a long freeze because designer load all information about differents runtimes (it make a refresh of every runtimes). Is-it possible to disable this automatic refresh ?
Thanks
Best Answer
B
Benjamin Millet
said
9 months ago
Hello Audric,
Just to confirm that if we use the runtime metadata and not a conf.ecg (file used with Stambia) we haven't an automatic refresh of the runtimes when we open Semarchy xDI Designer and we haven't duplication of the runtime when we modified them.
If we open the navigator view, there is an automatic refresh. It could be better if you add a parameter to refresh automatically or not the runtimes. This refresh is longer than Analytics refresh (it was already the case with Stambia).
Please update documentation to indicate it's necessary to create a runtime metadata file because if you have an old conf.ecg file, you will have some bug and maybe automatically convert conf.ecg file to runtime metadata during upgrade model from Stambia S19 to Semarchy xDI.
What do you mean about long freeze because the designer loads all the information about different runtimes ?
Can you illustrate it with some screens? And give us more details?
B
Benjamin Millet
said
9 months ago
Answer
Hello Audric,
Just to confirm that if we use the runtime metadata and not a conf.ecg (file used with Stambia) we haven't an automatic refresh of the runtimes when we open Semarchy xDI Designer and we haven't duplication of the runtime when we modified them.
If we open the navigator view, there is an automatic refresh. It could be better if you add a parameter to refresh automatically or not the runtimes. This refresh is longer than Analytics refresh (it was already the case with Stambia).
Please update documentation to indicate it's necessary to create a runtime metadata file because if you have an old conf.ecg file, you will have some bug and maybe automatically convert conf.ecg file to runtime metadata during upgrade model from Stambia S19 to Semarchy xDI.
Best regards
A
Audric FREY
said
9 months ago
Hello Benjamin,
A new ticket for a documentation enhancement has been created about this topic.
Benjamin Millet
Hello,
When we start Semarchy xDI designer, there is a long freeze because designer load all information about differents runtimes (it make a refresh of every runtimes). Is-it possible to disable this automatic refresh ?
Thanks
Hello Audric,
Just to confirm that if we use the runtime metadata and not a conf.ecg (file used with Stambia) we haven't an automatic refresh of the runtimes when we open Semarchy xDI Designer and we haven't duplication of the runtime when we modified them.
If we open the navigator view, there is an automatic refresh. It could be better if you add a parameter to refresh automatically or not the runtimes. This refresh is longer than Analytics refresh (it was already the case with Stambia).
Please update documentation to indicate it's necessary to create a runtime metadata file because if you have an old conf.ecg file, you will have some bug and maybe automatically convert conf.ecg file to runtime metadata during upgrade model from Stambia S19 to Semarchy xDI.
Best regards
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstAudric FREY
Hello,
What do you mean about long freeze because the designer loads all the information about different runtimes ?
Can you illustrate it with some screens? And give us more details?
Benjamin Millet
Hello Audric,
Just to confirm that if we use the runtime metadata and not a conf.ecg (file used with Stambia) we haven't an automatic refresh of the runtimes when we open Semarchy xDI Designer and we haven't duplication of the runtime when we modified them.
If we open the navigator view, there is an automatic refresh. It could be better if you add a parameter to refresh automatically or not the runtimes. This refresh is longer than Analytics refresh (it was already the case with Stambia).
Please update documentation to indicate it's necessary to create a runtime metadata file because if you have an old conf.ecg file, you will have some bug and maybe automatically convert conf.ecg file to runtime metadata during upgrade model from Stambia S19 to Semarchy xDI.
Best regards
Audric FREY
Hello Benjamin,
A new ticket for a documentation enhancement has been created about this topic.
Thank you for your feedback
-
File external resolver with encrypted value
-
Timeout on Mapping/Webservice call
-
UNIQUE TEMP TABLE NAMES
-
Previous step name from a sub-process of execute delivery
-
Dropping multiple tables at once in XDI
-
Freeze Designer and corrupted workspace
-
FileWait/Move/Copy: FileInclude with space
-
Loop excel files
-
Change SVN user in the Designer
-
How to Specify the JVM used by the Designer?
See all 64 topics