What are the best approach and procedures to facilitate the modernization of web front-end development for new developers.

I asked AI  if I need a web server for our D3/LX64 backend and it came back with the following; 

Using a web server like NGINX can be beneficial in your setup with Rocket D3 MultiValue Database, a Node.js server, and a React frontend, but it's not strictly necessary. Here's a breakdown of how each component fits into your architecture:

Rocket D3 MultiValue Database: This will handle your data storage and retrieval. 
Node.js Server: This acts as the middle layer, handling API requests, business logic, and communication between your React frontend and Rocket D3 backend. Node.js is well-suited for this role due to its non-blocking, event-driven architecture.
React Frontend: This will be your user interface, providing a dynamic and responsive experience for users.
NGINX: While not mandatory, NGINX can serve multiple purposes:
Reverse Proxy: It can route incoming requests to your Node.js server, improving load balancing and security.
Static File Serving: It can efficiently serve static assets like HTML, CSS, and JavaScript files.
SSL Termination: It can handle SSL/TLS encryption, offloading this task from your Node.js server.

Using NGINX can enhance performance, security, and scalability of your application. However, if you're just starting out or working on a smaller project, you might manage without it initially and add it later as your needs grow.

We want to get away with Telnet and go with the html route,  how do you experts/guys do this? 

Thank you,

J

I asked AI  if I need a web server for our D3/LX64 backend and it came back with the following; 

Using a web server like NGINX can be beneficial in your setup with Rocket D3 MultiValue Database, a Node.js server, and a React frontend, but it's not strictly necessary. Here's a breakdown of how each component fits into your architecture:

Rocket D3 MultiValue Database: This will handle your data storage and retrieval. 
Node.js Server: This acts as the middle layer, handling API requests, business logic, and communication between your React frontend and Rocket D3 backend. Node.js is well-suited for this role due to its non-blocking, event-driven architecture.
React Frontend: This will be your user interface, providing a dynamic and responsive experience for users.
NGINX: While not mandatory, NGINX can serve multiple purposes:
Reverse Proxy: It can route incoming requests to your Node.js server, improving load balancing and security.
Static File Serving: It can efficiently serve static assets like HTML, CSS, and JavaScript files.
SSL Termination: It can handle SSL/TLS encryption, offloading this task from your Node.js server.

Using NGINX can enhance performance, security, and scalability of your application. However, if you're just starting out or working on a smaller project, you might manage without it initially and add it later as your needs grow.

We want to get away with Telnet and go with the html route,  how do you experts/guys do this? 

Thank you,

J

Well, if you're going to use Node.js as a backend, you still need to get data to/from D3.

https://d3demo.webbtide.com uses Angular for the client, nginx, Apache Tomcat, MVSP Java and D3/Linux.

You can replace Angular with whatever your preferred front end framework is. IMO, using Tomcat allows you to write your D3 interface code in Java and use the MVSP code to communicate with D3. MVSP seems to work well, and you can create a pool of connections at Tomcat startup so each web request doesn't canny the overhead of a login to D3.

For what it's worth, if your app is an internal LOB app, you might want to consider a Java Swing (or Java FX) desktop app. Would still use MVSP to talk to D3. If your clients are all Windows machines you could alternatively use whatever is Microsoft's current take on desktop UI development and use the C# version of MVSP. 

Well,  Impressed that an AI engine got rocket D3 correct!  Y

our question would actually have many answers and needs more detail on your goals to help answer the question.  Have you been involved with some of the Rocket Tutorials and conversations on this topic? 

 I can tell you that we are using MVConnect on D3  along with an apache web server for the infrastructure.  We develop on our CMS (Joomla) in PHP with all our current UI development being done in VUE.   We have moved all telnet connections to SSH and have managed to get all terminal logins to be from our AD server to facilitate a single login name/password.   We have been using the HTML and web for client applications for many, many (netscape 1.0) years and currently moving older HTML applications into VUE while slowly moving other terminal applications to the browser.

Let me know if you would like more details.

Based on  the tutorial https://www.youtube.com/watch?v=mSI5mXbCkkA

Can we use the new functions in Pick D3 Multivalue instead of JBase to enable our Pick applications to write data into MongoDB and use Vue or React as the frontend? Is this the first stage in modernizing our existing Pick database? I’m looking for a platform to present application data in a regular browser. Our plan is to completely redesign the interface, retiring the text-based ‘menu’ screens from Accuterm or Wyse50 TTY sessions. We will hire developers to work on the GUI. Thank you

------------------------------
Eric Estrella
IT Specialist
Self Registered
Glendale CA US
------------------------------

I asked AI  if I need a web server for our D3/LX64 backend and it came back with the following; 

Using a web server like NGINX can be beneficial in your setup with Rocket D3 MultiValue Database, a Node.js server, and a React frontend, but it's not strictly necessary. Here's a breakdown of how each component fits into your architecture:

Rocket D3 MultiValue Database: This will handle your data storage and retrieval. 
Node.js Server: This acts as the middle layer, handling API requests, business logic, and communication between your React frontend and Rocket D3 backend. Node.js is well-suited for this role due to its non-blocking, event-driven architecture.
React Frontend: This will be your user interface, providing a dynamic and responsive experience for users.
NGINX: While not mandatory, NGINX can serve multiple purposes:
Reverse Proxy: It can route incoming requests to your Node.js server, improving load balancing and security.
Static File Serving: It can efficiently serve static assets like HTML, CSS, and JavaScript files.
SSL Termination: It can handle SSL/TLS encryption, offloading this task from your Node.js server.

Using NGINX can enhance performance, security, and scalability of your application. However, if you're just starting out or working on a smaller project, you might manage without it initially and add it later as your needs grow.

We want to get away with Telnet and go with the html route,  how do you experts/guys do this? 

Thank you,

J

Eric,

Without knowing what your application or your business case are, "Best" is not a useful measure. However, D3 db to Mongo db to Web and back again seems like an inefficient way to proceed.

A common and "well-known" pattern is to use a REST service layer. This will allow you to create a service to integrate with your D3 application (perform CRUD operations, call basic programs, etc.) and integrate to a front-end server utilising a well-known pattern your new front-end developers should understand. 

Design patterns for modern web APIs | by David Luecke

Rocket has MV Integration Server but the D3 integration may not be available yet; check with Rocket. There are also several commercial REST offerings for D3 I'm aware of.

I asked AI  if I need a web server for our D3/LX64 backend and it came back with the following; 

Using a web server like NGINX can be beneficial in your setup with Rocket D3 MultiValue Database, a Node.js server, and a React frontend, but it's not strictly necessary. Here's a breakdown of how each component fits into your architecture:

Rocket D3 MultiValue Database: This will handle your data storage and retrieval. 
Node.js Server: This acts as the middle layer, handling API requests, business logic, and communication between your React frontend and Rocket D3 backend. Node.js is well-suited for this role due to its non-blocking, event-driven architecture.
React Frontend: This will be your user interface, providing a dynamic and responsive experience for users.
NGINX: While not mandatory, NGINX can serve multiple purposes:
Reverse Proxy: It can route incoming requests to your Node.js server, improving load balancing and security.
Static File Serving: It can efficiently serve static assets like HTML, CSS, and JavaScript files.
SSL Termination: It can handle SSL/TLS encryption, offloading this task from your Node.js server.

Using NGINX can enhance performance, security, and scalability of your application. However, if you're just starting out or working on a smaller project, you might manage without it initially and add it later as your needs grow.

We want to get away with Telnet and go with the html route,  how do you experts/guys do this? 

Thank you,

J

Hello Jose, this is Patrick with Rocket formerly with Zumasys.  MVConnect is our recommended solution to create rest EndPoints.  MVConnect is a platform neutral package that is now free.  It is a small Web Server and some libraries in MVBasic to create your end points.  It has a bunch of familiarity with FlashConnect which is a depreciated package.  It has a nice WOBJ package to assist in making and consuming jSON payloads.  MVConnect is built into jBASE and MVIS making your code more platform neutral.

MVConnect (rocketsoftware.com) -Docs Site

WOBJ (rocketsoftware.com) - WOBJ api to create objects.  Originally created for D3 since it has nothing built in - Note Python is now a option

Building a Web Interface for a MultiValue Application (youtube.com) - Old video showing a simple to do app

Note, that demo video (and there are more) uses a simple SPA app that looks like Visual Basic and is not intended to be your front but shows the concepts.

This video is done with jBASE and only shows the MVConnect style design pattern to create endpoints.  The coding side is identical for D3.

RESTful Services and Web APIs with Pick MultiValue (youtube.com)

Hello Jose, this is Patrick with Rocket formerly with Zumasys.  MVConnect is our recommended solution to create rest EndPoints.  MVConnect is a platform neutral package that is now free.  It is a small Web Server and some libraries in MVBasic to create your end points.  It has a bunch of familiarity with FlashConnect which is a depreciated package.  It has a nice WOBJ package to assist in making and consuming jSON payloads.  MVConnect is built into jBASE and MVIS making your code more platform neutral.

MVConnect (rocketsoftware.com) -Docs Site

WOBJ (rocketsoftware.com) - WOBJ api to create objects.  Originally created for D3 since it has nothing built in - Note Python is now a option

Building a Web Interface for a MultiValue Application (youtube.com) - Old video showing a simple to do app

Note, that demo video (and there are more) uses a simple SPA app that looks like Visual Basic and is not intended to be your front but shows the concepts.

This video is done with jBASE and only shows the MVConnect style design pattern to create endpoints.  The coding side is identical for D3.

RESTful Services and Web APIs with Pick MultiValue (youtube.com)

Hello Eric.

I work with QM and have made several complex browser-based applications. My work environment is QM + websvc + React. In QM and using the websvc command we implement an API with the JSON RPC format (https://www.jsonrpc.org/) since it is easier for us to implement directly in QM than a complete RESTful system. To handle https traffic and not directly access the web services provided by the QM websvc command we implement a reverse proxy with NGINX.

I hope it helps or inspires you.

Marcos Alonso
INGESCO Sistemas Informáticos, S.L.

Thank you for your suggestions, appreciate them. 

I assume you are referring to OpenQM, WebService, and React. We are in the early stages of product selection, and I want to set up a lab environment so that our developers, who have over 25 years of experience with D3 MultiValue, can easily learn OpenQM. I want them to adapt to modern web development using their knowledge of Pick Systems. We've been using Redhat since RHEL 4 and I think we will stay with Redhat. I am thinking of evaluating OpenQM and deploy it using Podman/Quadlet if it's doable and I am open to ideas!   Thanks again!

------------------------------
Eric Estrella
IT Specialist
Self Registered
Glendale CA US
------------------------------