From customer:
The url mapping is the same structure as for yyy customers, so:
/lsm/rest = Production (xxx calls this LIV)
/lsmtst/rest = Test (xxx calls this TST)
/lsmnxt/rest = Next (xxx calls this TRN)
In xxx you can have multiple production databases. If a customer has a branch in America and a branch in Europe, they could create 2 production databases called LIVUSADB and LIVEURDB for example.
We need to configure the REST endpoint to write to a specific database. We tried solving this with adding a parameter to the BBxServlet configuration, but after reading the RestBridge.bbj code, we noticed that you could only use a specified set in these parameters and not add your own stuff. We would expect that the parameters you set there, would be transformed to STBL's that you can use in your BC's.
Is there a way to send globals to your BC without creating a seperate config file for each context configuration or BBx Servlet? That would be overkill for what we are trying to achieve. The only thing we need is to set the variable xxx_ENVIRONMENTID so that the BC knows which database to go to.
From customer:
The url mapping is the same structure as for yyy customers, so:
/lsm/rest = Production (xxx calls this LIV)
/lsmtst/rest = Test (xxx calls this TST)
/lsmnxt/rest = Next (xxx calls this TRN)
In xxx you can have multiple production databases. If a customer has a branch in America and a branch in Europe, they could create 2 production databases called LIVUSADB and LIVEURDB for example.
We need to configure the REST endpoint to write to a specific database. We tried solving this with adding a parameter to the BBxServlet configuration, but after reading the RestBridge.bbj code, we noticed that you could only use a specified set in these parameters and not add your own stuff. We would expect that the parameters you set there, would be transformed to STBL's that you can use in your BC's.
Is there a way to send globals to your BC without creating a seperate config file for each context configuration or BBx Servlet? That would be overkill for what we are trying to achieve. The only thing we need is to set the variable xxx_ENVIRONMENTID so that the BC knows which database to go to.