You are responsible for the cost of the AWS services used while running this Quick Start reference deployment.
This can be used to roll out new versions of the application, and the database configuration can use OpenEdge replication sets to provide redundancy. The web server and PAS for OpenEdge dynamically download and install the latest package when Amazon Elastic Compute Cloud (Amazon EC2) creates instances. You can package your on-premises application using this approach to deploy it to the AWS Cloud. The template contains user-provided deployment packages for the web server, Progress Application Server (PAS) for OpenEdge, and OpenEdge database so that the components are ready to run when the infrastructure is created. Use the AWS CloudFormation template to create new infrastructure, or use the AWS Command Line Interface (AWS CLI) to automate deployments of OpenEdge applications from a continuous integration and continuous deployment (CI/CD) pipeline.
It combines AWS services and OpenEdge functionality to achieve high availability, redundancy, and scalability. Upon installing, I am looking int he installation log and every single component appears to install successfully though.OpenEdge is a convenient way to create the infrastructure required to run an n-tier OpenEdge Advanced Business Language (ABL) application with a web user interface (UI), representational state transfer (REST) data services, and the OpenEdge database. Bronco has in his github page here but he has done some stuff for Suse Linux, and I am exclusively interested in Windows. I have had a look over the dockerfile and response.ini that Mr. NOTE: I have a host machine with Windows and the container in which I'm trying to install OpenEdge 11.7.2 has Windows Core in it as well. I believe the issue may have something to do with Java paths, but I'm not sure. When using proadsv -query or proadsv -start or proadsv -stop inside the container, I receive the standard 'OpenEdge Release + ' message yet nothing more. However, I cannot find a way to make 11.7.2 32bit working, and it's getting quite frustrating. I have successfully managed to install Progress OpenEdge 11.6 32bit, 11.7 32bit and 11.7.1 32bit inside a Docker container, using the response.ini file.
0 kommentar(er)
