EASYProcess Installation Overview
What is EASYProcess?
EASYProcess is an Enterprise Application Development Platform which is used to develop all K-Rise solutions. Any solution created with EASYProcess is referred to as the Application. It is the tool with which complex web portal applications can be created. It allows for Rapid Application Development of JD Edwards custom projects by utilizing a No-Code approach.
Some of the already built K-Rise solutions are EASYCommerce (a B2B or B2C ecommerce site), EASYPay (a PCI compliant shopping cart and invoice payment portal), and Employee Self-Service (Employee and Manager self-service portal for HR purposes). All of these built applications were done so using the EASYProcess tool and thus could be easily edited to add additional features when necessary.
EASYProcess acts as the integration layer between the Enterprise Systems and the Users of the Application (created K-Rise solution). It accomplishes this with some additional systems and tools.
EASYProcess, EEM, and SCM
EASYProcess allows developers to build and edit all EASYProcess Applications that exist on the computer. However each application is directly tied to one website, so all changes made to the application would be made directly in the live site of the Application and would have undesirable downtime windows while development and testing occurred. For that reason, multiple instances or copies of the Application are set up. These separate instances of the same Application are called Environments.
Each environment is a complete copy of the web portal application, so having multiple environments means having multiple copies of the site created by EASYProcess. This allows changes to be made in one copy while the live site (the production environment) is still using the last stable version. Then, once the new features are developed, and tested, the copy from the changed version (in the development environment) is moved to override the live site’s version. This removes all the downtime and the live site can instantly move from the last stable version to the next stable version.
The system which is responsible for taking copies of the web portal application and moving them between the EASYProcess environments is called the Source Control Management (SCM). SCM links the environments in a way so that changes could be made in a development environment, tested in a testing environment, and promoted to the final production environment once all changes are approved. The path that changes go through is called the promotion path. The most common promotion path is development (DV), testing or quality assurance (QA), and production (PD).
Different environments can exist on the same server. If done like this, EASYProcess would open and the user would be asked which application they wanted to work on. However, in some cases, it is more desirable to separate the environments to different servers. If this is done, each server must have EASYProcess installed in order to open the environment that is placed on that server. With a setup like this, there are multiple copies of the Application as well as EASYProcess.
SCM is a way of linking the EASYProcess environments so that any given environment knows which is next is the promotion path. SCM is able to do this when the environments of the promotion path exist in one server or multiple. In order to view the different environments and have a user interface to move changes through the promotion path at the click of a button, another K-Rise tool is used: EASYProcess Enterprise Manager (EEM).
EEM allows developers to manage the different instances of EASYProcess. This is necessary when SCM is set up since multiple environments are required for SCM. Like SCM, EEM can view EASYProcess Applications across servers. However, EEM views all EASYProcess Applications that exist on the servers it is looking at and is not limited to seeing only Applications that are in a given promotion path. If for any reason, two EASYProcess Applications existed on the same machine and were not part of the same promotion path (not different environments of the same application), EEM would still be able to view them and their related promotion paths (if SCM were set up for both).
Since EEM is used to manage EASYProcess, EEM will also be used to upgrade EASYProcess to newer versions. Given the proper file which can be downloaded from the K-Rise website, EEM is able to change aspects of EASYProcess behind the scenes. Changing these components that run EASYProcess is purpose of an EASYProcess upgrade. The newer versions are changed to work more efficiently and create a better tool for future use.
How Does EASYProcess Work?
Each EASYProcess is in charge of all Applications that exist on the server where EASYProcess in installed. The Application is the K-Rise solution that EASYProcess builds. The name of this application can be different depending on the purpose of the K-Rise solution, or it can be predetermined by the product already contained in the EASYProcess copy that is installed. This is done if a particular pre-built solution is installed with EASYProcess such as EASYCommerce, EASYPay, Employee Self-Service, Vendor Self-Service, etc.
The name of the Application will change, but each application will also have a corresponding Base Application. The Application gives developers the EASYProcess tools they need to create their solution. The Base Application allows K-Rise to create tools that the developers will use. Base is responsible for running things that are behind the scenes and make EASYProcess possible as the developers will see it.
Each Application (Base and the Project Application) must have a corresponding Database. The Application Database (the Project) contains all of the data that defines what the project or application is and what it does. Any component designed and developed in EASYProcess for an application is stored here. This is the database that the developer will be accessing and using to create the application. Examples of this are the specific logic, webpages, or created users for the Application’s site.
The Base Database contains data that is essential to core EASYProcess functionality. All services used in a process to create that logic or fields used in a WebPart to create a webpage are defined in the Base Database. The Base database is used to define the tools that EASYProcess offers to developers in order to create the K-Rise solution.
Since EASYProcess stores all data necessary for running EASYProcess and defining the Application built in EASYProcess in a database, it needs to access that database in order to run. Each EASYProcess installation needs to be told where its corresponding database is and how to access it (SQL credentials). The Installation.config file is a static file for the purpose of defining the locations of the various files, services, and information that EASYProcess uses and communicates with. EASYProcess will search for C:\EASYProcess\EPInstallation.config to find the file and reference expected values within that file to know where to look for various necessary information.
The Installation.config file will also tell EASYProcess the filepath of EASYProcess Folder Structure which stores its important folders on both the Application Server and the Web Server. Both servers will have a folder structure to store important files related to EASYProcess, but their uses will differ.
The Application Server is where EASYProcess and EEM are installed. It is also where SCM is set up and where the Installation.config file is saved. The Application Server runs EASYProcess. Since this is where EASYProcess is running, the files necessary to run EASYProcess are also stored here in the Toolset folder. When an EASYProcess is upgraded, the files in the Toolset folder are updated with newer versions developed by K-Rise.
The Application Server will also have files related to the JDE Business Function (BSFN) Server and Solr within the EASYProcess folder structure. The JDE BSFN Server which picks up the BSFN requests made by the EASYProcess Application and calls JDE. It then receives the response and gives it to the process that made the request which can then be used to give that information back to the user on the site who requested it. Solr is a tool that is used for fast searches which can be incorporated into the built application, such as item catalog searches.
The Web Server will host the website for the Application. It does this with Microsoft Internet Information Services (IIS) which will be set up on the Web Server. IIS is responsible for receiving the requests when users browse the site and sending back the response. If your site will have an SSL certificate applied, it will be done so through IIS.
IIS will point the website to the EASYProcess Website folder in the EASYProcess folder structure to know the source of the site. The website folder contains essential image, style, and script files that are used in the site. It also contains necessary IIS files, some of which must be configured to your specific site i.e. web.config and global.asax.
The Web Server communicates with the Application Server by sending requests to the EASYProcess Enterprise Server (EES). The Enterprise server is a Windows Service set up on the Application Server. It listens on a designated port for the requests and runs the requested Processes/Web Parts/etc in EASYProcess. This allows EASYProcess to be used and have processes and workflows initiated from user interaction on the website. The Enterprise Server also runs batch jobs (stand alone processes that are not initiated by user interaction on a webpage and can be started on a schedule). Without the Enterprise Server running, EASYProcess will not be able to run.