Friday, August 26, 2022

ERP Architecture - Discovery Process

A thought process seeded into my head by a senior colleague of mine who has actually been a very good mentor for me. The idea is basically to collect as much information about the Customers Application Farm to remove a dependency on a personnal.
To start with, am jotting down the very basic requirements by taking into consideration the ERP architecture for Oracle EnterpriseOne (a.k.a JD Edwards) . 

Type Info
Server Manager  
Deployment Server Instances/Pathcodes
OS Version - CPU/Mmmry/HDD
Database Server Type of DB
Database Version
RAC/Single Node
OS Version - CPU/Mmry/HDD
Data Size and Growth per year
DB Objects
Number of DB Servers / Pathcodes per Server
OS Version - CPU/Mmmry/HDD
Enterprise Server Number of Servers / Pathcode
OS Version - CPU/Mmry/HDD
HTML/JAS Server
BSSV  Server
AIS Server
RTE Server
OVR
ADF
JDE Orchestrator 
Number of Servers / Pathcode
OS Version - CPU/Mmry/HDD
Weblogic Version
LoadBalancers  Type of LB
Listener Port
Oracle EnterpriseOne  Application  Version
Tools Version
Tools Bitness (32/64)
Standard and Custom Environments and assosiated Pathcodes
Concurrent User Information
Count of Prod Packages per week
Activity Rules
Customizations and Custom OCM/objects
Batch Server No: of  UBEs per day
Batch Queue Information
ESU/ASU/Planner/Updates
21CFR
LDAP/SSO
3rd Party Integrations Vertex
DSI
Other Apps
DR and Replication Details DataGuard/MIMCS/Always ON

No comments:

Post a Comment

ZDM Configuration

1) ZDM Svr Details  -- Requires one Server per tenancy -- Provision a New Server  -- Create the pub and pvt keys for login         -...