• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerServer
  • Database connection required before adding to the list of available in PS

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

Resolved Database connection required before adding to the list of available in PS

  1. Advice
0
Votes
Undo
  1. damian jimenez
    damian jimenez
  2. PowerServer
  3. Friday, 27 September 2024 12:33 PM UTC

I didn't know whether to classify it as advice or just a question.

In a dockerized schema, I don't have access to the database from the Powerbuilder IDE. Then I can add the connection data (which I will have once the reverse proxy is mounted in Nginx).

I only have to manually edit the file Applications.json then mount the image in the container to achieve connectivity.

It would be good if the IDE allowed connections to be added without effectively testing connectivity at that time before add it to the list of Database connection

Thanks a lot

PowerServer - Read/Save to Azure Storage file
Internal Error Loading the SSL libraries
Responses (2)
damian jimenez
damian jimenez Accepted Answer Pending Moderation
  1. Monday, 30 September 2024 14:39 PM UTC
  2. PowerServer
  3. # 1

We are in a process of testing
during the development process from the IDE we connect to a database (local or remote) perfectly.

In a containerized scheme
, by a security scheme, the database is only accessible from the PowerServer application (which is in another service not containerized)

So on each build, I need to edit the JSON to add that database server. since from the IDE I cannot add it because from the IDE I do not have an effective connection to that server

Both databases are identical

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 30 September 2024 15:20 PM UTC
I still don't understand what's the problem. You add one dev or test database you have access to in the IDE so the compile can be performed correctly. Then as you move the compiled app from one environment to another you modify the environment-specific settings in the .JSON files. That's why we pulled those values out into the .JSON files so they can be modified.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 27 September 2024 14:32 PM UTC
  2. PowerServer
  3. # 2

Not sure if I'm understanding correctly what you are doing, but two key points to make you aware of:

1. The PowerBuilder IDE itself is not designed or intended to be run in Docker.  The PowerServer compiled app that the IDE produces is cloud-native architecture so the app you develop can be containerized.

2. The PowerBuilder IDE must be able to connect to a database to correctly generate the SQL.  If you somehow bypass this step the compiled app generated by PowerBuilder IDE will have SQL errors some times.

Comment
Load more comments
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 30 September 2024 17:01 PM UTC
Oh I think I now understand now what you mean. So you want to have a visual way to create the .JSON values rather than use text editor?
  1. Helpful
damian jimenez
  1. damian jimenez
  2. Friday, 4 October 2024 03:19 AM UTC
1. I liked the idea that the entire application could be governed from the powerserver tab, wherever it is published.



In Docker, this would not be the case, I need a nano or vim editor to enter that IP, after mounting the container, restart the container and then start the application.



2. Automating the deployment of the application would be a little more difficult.

In our case, we have the same application for many clients, and in turn each client can have different work environments.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 4 October 2024 13:24 PM UTC
Thanks for this additional detail to explain the challenges. We'll pass this on to the product manager.
  1. Helpful 1
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.