OTN - Installing and Configuring FDM 11.1.1

Installing and Configuring Oracle® Hyperion Financial Data Quality Management, Fusion Edition 11.1.1.0.0 for Financial Management

Purpose

This tutorial covers installing and configuring Financial Data Quality Management (FDM) for a Financial Management installation.

Time to Complete

Approximately 2 hours.

Topics

This tutorial covers the following topics:

	Overview
	Scenario
	Prerequisites
	Installing Financial Data Quality Management
	Configuring the Web Server
	Configuring Task Manager and Application Manager
	Configuring Load Balance Manager
	Configuring Workbench
	Creating Financial Data Quality Management Applications
	Installing and Configuring the Financial Management Adapters
	Summary
	Related information

Viewing Screenshots

Place the cursor over this icon to load and view all the screenshots for this tutorial. (Caution: This action loads all screenshots simultaneously, so response time may be slow depending on your Internet connection.)

Note: Alternatively, you can place the cursor over an individual icon in the following steps to load and view only the screenshot associated with that step. You can hide an individual screenshot by clicking it.

Overview

In this tutorial, you learn to install and configure FDM, create an FDM application, and link the FDM application to a Financial Management application.

Back to Topic List

Scenario

As an administrator, you are tasked with installing FDM, creating an FDM application, and integrating the FDM application with a Financial Management application.

Back to Topic List

Prerequisites

Before starting this tutorial, you should:

1.	Have access to Workspace and Financial Management.
2.	Know the database creator account and password.
3.	Have access to or have created a Financial Management application that you can link to your FDM application.
4.	Know the Windows account under which DCOM objects run.
5.	Know the Windows account under which the .NET processes run.
6.	Know the user account in your authentication directory that is used to browse the directory and perform authentication.

Back to Topic List

Installing Financial Data Quality Management

In this topic, you install all components of FDM.

1.	Navigate to Oracle E-Delivery, and perform the following actions: a. In the Select a Product Pack drop-down list, select Oracle Enterprise Performance Management System. b. In the Platform drop-down list, select Microsoft Windows (32-bit). c. Click Go.
2.	On the Oracle Enterprise Performance Management (11.1.1.0.0) Media Pack for Microsoft Windows (32-bit) page, select Oracle Hyperion Financial Data Quality Management, Fusion Edition Release 11.1.1.0.0 Microsoft Windows X86, and click Download.
3.	Save the V13458-01.zip file to a temporary directory.
4.	Navigate to the V13458-01.zip file and extract the assembly.dat file to the assemblies folder on your computer.
5.	Navigate to your assemblies folder, and confirm that it contains the fdm folder.
6.	Navigate to your Oracle EPM System Install directory and double-click InstallTool.cmd to launch the Oracle Hyperion EPM System Installer.
7.	On the Welcome page of the Hyperion EPM System Installer Release 11.1.1, click Next.
8.	Accept the default destination folder or click Browse to enter a new destination folder, and then click Next.
9.	Select New Installation and Choose components individually, and click Next.
10.	Select FDM and click Next.
11.	Click Next to install all components.
12.	Confirm that all components are installed, and click Finish to exit Hyperion EPM System Installer Release 11.1.1.

Back to Topic List

Configuring the Web Server

In this topic, you configure the Web Server. The Web-based interface provides end users and administrators access to a number of FDM features.

1.	Select Start > Programs > Oracle EPM System > Financial Data Quality Management > Web Server Components > Web Config Manager.
2.	Enter the user name, password, and domain of the Windows account under which the .NET Web process will run. Note: This account can be a local or a domain account, and it must have administrator rights to the Web Server.
3.	On the Load Balance Server tab, enter the Load Balance server name, and click OK. The load balance server is the computer that stores FDM application configurations and performs load balancing on FDM application servers. You may also specify a backup load balance server.
4.	Select Start > Run, type cmd, and click OK to open a command prompt.
5.	Type iisreset to restart Internet Information Services (IIS).

Back to Topic

Configuring Task Manager and Application Manager

Task Manager installs a Windows service that runs scheduled tasks (FDM scripts) at specified intervals. Tasks can be scheduled to run repeatedly, daily, weekly, or monthly. The Application Server component enables the execution of resource-intensive tasks on a server other than the Web server, and thus can be used to limit database and file system access to a server behind a firewall (when the Web server is in front of the firewall).

In this topic, you assign the "Log on as a service" user permission to your administrator account. This user right is required for running scheduled tasks in Task Manager. You then configure the Task Manager and Application Manager components.

1.	Select Start > Programs > Administrative Tools > Local Security Policy, and expand Local Policies > User Rights Assignment.
2.	In the right pane, double-click Log on as a service.
3.	In the "Log on as a service Properties" dialog box, perform these actions: Verify that your admin account is listed, or click Add User or Group to add your admin account. Click OK to close the "Log on as a service Properties" dialog box. Select File > Exit to close the Local Security Policies window.
4.	Select Start > Programs > Oracle EPM System > Financial Data Quality Management > Task Manager> Task Manager Configuration.
5.	Enter the user name, password, and domain of the Windows account under which the Task Manager service and the FDM DCOM objects run. Note: The Windows account must have full control permission for the FDM application folders that reside on the data server, as well as rights to the target system.
6.	On the Load Balance Server tab, enter the name of your load balance server. You can enter a backup load balance server as well.
7.	Select Start > Programs > Oracle EPM System > Financial Data Quality Management > Application Server > Application Server Config Manager.
8.	Enter the user name, password, and domain of the Windows account under which the application server DCOM objects run, and click OK. Note: The Windows account must have full control permission on the FDM application folders that reside on the data server, as well as rights to the target system.

Back to Topic List

Configuring Load Balance Manager

Load Balance Manager enables you to balance the load on the FDM application servers and store the FDM application configuration. A common scenario is to install Load Balance Manager on a computer that is running the Application Server component.

In this topic, you configure Load Balance Manager by specifying the FDM application servers to use for load balancing.

1.	Select Start > Programs > Oracle EPM System > Financial Data Quality Management > Load Balance Manager > Load Balance Configuration.
2.	Enter the user name, password, and domain of the Windows account under which the Load Balance Manager DCOM objects run. Note: The Windows account must have full control permission on the FDM application folders that reside on the data server, as well as rights to the target system.
3.	On the Application Servers tab, click Add, and enter the names of all servers that run the FDM Application Server component.
4.	On the Authentication Providers tab, click Add, and enter the name of the authentication provider that you will use in FDM. The Authentication Provider dialog box is displayed. Note: This screen enables you to add the following authentication providers: NTLM (NT LAN Manager), LDAP (Lightweight Directory Access Protocol), MSAD (Microsoft Active Directory), VBSCRIPTSSO (Visual Basic script single sign-on), and VBSCRIPT (Visual Basic script). You can specify any combination of the five authentication providers. FDM attempts to authenticate users by using the authentication providers in the order in which they are listed, from top to bottom. You can click Move Up and Move Down to change the order. At least one enabled authentication provider is required.
5.	Enter the information for your authentication provider, and click OK. Note: When you place the cursor over an information icon (to the right of each item), a description of the item is displayed.
6.	Confirm that your authentication provider is displayed, and click OK. Note: Only accounts in the added URLs can access FDM. If no URLs are specified, the entire directory tree is searched.

Back to Topic List

Configuring Workbench

Workbench is a Windows client program that provides an administration and development environment. It enables you to perform common administrator tasks, such as creating locations, building import formats, and creating validation and logic groups. It also enables you to administer integration adapters, scripts, and reports.

In this topic, you configure Workbench by defining a Load Balance group.

1.	Select Start > Programs > Oracle EPM System > Financial Data Quality Management > Workbench > Workbench Client.
2.	In the Load Balance Server Group dialog box, click Add.
3.	Enter a group name and description, enter the name of your primary load balance server, and click OK. Note: You can also add a backup server name. A domain name, IP address, and server name are acceptable formats in which to designate the server. You can browse for a server by clicking .

Back to Topic List

Creating Financial Data Quality Management Applications

In this topic, you create an FDM application and database. After creating the new application, you install the standard reports and templates.

1.	Follow the steps required by your database provider to ensure that your database administrator account has rights to create a new database.
2.	Log on to FDM by performing the following actions: Open Internet Explorer and enter the following URL: http:///HyperionFDM/, where is the name of your Web Server. Select , and enter the user name, password, and domain of an account that can create FDM applications. Click Logon. Note: The specified account is added to the FDM application as an FDM administrator.
3.	On the General tab in the New Application form, enter the name, description, and path of the new application.
4.	On the Database tab perform the following actions: In OLE DB Provider list, select SQLOLEDB (SQL Server) or ORACLEDB.ORACLE (Oracle). Enter the database server name, database name, and the user name and password of the database administrator. Click OK.
5.	Verify that the application was created successfully, and click OK.
6.	Navigate to the V13458-01.zip file, and extract the V13458-01.zip file to a temporary directory. The file contains the Reports and Templates zipped files.
7.	Navigate to the unzipped V13458-01.zip file, and extract the FinancialDataManagement-Reports11.1.1.0.zip file to c:\Hyperion\products\FinancialDataQuality\\Reports.
8.	Navigate to the unzipped V13458-01.zip file, and extract the FinancialDataManagement-Templates11.1.1.0.zip file to c:\Hyperion\products\FinancialDataQuality\\Outbox\Templates.
9.	Select Start > Programs > Oracle EPM System > Financial Data Quality Management > Workbench > Workbench Client.
10.	Select your application, enter the user name, password, and domain (if necessary), and click OK.
11.	Select the Report tab, and then select File > Import.
12.	Select the file c:\hyperion\fdm\\Reports\StandardReportsSQLServer1111Active.xml (for SQL) or c:\hyperion\fdm\\Reports\StandardReportsOracle1111Active.xml (for Oracle), and click Open.
13.	On the General tab, select Reports and click OK.
14.	Select File > Exit.
15.	Log on to your application by performing the following actions: In Internet Explorer, enter the following URL: http:///HyperionFDM/, where is the name of your name of your Web server. Select your application, and enter the user name, password, and domain (if necessary). Click Logon.
16.	In the navigation pane, select Tools > Templates to view the imported templates.

Back to Topic List

Installing and Configuring Financial Management Adapters

After you create an FDM application, you install and configure the Financial Management adapters. Financial Management adapters enable interaction between the FDM application and the Financial Management applications.

Adapters have two components —DLL/EXE and XML metadata. DLL/EXE files contain the system-specific instructions for interacting with target or source systems. XML files contain all data that relates to the current FDM application.

In this topic, you install the Financial Management adapters and create a connection to a Financial Management application.

1.	On the Oracle E-Delivery site, select Oracle Hyperion Financial Data Quality Management Adapter for Financial Management, Fusion Edition Release 11.1.1.0.0 Microsoft Windows X86, and click Download.
2.	Save the V13502-01.zip file to a temporary directory.
3.	Extract the V13502-01.zipfile to c:\Hyperion\products\FinancialDataQuality\SharedComponents.
4.	Select Start > Programs > Oracle EPM System > Financial Data Quality Management > Workbench > Workbench Client.
5.	Select your application, enter the user name, password, and domain (if necessary), and click OK.
6.	On the Adapters tab, select File > Import.
7.	Select FM9x-G4-B.xml, and click Open.
8.	On the General tab, select Integration Adapters, and click OK.
9.	On the Oracle Hyperion FDM Workbench, select File > Import.
10.	Select FM9i-G4-B.xml, and click Open.
11.	Select Integration Adapters, and click OK. Note: FM9x-G4-B.xml is the standard HFM adapter, and FM9i-G4-B.xml is the Intercompany Detail adapter.
12.	Verify that the two adapters are displayed in the Target System Adapters section on the Adapters tab.
13.	Select File > Register Adapter.
14.	Select upsFM9xG4B.dll, and click Open.
15.	Verify that the adapter registered successfully, and click OK.
16.	In the navigation pane, expand Target System Adapters > FM9x-G4-B.xml, right-click Machine Profile, and select Add Machine Profile.
17.	In the Add Machine Profile dialog box, enter the required information: Source Machine is the FDM application server name. Target Machine is the computer name or IP address of the application server or application cluster. Optional: To override the logon method specified by the integration settings, specify a user name, password, and domain for the local computer
18.	In the navigation pane, expand Target System Adapters > FM9i-G4-B.xml, right-click Machine Profile, and select Add Machine Profile.
19.	In the Add Machine Profile dialog box, enter the required information: Source Machine is the FDM application server name. Target Machine is the computer name or IP address of the application server or application cluster. Optional: To override the logon method specified by the integration settings, specify a user name, password, and domain for the local computer.
20.	Log on to your application by performing the following actions: In Internet Explorer, enter http:///HyperionFDM/, where is the name of your Web server. Select your application and enter the user name, password, and domain (if necessary). Click Logon.
21.	Select Administration > Application Settings.
22.	In the System Code list, select FM9X-G4-B, and click Save.
23.	Select Administration > Integration Settings.
24.	In Integration Settings, perform the following actions: In the Options list, select Application name. In the App Name box, enter the name of your Financial Management application.
25.	In Integration Settings, perform these actions: In the Options list, select Logon Method. In the Method list, select a logon method: Unified: The FDM user name and password are used to log on to the target system. For this option to be usable, the target user name and password and the FDM user name and password must be the same. Global: The user name and password specified for global logon is passed to the target system. Users enter the same user name and password to connect to the target system. Click Save.
26.	Select Activities > Maps to test the connection to Financial Management.
27.	Click Add to add a row.
28.	Click in the Target FM Account cell, and select Browse for Target Value.
29.	Verify that the list of accounts is from your Financial Management application. You have successfully installed and configured FDM for a Financial Management application.

Back to Topic List

Summary

In this tutorial, you learned how to:

	Install Financial Data Quality Management
	Configure the FDM Web Server, Task Manager, Application Manager, Load Balance Manager, and Workbench
	Create an FDM application and install standard reports and templates
	Install and configure the Financial Management adapters

Back to Topic List

Related Information

To learn more about Financial Data Quality Management, refer to additional OBEs on the OTN Web site

Oracle Data Integrator简介

作者：NinGoo

ODI(Oracle Data Integrator)是Oracle在2006年10月收购Sunopsis公司后，整合Sunopsis Active Integration Platform而推出的一款数据集成工具，现在是Oracle Fusion Middleware的组件。和Oracle自己的OWB(Oracle Warehouse Build)相比，ODI支持更多的异构数据源，支持SOA，支持Jython，和OWB正好互补。ODI和OWB都是所谓的ELT工具，和通常所见的 ETL工具不同，它们不是采用独立的引擎而是采用RDBMS进行数据转换。做为领先的RDBMS供应商，Oracle选择ELT而不是ETL不是没有道理 的。

ODI的主要组件包括模块知识库，图形模块和执行引擎，都是基于java编写，所以运行ODI需要有JDK的支持。另外还有一个基于J2EE的元数据导航器(Metadata Navigator)。

知识库

ODI所有模块的信息都保存在一个叫做Master Repository的中心知识库中。Master Repository通过Master Repository Creation Wizard创建，这也是安装完ODI后应该做的第一个任务。

除了Master Repository，还需要为不同的任务创建Work Repository。Work Repository中的信息包括模块信息，项目信息和运行期信息。

图形模块

Designer 用于定义数据转换逻辑，这是最常用的开发工具，大部分的开发任务，包括data store的定义，interface(数据映射关系)和package（相当于workflow）的创建等，都是在Designer中完成。

Operator用于管理和监控数据转换任务的执行情况，在设计阶段，也可用于调试(debugging)

Topology Manager用于定义物理和逻辑基础架构，如work repository的创建和管理等。

Security Manager用于管理用户权限

运行期组件

Schedule Agent计划代理，用于调度执行数据转换任务。计划代理同时也带有一个数据转换引擎，但是ODI采用E-LT架构，所以基本上计划代理只是将任务传递给目标库，其数据转换引擎很少用到。

附：安装完ODI后默认用户名为SUPERVISOR，密码为SUNOPSIS，大小写敏感。

ODI官方网站：http://www.oracle.com/technology/products/oracle-data-integrator/index.html
ODI中文官方网站：http://www.oracle.com/technology/global/cn/products/oracle-data-integrator/index.html

参考文章：An Introduction to Real-Time Data Integration

DB - Oracle reconfig database control

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>cd C:\app\Administrator\product\11.1.0\d
b_1

C:\app\Administrator\product\11.1.0\db_1>cd bin

C:\app\Administrator\product\11.1.0\db_1\BIN>emca
C:\app\Administrator\product\11.1.0\db_1\bin\emca.bat [operation] [mode] [dbType
] [flags] [parameters]

-h | --h | -help | --help: prints this help message
-version: prints the version

-config dbcontrol db [-repos (create | recreate)] [-cluster] [-silent] [-backup]
[parameters]: configure Database Control for a database
-config centralAgent (db | asm) [-cluster] [-silent] [parameters]: configure cen
tral agent management
-config all db [-repos (create | recreate)] [-cluster] [-silent] [-backup] [para
meters]: configure both Database Control and central agent management

-deconfig dbcontrol db [-repos drop] [-cluster] [-silent] [parameters]: de-confi
gure Database Control
-deconfig centralAgent (db | asm) [-cluster] [ -silent] [parameters]: de-configu
re central agent management
-deconfig all db [-repos drop] [-cluster] [-silent] [parameters]: de-configure b
oth Database Control and central agent management

-addInst (db | asm) [-silent] [parameters]: configure EM for a new RAC instance
-deleteInst (db | asm) [-silent] [parameters]: de-configure EM for a specified R
AC instance

-reconfig ports [-cluster] [parameters]: explicitly reassign Database Control po
rts
-reconfig dbcontrol -cluster [-silent] [parameters]: reconfigures RAC Database C
ontrol deployment

-displayConfig dbcontrol -cluster [-silent] [parameters]: displays information a
bout the RAC Database Control configuration

-migrate -from dbcontrol -to centralAgent [-repos drop] [-cluster] [-silent] [p
arameters]: migrates EM configuration from Database Control to central agent

-upgrade (db | asm | db_asm) [-cluster] [-silent] [parameters]: upgrades an earl
ier version of the EM configuration to the current version

-restore (db | asm | db_asm) [-cluster] [-silent] [parameters]: restores the cur
rent version of the EM configuration to an earlier version

Parameters and Options:
[parameters]: [ -respFile fileName ] [ -paramName paramValue ]*
db: perform configuration operation for a database (including databases that use
ASM)
asm: perform configuration operation for an ASM-only instance
db_asm: perform upgrade/restore operation for a database and an ASM instance
-repos create: create a new Database Control repository
-repos drop: drop the current Database Control repository
-repos recreate: drop the current Database Control repository and recreate a new
one
-cluster: perform configuration operation for a RAC database
-silent: perform configuration operation without prompting for parameters
-backup: configure automatic backup for a database

Parameters for single instance databases
ORACLE_HOSTNAME: Local hostname
SID: Database SID
PORT: Listener port number
ORACLE_HOME: Database ORACLE_HOME
HOST_USER: Host username for automatic backup
HOST_USER_PWD: Host user password for automatic backup
BACKUP_SCHEDULE: Automatic backup schedule (HH:MM)
EMAIL_ADDRESS: Email address for notifications
MAIL_SERVER_NAME: Outgoing Mail (SMTP) server for notifications
ASM_OH: ASM ORACLE_HOME
ASM_SID: ASM SID
ASM_PORT: ASM port
ASM_USER_ROLE: ASM user role
ASM_USER_NAME: ASM username
ASM_USER_PWD: ASM user password
SRC_OH: ORACLE_HOME for the database to be upgraded
DBSNMP_PWD: Password for DBSNMP user
SYSMAN_PWD: Password for SYSMAN user
SYS_PWD: Password for SYS user
DBCONTROL_HTTP_PORT: Database Control HTTP port
AGENT_PORT: EM agent port
RMI_PORT: RMI port for Database Control
JMS_PORT: JMS port for Database Control
EM_SWLIB_STAGE_LOC: Software library location
PORTS_FILE: Path to a static file specifying the ports to use (Default v
alue : ${ORACLE_HOME}/install/staticports.ini).

Additional Parameters for cluster databases
CLUSTER_NAME: Cluster name
DB_UNIQUE_NAME: Database unique name
SERVICE_NAME: Service name
EM_NODE: Database Control node name
EM_SID_LIST: Agent SID list [comma separated]

C:\app\Administrator\product\11.1.0\db_1\BIN>emca -config dbcontrol db

STARTED EMCA at Mar 27, 2009 4:21:55 PM
EM Configuration Assistant, Version 11.1.0.5.0 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.

Enter the following information:
Database SID: orcl
Database Control is already configured for the database orcl
You have chosen to configure Database Control for managing the database orcl
This will remove the existing configuration and the default settings and perform
a fresh configuration
Do you wish to continue? [yes(Y)/no(N)]: y
Listener port number: 1521
Password for SYS user:
Password for DBSNMP user:
Password for SYSMAN user:
Password for SYSMAN user: Email address for notifications (optional):
Outgoing Mail (SMTP) server for notifications (optional):
-----------------------------------------------------------------

You have specified the following settings

Database ORACLE_HOME ................ C:\app\Administrator\product\11.1.0\db_1

Local hostname ................ cdcjp70
Listener port number ................ 1521
Database SID ................ orcl
Email address for notifications ...............
Outgoing Mail (SMTP) server for notifications ...............

-----------------------------------------------------------------
Do you wish to continue? [yes(Y)/no(N)]: y
Mar 27, 2009 4:23:28 PM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at C:\app\Administrator\cfgtoollogs\emca\or
cl\emca_2009_03_27_16_21_55.log.
Mar 27, 2009 4:23:35 PM oracle.sysman.emcp.util.DBControlUtil stopOMS
INFO: Stopping Database Control (this may take a while) ...
Mar 27, 2009 4:23:43 PM oracle.sysman.emcp.EMReposConfig uploadConfigDataToRepos
itory
INFO: Uploading configuration data to EM repository (this may take a while) ...
Mar 27, 2009 4:24:52 PM oracle.sysman.emcp.EMReposConfig invoke
INFO: Uploaded configuration data successfully
Mar 27, 2009 4:24:55 PM oracle.sysman.emcp.EMConfig perform
SEVERE: Cannot start Database Control. The following ports are already in use: [
Database Control HTTP port:1158 RMI port for Database Control:5520].
Refer to the log file at C:\app\Administrator\cfgtoollogs\emca\orcl\emca_2009_03
_27_16_21_55.log for more details.
Could not complete the configuration. Refer to the log file at C:\app\Administra
tor\cfgtoollogs\emca\orcl\emca_2009_03_27_16_21_55.log for more details.

C:\app\Administrator\product\11.1.0\db_1\BIN>

HW - Memory Limits for Windows

Ref: MSDN
http://msdn.microsoft.com/en-us/library/aa366778(VS.85).aspx#physical_memory_limits_windows_server_2003

Physical Memory Limits: Windows Server 2003

The following table specifies the limits on physical memory for Windows Server 2003. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version	Limit in 32-bit Windows	Limit in 64-bit Windows
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition	128 GB 64 GB with 4GT	2 TB
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition	64 GB	2 TB
Windows Storage Server 2003, Enterprise Edition	8 GB	Not applicable
Windows Storage Server 2003	4 GB	Not applicable
Windows Server 2003 R2 Datacenter Edition Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition	128 GB 16 GB with 4GT	1 TB
Windows Server 2003 R2 Enterprise Edition Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition	64 GB 16 GB with 4GT	1 TB
Windows Server 2003 R2 Standard Edition Windows Server 2003, Standard Edition SP1 Windows Server 2003, Standard Edition SP2	4 GB	32 GB
Windows Server 2003, Datacenter Edition	128 GB 16 GB with 4GT	512 GB
Windows Server 2003, Enterprise Edition	32 GB 16 GB with 4GT	64 GB
Windows Server 2003, Standard Edition	4 GB	16 GB
Windows Server 2003, Web Edition	2 GB	Not applicable
Windows Small Business Server 2003	4 GB	Not applicable
Windows Compute Cluster Server 2003	Not applicable	32 GB

HW - Windows Server 2003支持多大内存

Windows Server 2003 Enterprise Edition(企业版32位)最大内存支持

2009年01月09日 星期五 05:11 P.M.

Windows Server 2003 Enterprise Edition(企业版)
* 支持8节点集群、NUMA；支持8路SMP
* 内存支持: (i386)32位版支持32GB内存
(X64) 64位版支持64GB内存

windows 2003 默认只支持小内存模式(最大3G)大于3G需要编辑Boot.ini加 /pae 参数开启大内存模式才能支持3G以上内存,按以上操作编辑Boot.ini重新启动仍有问题就是你内存兼容有问题.下面给出一个2003 boot.ini 的例子:

[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect /usepmtimer /NoExecute=OptIn /PAE





Windows Server 2003 Web版:为快速开发、部署Web服务与应用程序，提供Web托管与服务平台。支持2路SMP(对称多处理)系统、2GB内存。
Windows Server 2003标准版:面向中小型企业和部门级应用。支持4路SMP、4GB内存。
Windows Server 2003企业版:适合中心与大型组织使用，有32位和64位两个版本。支持8节点集群、NUMA；支持8路SMP，其中32位版支持32GB内存，64位版支持64GB内存。
Windows Server 2003数据中心版：面向要求强伸缩性和高可用性的企业，有32位和64位两个版本。32位版支持32路SMP、64GB内存；64位版支持64路SMP、512GB内存；两个版本均支持8节点集群、NUMA

要启用 Windows 2003 支持大于4GB的物理内存，必须将参数 /pae 添加到 boot.ini 文件中。

服务器刚刚购回来时就发觉这个问题，为什么好好的4G内存主板剧只识别成3G呢，三返四次修改BIOS也只能让主板识别成3.3G及3.5G左右，真烦人。。。
原来是有的服务器都有内存空洞,所以3.3G-3.8G都是正常的，这部分空洞的内存作为硬件的消耗了，差的太多就要升级主板的BIOS和阵列卡的firmware就可以了。
如果是XP或2003系列的话还要在BOOS.INI里加上/PAE参数才能正常访问扩展内存。超过1G的话还要加上/USERVA=3030参数才能最优化配置虚似内存。

由win2003 SP1中一个重要的安全功能－“数据执行保护功能（简称：DEP）”产生的。
你可以在“控制面板→系统→高级→设置→数据执行保护”中找到它。
当你在这两项中进行切换时，“/NoExecute=OptIn”也会变成“/NoExecute=Optout”。
注意：此功能需要硬件支持：包括AMD Athlon 64、AMD Opteron、Intel的安腾和安腾2，据说nVIDIA、VIA、全美达等公司也计划在其芯片中加入该技术。建议普通用户不要去修改它，否则会引起系统运行不稳定。

/NoExecute=alwaysoff 就是关闭数据执行保护功能
/NoExecute=OptIn 表示选择的是第一项，就是“只为……”那项
/NoExecute=Optout 表示选择的是第二项


/noexecute=AlwaysOff时,相当于关闭了DEP和EVP功能,凡是被其阻止的程序都能正常运行

/NoExecute=OptOut --DEP被打开,且一切服务都使用dep


v如果你的服务器内存大于3G以上,系统是Win2003不支持3G以上时可以看看此文

概要
本文介绍物理地址扩展 (PAE) 和地址窗口化扩展 (AWE) 并解释它们如何协同工作。本文还将讨论超出 32 位操作系统所固有的 4 GB 范围的内存使用限制。
更多信息
PAE 提高了 IA32 处理器处理大于 4 GB 的物理内存的能力。Microsoft Windows 2000 Advanced Server、Microsoft Windows 2000 Datacenter Server、Microsoft Windows Server 2003 Enterprise Edition 和 Microsoft Windows Server 2003 Datacenter Edition 可以使用 PAE 来利用超出 4GB 的物理内存。若要启用 PAE，需要在 Boot.ini 文件中使用 /PAE 参数。

注意：只有在服务器使用热添加内存设备时，Windows Server 2003 Enterprise Edition 和 Windows Server 2003 Datacenter Edition 才自动启用 PAE。在这种情况下，不需要在配置为使用热添加内存设备的系统上使用 /PAE 开关。在其他情况下，必须在 Boot.ini 文件中使用 /PAE 开关来利用大于 4GB 的内存。

典型情况是，在 Windows 2000 或 Windows Server 2003 下运行的进程最多可以访问 2 GB 的内存地址空间（假设未使用 /3GB 参数），其中一些内存是物理内存，另一些是虚拟内存。运行的程序越多（因而进程也越多），占用的内存地址空间也就越接近 2 GB 这一最大值。

当出现这种情况时，分页进程将显著增加并且会对性能产生负面影响。Windows 2000 和 Windows Server 2003 内存管理器使用 PAE 向程序提供更多的物理内存。这会降低对交换页面文件内存的需要，从而提高了性能。程序本身并不知道实际的内存大小。所有的内存管理和 PAE 内存分配都由内存管理器处理，与运行的程序无关。

当使用 /3GB 参数时，上述信息对于运行的程序有效。要求 3 GB 内存的程序更有可能让其所需的内存有更多部分在物理内存中，而不是在分页的虚拟内存中。这将增强那些能够使用 /3GB 参数的程序的性能。但例外情况是当 /3GB 参数与 /PAE 参数一起使用时。在这种情况下，操作系统将不使用任何超过 16 GB 的内存。此行为是由内核虚拟内存空间考虑导致的。因此，如果系统使用 Boot.ini 文件中的 /3GB 项重新启动，并且系统的物理内存超过 16 GB，则操作系统不使用额外的物理随机存取内存 (RAM)。重新启动计算机时如果不使用 /3GB 开关，将能够使用所有的物理内存。

AWE 是内存管理器功能的一套应用程序编程接口 (API)，它使程序能够寻址更多内存 — 超过标准 32 位寻址的 4 GB 内存空间。AWE 使程序能够将物理内存保留为非分页内存，然后将非分页内存部分动态映射到程序的内存工作集。此过程使内存密集型程序（如大型数据库系统）能够为数据保留大 量的物理内存，而不必交换分页文件以供使用。相反，数据在工作集中进行交换，并且保留的内存超过 4 GB 范围。此外，超出 4 GB 的内存范围对内存管理器是公开的，并且 AWE 通过 PAE 发挥作用。没有 PAE，AWE 就无法保留超出 4 GB 的内存。

以下是一个 Boot.ini 文件的示例，其中已添加了 PAE 开关：
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect /PAE


警告：Boot.ini 文件的内容根据您的配置而异。 有关更多信息，请单击下面的文章编号，以查看 Microsoft 知识库中相应的文章：
317526 (http://support.microsoft.com/kb/317526/) 如何在 Windows Server 2003 中编辑 Boot.ini 文件
总之，PAE 是 Windows 2000 和 Windows Server 2003 内存管理器的一项功能，它为请求内存的程序提供了更多物理内存。程序并不知道它正使用的内存中有些在大于 4 GB 的范围内，正如程序不知道它请求的内存实际上是在页面文件中一样。

AWE 是一个 API 集，它使程序能够保留大内存块。保留的内存是非分页的，并且只可以由该程序来使用。 有关 AWE 和 PAE 的更多信息，请单击下面的文章编号，以查看 Microsoft 知识库中相应的文章：
268363 (http://support.microsoft.com/kb/268363/) Windows 2000 中的 Intel 物理地址扩展 (PAE)
有关更多信息，请访问下面的 Microsoft 网站：
http://msdn.microsoft.com/library/psdk/sql/ad_1_server_1fnd.htm (http://msdn.microsoft.com/library/psdk/sql/ad_1_server_1fnd.htm)
http://msdn.microsoft.com/librar ... html/awewindata.asp (http://msdn.microsoft.com/librar ... tml/awewindata.asp)

如果向系统添加更多内存，BIOS 可能会认出安装在服务器中的全部物理 RAM，而 Windows 将只能认出部分 RAM。如果服务器具有启用的冗余内存功能或内存镜像功能，则全部剩余内存可能对 Windows 都不可见。冗余内存在某个内存块故障时为系统提供一个故障转移的内存块。内存镜像将内存块拆分为一个镜像集。两种功能都在 BIOS 中启用或禁用，而无法通过 Windows 访问。要修改这些功能的设置，您可能必须参考系统用户手册或 OEM 网站。另外，您可能必须联系硬件供应商。

例如，如果正在运行的系统安装了 4GB 的 RAM，随后又添加了另外 4GB 的 RAM，Windows 可能只识别出 4GB 或 6GB 的物理内存，而不是全部的 8GB。冗余内存功能或内存镜像功能可能在您未知的情况下就在新内存块上启用。这些症状类似于未将 /PAE 开关添加到 Boot.ini 文件时的症状。

	标准版	企业版
支持最大内存数量	4GB	32GB	(32bit)
	64GB	1TB	(64bit)
支持最大CPU数量	4	8	(32bit)
	4	8	(64bit)
服务器群集	否	是
网络负载平衡群集	是	是
内容索引	是	是
磁盘碎片整理工具	是	是
远程管理桌面	是	是
.NET Framework	是	是
Internet Information Services (IIS) 6.0	是	是
Microsoft Identity Integration Server 2003 (MIIS) 支持	否	是

EPM - Multi-language Installation

Before attempting to install Oracle EPM 11.1.1.2 Japanese version, user should set 'Region and Language' proper for displaying Japanese, including installing East language support, set region to Japan and something else like this.

Brent