Skip Headers
JD Edwards EnterpriseOne Tools Fundamentals Guide
Release 8.98 Update 4

Part Number E14712-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

6 Viewing EnterpriseOne Tools Architecture and Implementation Phases

This chapter contains the following topics:

This chapter provides overview information related to using JD Edwards EnterpriseOne Tools within a sample implementation framework.

Note:

The implementation phases in this framework are intended to help you gain a better understanding of JD Edwards EnterpriseOne Tools regarding how and when they may be used. The implementation phases in no way imply strict dependencies between phases. Every implementation is unique.

6.1 Understanding the Phases of Implementation

Although few implementations follow exactly the phases of a system development life cycle (SDLC) or implementation plan, the following implementation phases are provided as a framework through which you can gain an understanding of how specific JD Edwards EnterpriseOne Tools are intended to be used. This framework should be viewed as a high-level educational rather than a strict, implementation model.

Note:

Some JD Edwards EnterpriseOne Tools may be used in multiple phases of an implementation.

6.2 JD Edwards EnterpriseOne Architecture and Process Flow for Windows

These host server processes perform the indicated actions:

Figure 6-1 JD Edwards EnterpriseOne Architecture and Process Flow for Windows

Description of Figure 6-1 follows
Description of "Figure 6-1 JD Edwards EnterpriseOne Architecture and Process Flow for Windows"

All communications between the client and the host server occur using sockets. The communications between jdenet_n and jdenet_k occur with shared memory. jdenet_n and queue kernel communicate using the Job Control Status Master database table (F986110).

This text explains the process flow:

6.3 Using JD Edwards EnterpriseOne Tools within Implementation Phases

The following table describes the implementation phases.

Phase Description
Installation This phase covers the activities involved in installing the JD Edwards CDs and setting up your demonstration JD Edwards environment. A demonstration environment includes application servers, Process Scheduler servers, web servers, and a JD Edwards database.
Application Configuration This phase covers the activities involved in configuring the JD Edwards applications you have purchased to fit the business processes of your organization. This phase includes setting up security access, customizing pages, creating custom batch programs, and so on.
System Configuration This phase covers the activities involved in setting up and configuring the infrastructure that supports the deployment of your application configuration. For example, in this phase you would set up the servers, the security, and processes required to be in place for your end users to use the JD Edwards system to complete business transactions with a browser or other device.
Decision Support Configuration This phase covers the activities involved with setting up the reporting and decision support systems that decision makers will use to gather business information. This includes developing predefined queries and reports, setting up a system to generate reports at scheduled times, set up access to OLAP cubes, and so on.
Business Process Integration This phase covers the activities involved in setting up systems that enable your business processes to span multiple business areas, such as HR and Finance, within your organization. This phase includes setting up our XML-driven integration technology that enables disparate systems to exchange data seamlessly, and it also includes setting up JD Edwards Workflow to enable multiple users within a business process to easily route data and notifications to each other.
Maintenance This phase covers the activities that are involved in maintaining your JD Edwards system once you have rolled out the system to your end users. This phase includes monitoring system performance, upgrading to new releases, applying patches, and so on.