Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved PowerServer_ConnectionConfig table

  1. Advice
0
Votes
Undo
  1. John Raghanti
    John Raghanti
  2. PowerServer
  3. Friday, 20 September 2024 14:41 PM UTC

Hi all! Running PB 2022 R3 build 3356.

I have a question about the PowerServer_ConnectionConfig table that is created for dynamic caching.

Is it possible to add columns in there for specific application usage? If so, how would we get the data from those columns into PowerBuilder?

For example, we have API servers associated with our client databases. We'd like to store the API server IP and port at the cache level, but we need to have access to that inside the application. That way if we need to change it, we only need to access the Cache information and that will filter down to all customers connecting to that cache entry.

Any thoughts? Thanks!

Local Kestrel server error cannot reach license se...
Cant verify license server starting today.
Responses (2)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 20 September 2024 14:47 PM UTC
  2. PowerServer
  3. # 1

Hi John;

  At this time (AFAIK), this table data is only handled (and thus available) to internal PS processing logic.

What you are describing though is an interesting idea. I would suggest opening up a support ticket as an enhancement request for this feature.

Regards .. Chris

Comment
John Raghanti
  1. John Raghanti
  2. Friday, 20 September 2024 16:20 PM UTC
Thanks! In the interim, we decided to put the information at the client database level and we'll have to create a UI for it. I wrote up a support ticket for this.
  1. Helpful
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Friday, 20 September 2024 16:26 PM UTC
  2. PowerServer
  3. # 2

we use a 2nd table (actually several to track a few things) in the same database that hosts those PowerServer_ConnectionConfig  tables.

that way we only have to create the table once and makes it easier to maintain it.  we use a 2ndary api to get that info.

 

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 20 September 2024 16:44 PM UTC
That's a great technique Mike!
  1. Helpful
John Raghanti
  1. John Raghanti
  2. Friday, 20 September 2024 18:01 PM UTC
Thanks Mike. I thought about that, but I didn't want to have to set up another manual SQL transaction object if I didn't have to. I assumed that we would be able to access the information from that table through the PowerServer entry points, but I guess it's all under the covers. Storing it individual client databases seems like the next best thing. It makes maintenance a little more difficult because the support technician will need to access their database directly rather than using the PowerServer Console to the Cache database.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.