RTS - MetCreatives Cacoon Theme Questionnaire.pdf · general information about your JD Edwards...

RTS

Sizing Questionnaire

for

Oracle JD Edwards

EnterpriseOne

723 S. Casino Center Blvd . 2nd Floor Las Vegas, NV 89101 VOice: (702) 387-5387

www.realtimeltc.corn

,e RTS Table of Contents

Introduction 4

Do you have the right Questionnaire for your Sizing? 5 Where to return the completed Questionnaire , , .

Contact Information 6

Profiles for Application, System, and Infrastructure 7

Identify Infrastructure Profile . ERP Implementation .

Sizing Inputs .

Section 1: User Counts and Transactions .. Section 2: General system and sizing guest ions 14 Section 3: Collaborative Portal "" ", , .

Appendix A - Explanations and Terminology .

EDI , , , . MuItipIe Instances of EnterpriseOne ,, ' , . FAStT 22 ESS . High Availability .

Appendix B ERP sizing scenarios 24

Appendix C Collaborative Portal sizing scenarios 26

723 S. Casino Center Blvd . 2nd Floor Las Vegas, NV 89101 Voice: (702) 387-5387

www.realtrmellc.corn

,e RTS

Introduction

Thank you for requesting a sizing estimate for your REAL-TIME SYSTEMS JD Edwards EnterpriseOne implementation . The information you provide in this document will allow REAL-TIME SYSTEMS to develop a sizing recommendation which describes the REAL-TIME SYSTEMS server and disk resources required to support your planned JD Edwards EnterpriseOne installation.

It is recommended that several resources be used to complete this questionnaire (your organization's business experts, consultants, , etc.) to obtain valid inputs .

What is a Sizing?

A sizing is an approximation of the hardware resources required to support a specific software implementation. The purpose of this questionnaire is to collect information to estimate the REALTIME SYSTEMS hardware requirements for the implementation of JD Edwards EnterpriseOne on IBM System i, System x, or System p environments.

It is important to understand that "sizing " the hardware for each customer's JD Edwards EnterpriseOne applications implementation is an iterative process, which may be refined and repeated a number of times. If you are in the early stages of planning, you will probably have limited information about your planned environment. In this case, we can complete the sizing estimate with general information about your JD Edwards EnterpriseOne applications users. When you are further along in your implementation planning, you will know more about JD Edwards EnterpriseOne applications, the modules you plan to use, the number of users and your potential transaction activity. At that time, you may request another sizing estimate based on more detailed information. In any case , after receiving the results of a sizing estimate, you may choose to revise your input and request a re-sizing. At the SOlutions Sizing Center, we will be happy to work with you throughout this process.

This questionnaire, when completed , will return to you a sizing estimation including a workload from a provider other than REAL-TIME SYSTEMS. REAL-TIME SYSTEMS is not responsible for the accuracy of the data contained in such a workload, Any reliance by you on the third party workload is at your sole risk and will not create any liability or obligation for REAL-TIME SYSTEMS. If you have any questions or are unsatisfied with the third party workload information, you should contact the third party provider.

The system resources quoted to you in any sizing related communications are sufficient only for the workload(s) estimated. Other factors may require additional resources (e.g . additional non-estimated workloads, minimum configurations for RAID, allowance for growth, workspace, etc).

The information provided to you in any sizing related communications are provided by Real-Time Systems Corporation (REAL-TIME SYSTEMS) as a service to you and may be used for informational purposes only. Use of any siZing related communications is restricted to the purpose of helping you predict a possible (8M eServer model processor, memory and disk resources for a given workload .

Vorce: (702) 387 -5387

www.realttrnellc.corn

723 S. Casino Center Blvd. 2nd Floor Las Vegas, NV 89101

RTS

All representations of processor utilization, throughput, response time, memory , disk, and other performance data in the sizing communications are estimates and averages based on certain assumptions and conditions. No representation is made that these throughputs and their corresponding response times or other performance data will be accurate or achieved in any given IBM eServer installation environment. They are based on specific configurations and run time environments. Customer results will vary . Any configuration recommended by the sizing information communicated should be tested and verified . By accepting this information or using the sizing details you agree to the terms and conditions contained herein. If you do not agree with such terms and conditions, please do not review or use the provided materials and return the materials to REALTIME SYSTEMS.

Do you have the right Questionnaire for your Sizing?

The sizing questionnaires are updated frequently. Before taking the time to complete it, make sure you have the most recent version. The current version of the questionnaire can be obtained from your REAL-TIME SYSTEMS Representative or by visiting the REAL-TIME SYSTEMS Solutions Sizing website at http://www.ibm.com/erp/sizing

This questionnaire (JD Edwards EnterpriseOne New Sizing Questionnaire) is for customers implementing the JD Edwards EnterpriseOne application for the first time .

Customers planning an upgrade or migration or consolidation should use the JD Edwards EnterpriseOne Upgrade Sizing Questionnaire.

723 S. Casino Center Blvd . 2nd Floor Las Vegas, NV 89101 VOice: (702) 387 -5387

www.reainrnenc.corn

RTS

Contact Information

Client

Company Name:

Street Address

City, State Zip

Country -

Contact Name

Phone Number

E-mail Address

Industry

Short Business Description

REAL-TIME SYSTEMS

REAL-TIME SYSTEMS Client Rep,

Phone Number

E-mail Address

REAL-TIME SYSTEMS Specialist

Phone Number

E-mail Address

Business Partner

Business Partner Company Name,

Contact Name

Phone Number

E-mail Address

Contact Name

Phone Number

E-mail Address

Voice: (702) 387-5387

www.realtirnellc.corn


RT

Profiles for Application, System, and Infrastructure

Identify Infrastructure Profile

ERP Implementation

I. Architecture

A. Select database server platform (mark with an "X")

Option Select One System i with i50S/OB2 UDB database System x with DB2 UDB database (Linux) System x with 082 UDB database (Windows) System x with SOL Server database (W indows) System x with Oracle database (Windows) System x with Oracle database (Linux)

AIX5.2-AIX5.3 AIX5.2AIX5.3

System p with DB2 UOB database

System p with Oracle database

* Sizing requests that involve more than one platform or more than one scenario may take more time to complete.

B. If sizings for other platforms are being submitted on separate documents, please indicate which additional platforms have been submitted

ISystem i System p System x

C. Select location of Business Function logic

The default REAL-TIME SYSTEMS sizing algorithm assumes that the business application logic will run on the database server in a virtual 3-tier configuration , (unless there are "full" clients, which run the business application logic locally). If you require a separate application server for the business logic, please specify the required platform (System i, System p, System x):

Select one of the tollow ino options Select One Business l.oqic runninq on the database server, combined server Business Logic running on a separate , dedicated server

Platform for separate application server: System i__ System p__ System x__

723 S. Casino Center Blvd. 2nd Floor Las Vegas, NV 89101 VOice: (702) 387 -5387

www.realtimelle.com

RTS D. Select location of Batch processing

The default REAL-TIME SYSTEMS sizing algorithm assumes that the batch workload will run on the database server. If you require a separate server for batch processing , please specify the required platform (System i, System p, System x):

Select one of the following options Select One

Batch running on the database server. combined server

Batch running on the applicat ion (Business Function) server

Batch running on a separate , dedicated server

Platform for separate Batch server: iSeries System i__ System p__ System x__

* Typical EnterpriseOne ERP implementations run most batch processing on the database server.

E. Select location of Java Application Server, (WebSphere server or Oracle Application Server) for Web clients (HTML) (mark only one with an "X" )

Select one of the following options for HTML users Select One

Java Application Server running on the database server, combined server

Java Applicallon Server running on the application (Business Function) Server

Java Application Server on a separate, dedicated server

The default REAL-TIME SYSTEMS sizing algorithm assumes that the Java Application server workload will run on a separate server from the Enterprise server. Please specify the required platform for webserving (System i, System p, System x):

Platform for separate Java Application Server: System i__ System p__ System x__

VOice: (702) 387-5387

www .realtimetle.com

723 S. Casino Center Blvd. 2nd Floor LAs Vegas, NV 89101

,e RTS F. Select location of HTTP Server

The default REAL-TIME SYSTEMS sizing places HTTP server on the same box as Java Application Server above . This approach is recommended for implementations using internal or intranet access only. If external/Internet access is planned , a separate box separated by a firewall is recommended. Please specify the configuration choice and platform for the HTIP server (System i, System p, System x):

Select one of the following configuration options Select One

HTTP server running on the same box as the Java Application Server

HTTP server running on a separate, dedicated box

HTTP server running on another box, combined with other workloads Other workloads:

Platform for HTIP server : System i__ System p__ System x__

An estimate of the disk space required to support the JD Edwards EnterpriseOne applications will be based on the number of users defined in your workload estimate. This will be a very rough estimate, as the d isk space required does not always correlate with the number of active users

723 S. CaSH10 Center Blvd. 2nd Floor Las Vegas, NV 89101 VOice: (702) 387-5387

www.realtrrneltc.corn

,e RTS

Sizing Inputs

Section 1: User Counts and Transactions

User Counts

Please complete this information as accurately as possible. Be sure not to double count users. Classify users in the application where they spend a majority of their time each day. We are trying to size the servers for a peak hour of a day when the most users are online and actively working.

Active users : users are judged to be active if they are clicking the "OK" button or using Fn keys 2 to 3 times a minute. Users that are signed on, but are not actually using the system should not be counted. For this sizing, the number of users reported should be the total number of active users during a peak period.

Note: If concurrent active user counts are not known, a default of 65% of total users should be considered a conservative, reasonable estimate for concurrent active users for most applications. However, some applications, such as Employee Self Service may have much lower concurrency . The default concurrency for Employee Self Service is 10% of total users are considered active. Please consider your planned application usage when filling in the active user tables below.

"Full" clients : Full clients are those that have the business application logle running locally on the client. Full clients are no longer supported in EnterpriseOne version 8.11 and beyond.

"Mapped" clients: Mapped clients are those that have some or all of the business application logic mapped to the enterprise server or some machine other than locally. Mapped clients are no longer supported in EnterpriseOne version 8.11 and beyond

WTS/Citrix clients: Those clients which are connected via Windows Terminal Server or Citrix. WTS/Citrix clients are no longer supported in EnterpriseOne version 8.11 and beyond

Web clients : Those clients which use a browser interface to connect to the ERP application.

Note: Full clients are not recommended over a Wide Area Network due to bandwidth req uirements.

WorldfWorldVision Active Users: indicates the maximum number of active users of World or WorldVision software. Use the same definition for active user as above.

723 S. Casino Center Blvd. 2nd Floor las Vegas, NV 89101 VOLce : (702) 387-5387

www.realtrrnellc.com

RTS A. Define ALL EnterpriseOne active users during a peak processing period:

Active Users Application Full

Client (not

supported for 8.11

and beyond)

"Mapped" Client (not

supported for 8.11

and beyond)

WTS/ Citrix (not

supporte dfor 8.11

and beyond)

Web Client

Financials Distribulion* I I Manufacturing Advanced Pricing** Advanced Transportation Employee Self Service Human Resources Property Management Customer Relationship Management Total I

*Oivide Distribution users between those that will use Advanced Pricing (if any) and those that will not.

B. **Only limited benchmarking information is available for the Advanced Pricing application. To provide a reasonable pre-sales estimate of the resources required for Advanced Pricing, the users are factored at double the resources for a standard distribution user. The resources actually used by the application will vary based on the complexity of the rules and options of the implementation. The details of the implementation and any special considerations should be discussed with an Oracle JD Edwards EnterpriseOne analyst.

Voice: (702) 387-5387

www.realtimellc.com

723 S. ces.no Center BlVd. 2nd Floor Las Vegas, NV 89101

RTS

c. Transaction Information (Sales orders/Distribution only)

The standard scripts used to perform the sizing tests and benchmarks process transactions at a high rate. A typical user may not process transactions at the same rate. To assist in accurately accounting for users, please provide transaction rates below. The information required is transaction lines per hour during a peak period. If your peak period is not known then we will account for the peak by taking twice the average.

For exam pie: If a company processes 100,000 sales orders per month, with an average of 5 lines per order. Given a 20 workday month and a 10 hour work day, we would use 100,000 orders x5 lines per order /20 days /10 hours per day = 2500 lines per hour average. To size for a peak period, we would assume twice the average or 5000 lines per hour.

The transaction information is only used as a comparative check. It is not used to calculate any resource requirements. The sales order transactions are converted to equivalent standard distribution users, and this number is compared to the active distribution users listed in the user section. This comparison provides validation of the user counts listed. If the variation between the user counts listed and the equivalent users is significant, then the user counts may need to be revisited.

Currently Sales Orders are the only transaction type for which detailed data is available. Other transaction types may be added in the future.

Peak Sales Orders per hour: Average Lines per sales Order:

Note : Only transactions entered by users should be included. Transactions entered via EDI will be accoun ted for below.

EDI:

Will your environment be receiving and/or sending transactions through EDI?

Yes/No

Approximate peak lines per hour to be processed in each time frame*

Day Night

"It is assumed that daytime EDI transactions are processed while users are active and nighttime transactions are processed during a time when user activity is very Jaw.

723 S. Casino Center Blvd. 2nd Floor Las Vegas, NV 89101 VOice: (702) 387-5387

www.realtimellc.ccrn

,e RTS D. Batch production environment:

REAL-TIME SYSTEMS uses two different methods to provide a pre-sales estimate of the amount of resources required for batch jobs related to JD Edwards EnterpriseOne; allocating a specific amount of resources based on the user workload and the expected level (low, medium, high) of batch workload and also a processor allocation based on the number of concurrent batch jobs that may be run.

To assist in estimating expected batch workload, please provide an estimate of the expected level of batch; low, medium or high.

• A business that does very little batch work while users are active and has very few interl'aces to external systems would likely be considered a low batch environment.

• An environment with larger amounts of EDI, or interfaces to other systems, or long running processes such as Payroll or MRP may be considered a medium batch environment.

• An implementation with rnultlpte interfaces, very high volumes of EDI, or multiple long running processes , or those using mUltiple advanced applications such as Advanced transportation. Advanced warehousing or other batch intensive applications would be considered high batch environments.

1. Expected Level of batch

What level of batch activity do you expect for your environment? High, Medium, Low (default is medium)

Most batch jobs are processor intensive and single threaded. They will use a relatively high percentage of a single processor. Tests have shown that a single processor can support a typical user workload as well as batch processes, but as multiple concurrent batch streams are run, at some point the multiple batch streams are competing for limited resources and will slow down and take longer to run. Because of this degradation , in some environments it may be important to limit the number of batch processes that run concurrently on a per processor basis.

A standard REAL-TIME SYSTEMS sizing accounts for a significant batch workload by allocating resources based on the level of batch workload . This standard allocation should fit most environments. In certain cases , there are mission critical batch processes that need to be processed at the highest priority. The default assumption , if no input IS provided to this question is that capacity for typical batch jobs to execute is reserved, based on the user counts , but there are no critical batch processes that must be accounted for individually. Care should be taken when answering this question since only a limited number of processes will be permitted per processor. This could lead to a larger number of processors than would normally be required to handle the user workload .

Typical high priority batch jobs are high volume interfaces , high EDl volumes at times when users are also active or other long running, processor intensive batch jobs that will be run during times of high user activity.

723 S. Casino Center Blvd . 2nd Floor Las Vegas, NV 89101 VOIce : (702) 387-5387

www.realttmellc.com

--

,e RTS 2. Number of concurrent batch jobs (optional)

This information is optional and should only be given if detailed information about the production batch environment is known in advance. If no response to this question is given, batch processes will be sized based on the standard allocation and the response to the expected batch level above.

Please provide an estimate of the number of concurrent high priority batch jobs that will be run dUring times when users are also active on the system.

Section 2: General system and sizing questions A. Additional information for production environment

Are you currently running OneWorld, ERP 8.0, OneWorld/ERP 8.0 _(yIn)EnterpriseOne or World in production?

EnterpnseOne 8,9 _ (yIn)

World _ (yIn)

What hardware do you have now? Specify model number, processors, memory and disk .

Is this sizing for an upgrade to current hardware or for a new box?

Date for start of production

Growth in users projected one year after start of production (%)?

Preferred Server CPU Utilization The defau lt maximum CPU utilizat ion for a standard REAL-TIME SYSTEMS sizing depends on the type of server being sized and varies between 65% and 75%. If another utilization number is preferred, to allow for more growth or headroom for peak workloads, please specify the percentage here ,

Are Multiple Instances requ ired? If yes, how many? YeslNo # of instances Note: Multiple Instances refers to multiple cop ies of the full set of ERP files , or multip le installations. This should not be confused WIth multiple environments. A standard ERP sizing accounts for multiple environments including production, pristine , deve lopment, test and training . Refer to Appendix A for a more detailed explanation ,

Will REAL-TIME SYSTEMS ESS (Enterprise Storage Yes/No Server) or FAStT (Fibre Array Storage Technology) , external disk subsystem be used for data storage requirements? (applies only to pSeries or xSenes. If using external storage with iSeries, please consult a pre

1c:.~lpc:.

723 S. Casino Center Blvd . 2nd Floor Las Vegas , NV 89101 Voice : (702) 387 -5 387

www .realtimel lc.com

RTS

High Availability configuration required such as MIMIX, MIMIX OMS OMS, Datamirror, HACMP, or MSCS? Datamirror HACMP MSCS

B. Advanced Applications

Will Advanced Warehousing be used?

How many warehouses will be processing concurrently?

Yes/No

The configuration options for these applications can have a very large impact on the amount of resources consumed. Benchmarking information is not available for Advanced Transportation or Advanced Warehousing. To provide a reasonable pre-sales estimate of the resources required for these applications, the users are factored at double the resources for a standard distribution user. The resources actually used by these applications will vary based on the complexity of the rules and options of the implementation. The details of the implementation and any special considerations should be discussed with an Oracle JD Edwards EnterpriseOne analyst.

C. Development Environment

Will a separate development server be required

Number of concurrent DeveloperslTesters

Yes/No

Platform for Development server: System i__ System p__ System x__

Additional Information

Please list any other information related to your JD Edwards EnterpriseOne implementation which should be considered in the sizing, such as additional applications, phased implementations or other considerations . Also, please provide information on how this information should be applied to the sizing.

For example, if 3rd party interfaces are used to provide input into the JD Edwards EnterpriseOne applications , those users might be considered heavier than a standard user. In order for the sizing center to incorporate additional information into the sizing, guidance must be provided by the customer or business partner regarding how the additional information should be applied.

Voice: (702) 387-5387

www.realtrrnellc.corn


RTS

Section 3: Collaborative Portal

The JD Edwards EnterpriseOne Technology Foundation Collaborative Portal includes several key components . Please answer the following questions to help determine the appropriate configuration for the Collaborative Portal implementation.

Which pieces of the JD Edwards EnterpriseOne Collaborative Portal will be implemented?

Actively Using

Minimal Implementation

Not used

IBM WebSphere Portal Server (Minimal Required) IBM Lotus Sametime (Minimal Required) IBM Lotus Quickplace (Minimal Required) IBM Directory Server (LDAP) IBM Network Dispatcher Other

I. Architecture

A typical JD Edwards EnterpriseOne implementation uses many different server functions, including the servers listed in the ERP implementation section, those for the CRM implementation and the functions listed above for the Collaborative Portal. In order to minimize the footprint and number of boxes, many of these server functions can be combined, particularly for smaller implementations. As the number of users increases and the size of the implementation grows, separate servers may be recommended to isolate heavy workloads or to provide higher availability. Examples of the Collaborative Portal architecture choices may be found in Appendix D. Please describe your planned architecture by answering the questions below.

A. Select location of WebSphere Portal Server

The default REAL-TIME SYSTEMS sizing places WebSphere Portal Server (WPS) on the same box as the ERP Webserver. Please specify the configuration choice and platform for the WPS server (System i, System p, System x):

Select one of the following configuration options Select One WPS runninq on ERP Webserver (JAS Server) WPS running on a separate, dedicated box WPS running on another box, combined with other workloads

Other workloads:

Platform for WPS server:

System i__ System p__ System x__

723 S. Casmo Center Blvd . 2nd Floor Las Vegas, NV 89101 VOice: (702) 387-5387

www .rea ttimellc.com

R S 8. Select location of HTTP Server

The default REAL-TIME SYSTEMS sizing places HTTP server on the same box as WebSphere Portal Server (WPS). This approach is recommended for implementations using internal or intranet access only. If external/Internet access is planned, a separate box separated by a firewall is recommended. Please specify the configuration choice and platform for the HTTP server (System i, System p, System x):

Select one of the following configuration options Select One HTIP server running on the same box as the WPS server HTIP server running on a separate, dedicated box HTIP server running on another box, combined with other workloads

Other workloads'

Platform for HTTP server:

System i__ System p__ System x__

C. LDAP Server

Do you currently have an existing LDAP server in your enterprise? If Yes, what LDAP server is being used? (IBM Directory Server, Domino, other)

Yes/No

Do you need assistance with sizing a new LDAP Server? (for EnterpriseOne workload only) If "No", ski P to Section II

Yes/No

D. Select location of LDAP Server

REAL-TIME SYSTEMS Directory Server is used as the default LDAP server. The default IBM sizing places the LDAP server on a separate, dedicated box. Please specify the configuration choice and platform for the IBM Directory server (System i, System p. System x):

Select one of the following configuration options: I Select One IBM Directory Server on a separate, dedicated box IBM Directory Server running on another box, combined with other workloads

Other workloads:

Platform for IBM Directory Server : System i__ System p__ System x__

723 S. Casino Center Blvd. 2nd Floor Las Vegas, NV 89101 VOice: (702) 387-5387

www.realtimellc.com

RTS E. Select location of Sametime Server

IBM Sametime is part of the Collaborative portal and can be installed on a separate , stand-alone server or combined with other workloads. The default REAL-TIME SYSTEMS sizing places the Sametime Server on a separate, dedicated box. Please specify the configuration choice and platform for the IBM Sametime server (System i, System o, System x):

Select one of the fallowing configuration options: Select One Sametime Server on a separate, dedicated box Sametime Server running on another box, combined with other workloads

Other workloads:

Platform for Sametime Server: System i__ System p__ System x__

F. Select location of QuickPlace Server

IBM QuickPlace is part of the Collaborative portal and can be installed on a separate, stand-alone server or combined with other workloads. The default REAL-TIME SYSTEMS sizing places the QuickPlace server on a separate, dedicated box. Please specify the configuration choice and platform for the IBM QuickPlace server (System i, System p, System x):

Select one of the followinq conficuration options: Select One QuickPlace Server on a separate, dedicated box QuickPlace Server running on another box, combined with other workloads

Other workloads:

Platform for QuickPlace Server: System i__ System p__ System x__

VO ice: (702) 387-5387

www.realtirneltc.corn

723 S. Casino Center Blvd. 2nd Floor Las Vegas, NV 89 10 1

RTS II. Portal Usage Information

A. User Environment

Active users : users are judqed to be active if they are clicking the "OK" button or using Function keys or some other key that initiates processing 2 to 3 times a minute. Users that are signed on, but are not actively using the system should not be counted. For this sizing, the number of users reported should be the total number of active users during a peak period.

Please note that the number of active portal users should be the same as or less th an the number of active HTML users listed in the application se ctio n, s ince it is ass um ed the po rtal users are also using the JD Edwards application. Please explain any differences in the user counts between the porta l section and the application section .

How many total registered users will there be? How many active users will there be during the peak hour?

The default concurrency for Portal users is 50% . This means that if the total registered user count is 100 users, the active users would be 50. Your planned usage should be taken into account to determine the active users during a peak period.

How many times will each user log on and off during the peak hour? (Default for EnterpnseOne is "1") Once logged on, how many requests per hour will each user make inside the portal? (Default for EnterpriseOne is "20Jl

)

On average how long will a logged on user pause before requesting a new page? This is known as "Think Time". (The default for EnterpriseOne IS

"20" seconds)

B. Portal environment

On average, how many portlets make up a web page? (Default for EnterpriseOne is "5") What is the ceresntace breakdown of portlet complexitv? (TotaI of 100%)

(Default for EnterpriseOne is "0") Simple (Default for EnterpriseOne is "50%") Moderate (Default for EnterpriseOne is "50%") Complex

Total 100%

Note: Portal complexity is a gauge of the work that must be done to generate the portlet. Static pages are considered simple . Portlets that require some basic computation should be considered moderate. The standard ERP related portlets are considered moderate. These portlets initiate a session on the ERP webserver, so much of the processing is carried out by the ERP webserver, decreasing the workload on the portal server. Portlets that require complex computation and calls to other programs should be considered complex. Portlets such as the Business

VOice: (702) 387·5387

www .realtimellc.ccrn


RTS Intelligence monitors could be considered complex . These portlets update status of key business intell igence indicators and process within the portlet server . The default for EnterpriseOne implementations is 50% moderate and 50% complex, with no simple portlets.

C. Portlets to be used

JD Edwards Enterprise One provides some basic port lets for use with the EnterpriseOne Collaborative portal Please select the portlets which will be used :

Mark "X" by all that apply

ERP portlets CRM Portlets

Business Intellioence Portlets Supply Chain Manaqemenl portlets

Self Service portlets Ema il access portlets for Lotus Notes or Microsoft Exchanqe/Outlook

Access to Lotus Qu ickPlace Access to Lotus Sametime Other

III. Other Information

A. Development Environment

uired Yes/No

Platform for Development server: System i__ System p__ System x__

B. High Availability

115 a high availability/failover required YeslNo

C. Growth

I Growth projected in Portal users one year after start of production (%)?

D. Additional Information

Please list any other Information related to your JD Edwards EnterpriseOne implementation w hich should be considered in the sizinq, such as additional applications , phased implementations or other considerations. Also, please provide information on how this information should be applied to the sizing .

For example , if 3rd party interfaces are used to provide input into the JD Edwards EnterpriseOne applications , those users might be considered heavier than a standard user. In order for the sizing center to incorporate additional information into the sizing , guidance must be provided by the customer or business partner regarding how the additional information should be applied .

VOice: (702 ) 387-5387

www.realtirnetlc.com


RTS

Appendix A - Explanations and Terminology

EDI

Electronic Data Interchange is a method of importing data such as sales orders though a batch process . Documents are transferred from vendors or other sources and converted to EnterpriseOne transactions via the import process . Transaction volumes for sizing purposes are converted to lines per hour , such as sales order lines per hour, which need to be processed during a peak period.

Batch Requirements

USEs (Universal Batch Engines) are EnterpriseOne batch and reporting processes. Most EnterpriseOne batch processes are CPU intensive. Because of this, running multiple concurrent UBEs on a single processor will cause some degradation in performance of the UBE. Since users generally process at a higher priority, their performance should not be impacted as much. In most environments, this USE degradation will be acceptable and running more than 1 batch process per processor will provide adequate performance. In some environments there are critical batch processes that must complete in the shortest time possible . In these cases, the system is sized to allow for adequate processors to account for the number of concurrent batch jobs being run. Care should be taken in answering the number of concurrent batch processes. Multiple concurrent USEs will require multiple processors and can quickly drive the cost of the system higher. A standard REAL-TIME SYSTEMS sizing accounts for a significant batch workload and should suffice in most envi ronments.

To determine number of concurrent USEs , critical business processes should be evaluated. What is critical to one business may be routine to others. Some examples of critical processes are:

• Interfaces with other systems that must happen in a short time window or that are critical to user activity,

• long running import or export processes that have a historically short time window

• other long running jobs, such as updates, payroll , MRP, etc, that have tight time constraints

• short running jobs that are very high volume that are critical to business processes such as printing pick slips or invoices in very high volume businesses

These are only a few examples to consider when determining the number of critical USEs. Your business processes should be evaluated along with historical patterns for your industry.

723 $. Casino Center Blvd . 2nd Floor Las Vegas, NV 8910 1 VOice: (702) 387-5387

www.reemmenc.corn

RTS

Multiple Instances of EnterpriseOne

Some circumstances require multiple instances of the EnterpriseOne application running on the same box. This would be similar to having multiple installations, each having a full set of ERP files, libraries and directories.

A standard ERP installation includes multiple environments, including environments for development, training, test, pristine and production. Some files and objects are shared across environments, others are specific to the environment. For example, data files for training and production environments would be separate, but they would share a common data dictionary. A separate instance would duplicate all of the objects, so there would be a full complement of all environments and files for each instance. There would be a production environment for instance A and a production environment for instance B, a development environment for instance A and a development environment for instance B, and so on . It is easiest to consider multiple instances as separate installations running on the same box.

Implementing multiple EnterpriseOne instances requires dupl icates of the all EnterpriseOne objects, including database files and application code. Some examples of when multiple EnterpriseOne instances may be required include support for multiple double byte languages or multiple code pages . When multiple instances are required careful customized planning for handling consolidated reporting, merged or separate file schemes, languages and time zones is needed. Additional disk space must be added to allow for the duplication of files for each instance. Additional servers, such as TSE servers may also be required . To determine if multiple instances are required and the number of instances necessary, contact your Oracle representative.

If multiple instances are specified disk space will be increased by the base amount for each instance. For example: if a base install on iSeries requires 40GB, (which includes ERPtOneWorld base libraries and files for the standard 4 pathcoces, 5 environments) , and 3 instances are specified, then an additional 80GB wil l be added to the raw disk estimate to account for the 2 additional instances beyond the standard 1. The dataspace amount. (calculated on a per user basis) , will then be added a single time to this base amount.

FAStT

FAStT500 Storage Server is the storage of choice for those wanting the ultimate in midrange storage consolidation and data sharing on multiple or heterogeneous server platforms. The FAStT500 supports rapid universal access to vast quantities of data through many advanced functions and features, making it a workhorse for business-critical applications.

The people of IBM Storage Systems can provide flexible business solutions that maximize price-toperformance ratios. IBM TotatStoraqe " FAStT500 Storage Server is a full-fibre , storage area network (SAN) solution that gives you the performance you need at the right price .

723 S. Casino Center Blvd. 2nd Floor Las Vegas, NV 89101 VOICe: (702) 387-5387

www. realt irnelie.eom

RTS

ESS

The Enterprise Storage Server (ESS) is REAL-TIME SYSTEMS's next generation leadership disk subsystem.

ESS represents the integration of multiple advanced technologies for safely storing, quickly accessing, and easily managing data. The ESS can be described as an all-in-one disk system for the entire enterprise that stands apart from the competition in many ways.

Delivering innovations in design, performance, and function , the ESS meets and exceeds the stringent requirements that demanding customers place on large scale disk subsystems. Satisfying needs ranging from easier management of storage resources, to 24x365 access , to higher levels of performance and lower cost of ownership. The ESS provides demonstrable business value. With concurrent support for a broad range of server families such as Windows NT/2000 servers, UI'JIX based servers, and iSeries (AS/400) servers (as well as zSeries) - the ESS is truly a storage solut ion for the entire enterprise.

High Availability

A highly available system can be implemented using technologies including REAL-TIME SYSTEMS's HACMP product on the UNIX platform, MIMIX (from Lakeview Corp.) , OMS (from Vision Solutions), or Datamirror (from Datamirror Corp.) on the iSeries , or MSCS on the xSeries. In all cases, a second system is required for implementation.

723 S. Casino Center Blvd. 2nd Floor Las Vegas, NV 89101 VOice: (702) 387·5387

www.realt.rnellc .com

RTS

Appendix B ERP sizing scenarios

Currently we are able to provide pre-sales sizing estimates for two tier implementations and three tier implementations of EnterpriseOne. In a two tier implementation , the proposed server functions as the central database server supporting client PCs running EnterpriseOne business logic and the EnterpriseOne user interface. A two-tier implementation of EnterpriseOne is shown in diagram 1 below.

ERP 2-tler

Full Chent (Including business

logic)

'-r--Locai Ar a Network-.----)

f---

Deployrr,etil Server

Diagram 1

In a three-tier implementation, the business logic (called Business Functions) can be moved from the client PC to the database server, this is known as a virtual three-tier implementation. Alternatively, the Business Function logic can be mapped to an intermediate layer on another system, this is known as a physical three-tier implementation. Support of WAN attached Clients with EnterpriseOne is best achieved by using a three tier architecture and Windows Terminal Server technology, Citrix, or by using the EnterpriseOne Web client support. Virtual three-tier and Physical three-tier configurations, including support for Windows Terminal Sever and the ERP Web client are shown in diagrams 2 and 3.

ERP DB Server

VOIce: (702) 387-5387

www .realtrrnellc .corn

723 S. Casino Center Blvd . 2nd Floor Las Vegas, NV 89101

,e RTS ERP V,rtual 3-oer

WTS c ie nt WebCII. nl

-~ant "M,pped" CI"nl

)

/ ~ S

§]~ ~

= ~ = = = = = = = = =

ER? \-~ s.o: -"' ef jepkJ't'lflP.nt Web (o~or) Teflflfili' Server S~I '~'o!: ' GerleIl;:(Ot Server

(q:t ;oj.al) lqJ:lCra )

Diagram 2

ERP Physical 3-tler

WT S Client Web Client

"Mapp<d" Chant

~==>----l'O-+ L o ca l Are. N&lwor,

~= = =

Local Area N two r~

ER'P A..""CUcation Server (IX."!.rless logic)

ERPV\l'eb Serve; W ndow s D<ploymenl 'Neb (optiOnsl) Te.omlO8l Server Server oene ecc-Server

ERPDBServer (o;:t,onal) (Cl'OO''')

'Nr.::.:""'s

7235" Casino Center Blvd. 2nd Floor Las Vegas, NV 89101 VOice: (702) 387-5387

www.realtimellc.com

,e RTS

Appendix C Collaborative Portal sizing scenarios

The EnterpriseOne Collaborative Portal can be implemented using several different architectures, depending on a client's specific needs. All architectures will make use of similar tiers and will use the same application components . How these components are separated or combined will vary. The individual components that make up the collaborative portal are the IBM HTTP server, WebSphere Portal server, WebSphere Application server, LDAP server, Sametime, QuickPJace, Domino and Collaboration server. In addition there are other pieces that make up the Enterprise application environment, such as ERP database servers, logic or batch servers. etc.

In a simple environment, some of the components will be combined onto the same box. As an implementation scales to larger user counts or higher transaction rates , separate servers may be recommended for different pieces . Likewise separate servers may also be recommended tor high availability or security purposes.

Figure 1 shows a common environment in which the WebSphere application server, Portal server and HTTP server are all run on the same system. This works well in many instances, although because the HTIP server is located on the same box, this architecture should not be considered secure if there is external/Internet access to the network .

HTML ClJent

,-----_ - - _ Elhern«1 -'o ,I

IBM HITP serve

!webSPhere f--- Entt rp."lSe LDAP Application Server

server W ebSphere App\u; 6t.rOn serv er

Enterprise Appbcencn enveoomc ot ( 1TIWl1ple serv er'S)

723 S. Casino Center 8lvd . 2nd Floor Las Vegas, NV 89101 VOice; (702) 387-5387

www.realtimellc.com

--------------

I

RTS

Figure 2 provides an example of a simple environment with failover capabilities. A network dispatcher has been added to balance traffic between two combined HTIP, WebSphere Application and portal servers. The enterprise application servers can also be configured to provide high availability. As in Figure 1, the scenario depicted in Figure 2 would satisfy the requirements of an internal network only, since the servers are not protected by a firewall .

IntemalOnly

0== - ---, i Bhtlli -..t )-

Websphere Application servers

Figure 2

I I

Net'ttiQr'l( c.~patc~I I .--------

16M HTTPSElV e f

~l!'PtlrtetllSlYV$f H~" o~" COAO VSCfVO ~

~b'S~" Ar)f "~icn . ~ "" Of

-- -----... »>:

~.c I1 T1P ;'CN'Y

"'......,bSophe re FOl1.,) $NVClf'

WEbSoher~ M~~;;.n ~~~r

--

Application r s=~ w

~r ll: fIl r ~se AopllCOtlel"t 1:""' ..._ ....,--.:

Envimoment (n-....c.pe $;!'I'''''· ~' ~ l

I I

P""""""'ec e J

7235. Casino Center Blvd . 2nd Floor Las Vegas, NV 89101 VOice: (702) 387 -5387

www. realtimelic.ccrn

RTS

Figure 3 provides an example of a more secure network . This is done by isolating the HTTP server from the rest of the network by a firewall. This figure also depicts multiple servers to provide high availability .

H T....... Cllerll:

lnternet

I

DMZ

Websphere Application servers

'--- --=:::__. - 1 l.- . --:::;o !,----- --__-~---

-~]Application En: II)"p" l~ AJlp·ok".l'lI lOn ":'! 1'"N .rQ""lm~H.

( 11l \Mt ' P'l!' ~f~rslEnvimoment

I'ao..,........,. ~l

Figure 3

723 S. Casino Center Blvd. 2nd Floor Las Vegas, NV 89101 VOice : (702) 387-5387

www.rea lnmellc.corn

RTS - MetCreatives Cacoon Theme Questionnaire.pdf · general information about your JD Edwards...

Documents

Transcript of RTS - MetCreatives Cacoon Theme Questionnaire.pdf · general information about your JD Edwards...