We would like to know where the "Server Base URL" variable is used in the Semarchy Global Configuration.
We encountered some synchronization errors in our production environment. After checking the PREPROD environment, we discovered that this variable was pointing to the production URL. By changing it to the correct link, the issue was resolved.
Could you please provide more details about this variable?
Thank you in advance.
BR,
Dounia BOUZOUBAA
Best Answer
A
Alexia SIMOND
said
9 days ago
Hello Dounia,
If the server base url update helped you solve synchronization issues, then it might mean that is has been involved in your integration process.
Because it sounds to me that if you had loads/batches that didn't pertain to this environment, they might have been brought from another environment through this faulty url.
This can be checked by analyzing the data related to those loads/batches inside your data location.
Another thing that comes to my mind, is that maybe the synchronization checks done by the solution is involving said server base url, but that I'd need to check more in-depth.
Please let me know if the first hypothesis led you to identify the culprit.
If not, we can transfer this forum post as a ticket, for me to help you check further the root cause of this behavior.
If I understand correctly you had an issue with your server base url which is now resolved after its update.
And so you'd like to know more about the impacts it could have had.
To begin with, I will preface by saying that this server base url is configured in the Configuration > Application Customization > Global Configuration module:
And that, as per stated in our documentation, "it is seeded when creating the repository and used in workflow notifications to provide links to the server".
That being said, the resulting variable :V_SERVER_BASE_URL can be found in many components.
I will list a few below, each with a link to our documentation. But please note, that as this variable is available at semql level, then it means that it can be found wherever semql is present in the tool, so pretty much everywhere.
Indeed, it is available in:
Any semql condition, so that the developer can create links inside forms or collections thanks to it.
Workflows to customize the legacy workflow notifications.
Of course, the list is not exhaustive as it can be found anywhere semql related.
Did you have concerns on a specific functionality that might have been impacted by it?
Please let me know if I can clarify anything else.
Have a good day.
Alexia
D
Dounia BOUZOUBAA
said
9 days ago
Hello Alexia,
Thank you so much for your answer.
If I understand correctly, this variable can be used in multiple components of the application, which I believe explains why it caused synchronization errors when it was pointing to the wrong environment.
We haven’t yet found where it is used specifically, but as I mentioned before, all the synchronization errors disappeared once it was corrected.
Again, thank you so much, and I’ll let you know if we find anything related to this subject.
Have a great day!
Best regards, Dounia
A
Alexia SIMOND
said
9 days ago
Answer
Hello Dounia,
If the server base url update helped you solve synchronization issues, then it might mean that is has been involved in your integration process.
Because it sounds to me that if you had loads/batches that didn't pertain to this environment, they might have been brought from another environment through this faulty url.
This can be checked by analyzing the data related to those loads/batches inside your data location.
Another thing that comes to my mind, is that maybe the synchronization checks done by the solution is involving said server base url, but that I'd need to check more in-depth.
Please let me know if the first hypothesis led you to identify the culprit.
If not, we can transfer this forum post as a ticket, for me to help you check further the root cause of this behavior.
Thank you and have a good evening.
Alexia
D
Dounia BOUZOUBAA
said
7 days ago
Hello Alexia,
Thank you for these leads!
Indeed, we have some API integration that might be using this URL. We’ll check the data and see if this is the cause.
I’ll keep you updated on what I find. If needed, I’ll reach out to convert this into a ticket.
Thanks again, and have a great day!
Best regards, Dounia
A
Alexia SIMOND
said
7 days ago
Hello Dounia,
My pleasure. Good luck with your investigations.
Don't hesitate to reach out via ticket if needed, we'll be glad to help further.
Dounia BOUZOUBAA
Hello,
We would like to know where the "Server Base URL" variable is used in the Semarchy Global Configuration.
We encountered some synchronization errors in our production environment. After checking the PREPROD environment, we discovered that this variable was pointing to the production URL. By changing it to the correct link, the issue was resolved.
Could you please provide more details about this variable?
Thank you in advance.
BR,
Dounia BOUZOUBAA
Hello Dounia,
If the server base url update helped you solve synchronization issues, then it might mean that is has been involved in your integration process.
Because it sounds to me that if you had loads/batches that didn't pertain to this environment, they might have been brought from another environment through this faulty url.
This can be checked by analyzing the data related to those loads/batches inside your data location.
Another thing that comes to my mind, is that maybe the synchronization checks done by the solution is involving said server base url, but that I'd need to check more in-depth.
Please let me know if the first hypothesis led you to identify the culprit.
If not, we can transfer this forum post as a ticket, for me to help you check further the root cause of this behavior.
Thank you and have a good evening.
Alexia
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstAlexia SIMOND
Hello Dounia,
Thank you for contacting us.
If I understand correctly you had an issue with your server base url which is now resolved after its update.
And so you'd like to know more about the impacts it could have had.
To begin with, I will preface by saying that this server base url is configured in the Configuration > Application Customization > Global Configuration module:
That being said, the resulting variable :V_SERVER_BASE_URL can be found in many components.
I will list a few below, each with a link to our documentation. But please note, that as this variable is available at semql level, then it means that it can be found wherever semql is present in the tool, so pretty much everywhere.
Indeed, it is available in:
Of course, the list is not exhaustive as it can be found anywhere semql related.
Did you have concerns on a specific functionality that might have been impacted by it?
Please let me know if I can clarify anything else.
Have a good day.
Alexia
Dounia BOUZOUBAA
Hello Alexia,
Thank you so much for your answer.
If I understand correctly, this variable can be used in multiple components of the application, which I believe explains why it caused synchronization errors when it was pointing to the wrong environment.
We haven’t yet found where it is used specifically, but as I mentioned before, all the synchronization errors disappeared once it was corrected.
Again, thank you so much, and I’ll let you know if we find anything related to this subject.
Have a great day!
Best regards,
Dounia
Alexia SIMOND
Hello Dounia,
If the server base url update helped you solve synchronization issues, then it might mean that is has been involved in your integration process.
Because it sounds to me that if you had loads/batches that didn't pertain to this environment, they might have been brought from another environment through this faulty url.
This can be checked by analyzing the data related to those loads/batches inside your data location.
Another thing that comes to my mind, is that maybe the synchronization checks done by the solution is involving said server base url, but that I'd need to check more in-depth.
Please let me know if the first hypothesis led you to identify the culprit.
If not, we can transfer this forum post as a ticket, for me to help you check further the root cause of this behavior.
Thank you and have a good evening.
Alexia
Dounia BOUZOUBAA
Hello Alexia,
Thank you for these leads!
Indeed, we have some API integration that might be using this URL. We’ll check the data and see if this is the cause.
I’ll keep you updated on what I find. If needed, I’ll reach out to convert this into a ticket.
Thanks again, and have a great day!
Best regards,
Dounia
Alexia SIMOND
Hello Dounia,
My pleasure. Good luck with your investigations.
Don't hesitate to reach out via ticket if needed, we'll be glad to help further.
Thank you and have a good weekend.
Alexia
1 person likes this
-
Deployment History Date
-
Username in Tomcat Access Logs
-
Is It Possible to Perform Automatic Authentication with The User's Windows Account?
-
Where is the documentation for Version 5.2.5?
-
On Prem Semarchy Authentication using Azure AD?
-
Delete old models
-
Sync production model version with dev
-
Recreate a dev environment. Any side effect?
-
Indexes on xDM database tables
-
What logging technology is used in the Semarchy xDM platform?
See all 69 topics