Beruflich Dokumente
Kultur Dokumente
Three-Tier Architecture
SmartPlant Materials uses "three-tier-architecture" technology with Oracle 11g R1 Fusion
Middleware.
Client Tier
You access the application server through an HTTP request. That is, you enter a URL or
bookmark in an Internet browser. The GUI (graphical user interface) is run as a Java applet. The
applet communicates with the application server by HTTP or socket connection, sending user
input to the application server and receiving representation instructions from the application
server.
Middle Tier
The application server runs the Oracle Forms and Reports modules that contain part of the
SmartPlant Materials business logic. The application server receives user input from the client tier
and returns instructions to the user. The client and middle tiers upload and download functionality
to exchange complete files from one file system to the other. The application server connects via
SQL*Net to a database to receive user data or system messages, and to send requests or user data
to update the database.
Database Tier
The database contains objects to store the SmartPlant Materials data, the user and system data
itself, as well as the second part of the SmartPlant Materials business logic.
Upgrade Prerequisites
Version 6.3 Version 7.0
SmartPlant SmartPlant
Materials 2008 Materials 2011
6.3.8 SP7 7.0.0 SP0
This
version/service
pack is the
minimum
prerequisite for the
Release 7
migration.
For more information about service packs and upgrades, see the How to Install a SmartPlant
Materials Service Pack document.
Internationalization
Database creation in SmartPlant Materials is done through the use of scripts, which specify the
character set options. SmartPlant Materials supports a homogeneous configuration. For more
information, see the Multi-Language Support document that is delivered with SmartPlant
Materials.
Windows 2003/2008 Server 32-bit environments are not supported for SmartPlant Materials
2011 7.0.
All domain verified user names and passwords must use ASCII7/English characters. Oracle
does not support non-ASCII / English characters in domain user names or passwords and will
not work. This limitation is an Oracle limitation, not Intergraph's.
The following graphic shows the configuration of the application server, database server, and
client.
Configure the application server and database server to be in the same domain. The computers
should also be physically close to each other.
During installation, turn off virus scanners and virtual machine services. Restart these
services after the installation.
Required Parts
Oracle WebLogic Server 11gR1 (10.3.2) Generic V18594-01
Oracle Portal, Forms, Reports and Discoverer 11g (11.1.1.2.0) for Microsoft Windows x86
(64-bit) (Part 1 of 4) V18785-01 Part 1 of 4
Oracle Portal, Forms, Reports and Discoverer 11g (11.1.1.2.0) for Microsoft Windows x86
(64-bit) (Part 2 of 4) V18785-01 Part 2 of 4
Oracle Portal, Forms, Reports and Discoverer 11g (11.1.1.2.0) for Microsoft Windows x86
(64-bit) (Part 3 of 4) V18785-01 Part 3 of 4
Oracle Portal, Forms, Reports and Discoverer 11g (11.1.1.2.0) for Microsoft Windows x86
(64-bit) (Part 4 of 4) V18785-01 Part 4 of 4
Oracle Fusion Middleware Repository Creation Utility 11g (11.1.1.3.0) for Microsoft
Windows (32-bit) V20970-01
Installation Prerequisites
4 GB RAM on the application server
80 GB hard disk for SmartPlant Materials and Oracle (approximate)
DVD-ROM drive access, either locally or through a network connection
Total Page file size (Virtual Memory) must be 1.5 GB.
Software Prerequisites
Adobe Reader 8 or later compatible version, downloadable from the Adobe website (required
to view the Software License Agreement and Printable Guides)
On the Oracle Application Server, we require Microsoft Excel 2007. Excel is required for all
Import/Export features of SmartPlant Materials.
The SmartPlant Materials database server must be installed on a single, dedicated server
without other production applications running on the same server hardware.
You must run two servers minimum because the 11g Fusion Middleware (SmartPlant
Materials application server) and the 11g R2 Database (SmartPlant Materials database server)
are not supported by Intergraph to run on a single machine.
To use SmartPlant Materials with Redwood Cronacle, your server must be supported by
Redwood.
The configuration is tightly related to the number of concurrent users working on the system.
Refer to Oracle documentation for detailed information.
Required Parts
Oracle Database 11g Release 2 (11.2.0.1.0) for Microsoft Windows x64 (64-bit) (Part 1 of 2)
V20610-01 Part 1 of 2
Oracle Database 11g Release 2 (11.2.0.1.0) for Microsoft Windows x64 (64-bit) (Part 2 of 2)
V20610-01 Part 2 of 2
Software Prerequisites
Adobe Reader 8 or later compatible version, downloadable from the Adobe website (required
to view the Software License Agreement and Printable Guides)
On the Installation Option screen, select Install database software only, and click Next.
On the Grid Installation Options screen, select Single instance database installation, and click
Next.
Use the Net Configuration Assistant from the Oracle Programs group.
Click Next.
Click Next.
SmartPlant Materials / Reference Data Classic Installation - Installs the Oracle Forms-based
part of SmartPlant Materials and SmartPlant Reference Data.
SmartPlant Reference Data Plus Installation - Installs the new SmartPlant Reference Data
software (.NET user interface). For more information, see the SmartPlant Reference Data Plus
Installation Guide.
SmartPlant MTI Installation - Installs the MTI components for integration.
SmartPlant Materials Release Notes - Opens the Release Notes document.
SmartPlant Materials Printable Guides - Opens a browser window and displays the Printable
Guides page, which is also available by clicking Help > Printable Guides in the software.
Our Web Site - Opens a browser window and displays the Intergraph SmartPlant Materials web
site.
Work at the top level of the folder structure (for example, D:\). The oradata folder contains the
standard folder structure for the SmartPlant Materials database files. By using a standard
folder structure, supporting the SmartPlant Materials installation is much easier, and you can
manipulate the database more easily.
All files used to create the database are stored in the scripts folder of this tree.
The <SPMAT7> that is used in our sample scripts represents the Oracle SID and can be
anything that you need. You should change this to a value to fit your needs (for example, HASE7).
We recommend that it have no more than six characters. For consistency's sake, rename the
SPMAT folder to match the SID name. Throughout the following steps, <SPMAT7> represents
the Oracle SID name.
###########################################
# Archive
###########################################
log_archive_format=ARC%S_%R.%T
###########################################
# Cache and I/O
###########################################
db_block_size=8192
###########################################
# Cursors and Library Cache
###########################################
open_cursors=1300
###########################################
# Database Identification
###########################################
db_domain=""
db_name=spmat7
###########################################
# File Configuration
###########################################
control_files=("D:\oradata\spmat7\ctl\control01.ctl",
"D:\oradata\spmat7\ctl\control02.ctl",
"D:\oradata\spmat7\ctl\control03.ctl")
db_recovery_file_dest=D:\oradata\spmat7\flash_recovery_area
db_recovery_file_dest_size=9413066752
###########################################
# Miscellaneous
###########################################
compatible=11.2.0.0.0
diagnostic_dest=D:\oradata\spmat7\diag
memory_target=828375040
###########################################
# Processes and Sessions
###########################################
processes=600
sessions=665
###########################################
# Security and Auditing
###########################################
O7_DICTIONARY_ACCESSIBILITY=TRUE
audit_file_dest=D:\oradata\spmat7\adump
audit_trail=db
remote_login_passwordfile=EXCLUSIVE
###########################################
# Shared Server
###########################################
dispatchers="(PROTOCOL=TCP) (SERVICE=spmat7XDB)"
###########################################
# System Managed Undo and Rollback Segments
###########################################
undo_tablespace=UNDOTBS1
###########################################
# PL/SQL
###########################################
utl_file_dir=D:\oradata\spmat7\utl
set ORACLE_HOME=<Your_ORACLE_HOME>
set ORACLE_SID=spmat7
set PATH=%ORACLE_HOME%\bin;%PATH%
<Your_ORACLE_HOME>\bin\oradim.exe -new -sid SPMAT7 -startmode manual
-intpwd manager1
<Your_ORACLE_HOME>\bin\oradim.exe -edit -sid SPMAT7 -startmode auto
-srvcstart system
<Your_ORACLE_HOME>\bin\sqlplus /nolog @d:\oradata\spmat7\scripts\
create11g_spmat7.sql
2. Modify the create11g_spmat7.sql file.
Use the Replace function of an editor to modify all settings in the same way as for the
create11g_spmat7.bat file.
3. Open initspmat7.ora in %\oradata\SPMAT7\scripts\, and modify/check all settings.
The parameter file that is placed in %\oradata\SPMAT7\scripts\ holds the database settings for the
database creation. Note that using the sample scripts creates an spfile in the
\%ORACLE_Home%\database folder from the specified parameter file. This spfile stores the
database parameters, which are used by the startup command, if no other parameter file is
specified.
Now you have modified the following three files and completed all preparations to create the new
instance:
File Folder
create11g_spmat7.bat %\oradata\SPMAT7\scripts check
create11g_spmat7.sql %\oradata\SPMAT7\scripts check
initspmat7.ora %\oradata\SPMAT7\scripts check
Check the log files from the database creation process. The log files are written to
%\oradata\SPMAT7\logs.
If the following error appears:
“ORA-00600: internal error code, arguments: [kkqctinvvm(2): Inconsistent
state space!], [], [], [], [], [], [], [], [], [], [], []”
See Oracle Support:
Bug 9442015: ORA-600[KKQCTINVVM(2): INCONSISTENT STATE SPACE!]
W/INTERLEAVED TRANSFORMATIONS
WURST7). We recommend that it have no more than six characters. For consistency's sake,
rename the SPMAT folder to match the SID name. Throughout the following steps, <REPO7>
represents the Oracle SID name.
###########################################
# Cache and I/O
###########################################
db_block_size=8192
###########################################
# Cursors and Library Cache
###########################################
open_cursors=300
###########################################
# Database Identification
###########################################
db_domain=""
db_name=repo7
###########################################
# File Configuration
###########################################
control_files=("D:\oradata\repo7\ctl\control01.ctl",
"D:\oradata\repo7\ctl\control02.ctl")
###########################################
# Miscellaneous
###########################################
compatible=11.2.0.0.0
diagnostic_dest=D:\oradata\repo7\diag
memory_target=250318528
###########################################
# Pools
###########################################
java_pool_size=0
###########################################
# Processes and Sessions
###########################################
processes=150
###########################################
# Security and Auditing
###########################################
audit_file_dest=D:\oradata\repo7\adump
audit_trail=db
remote_login_passwordfile=EXCLUSIVE
###########################################
# System Managed Undo and Rollback Segments
###########################################
undo_tablespace=UNDOTBS1
File Folder
create11g_repo7.bat %\oradata\REPO7\scripts check
create11g_repo7.sql %\oradata\REPO7\scripts check
initrepo7.ora %\oradata\REPO7\scripts check
Check the log files from the database creation process. The log files are written to
%\oradata\REPO7\logs.
Use startup and shutdown to start and stop the database instance.
C:\tnsping SPMAT7
Example 2:
SQL> select comp_name, status, version from DBA_REGISTRY where
comp_id='XDB';
COMP_NAME STATUS VERSION
-----------------------------------------------------------------
Oracle XML Database VALID 11.2.0.1.0
c. Install CATQM.
If the output is "no rows selected," you must proceed as follows:
Log on to SQL*Plus as user SYS and execute catqm.sql as described below.
The catqm.sql file creates the tables and views needed to run the XDB system.
Run this script like this:
Example:
SQL> show user
USER is "SYS"
SQL> @catqm.sql password xdb temp
You can determine whether or not Oracle XML DB is already installed. If it is installed,
then the following information is true:
User XDB exists. To check:
SELECT * FROM ALL_USERS where username like 'XDB';
3. Start a command window and go to the directory where the SmartPlant Materials dtd files are
located (%SPMAT_DB_InstallFolder%\sql\dtd\dbserver).
The graphic below shows the commands and responses explained in this step.
Connect via ftp to the database server:
>ftp <your-db-server>
BEGIN
SELECT
updateXML(
DBMS_XDB.cfg_get(),
'/xdbconfig/sysconfig/protocolconfig/ftpconfig/ftp-port/text()',0)
INTO newconfig
FROM DUAL;
DBMS_XDB.cfg_update(newconfig);
END;
/
COMMIT;
You can use the prepared scripts ftp_disable and ftp_enable to manage your active ftp
(D:\oradata\SPMAT7\scripts\useful\specials).
Use the following SQL*Plus statement to see if your DTD files were uploaded to the database
(connect as SYS):
SELECT a.path FROM path_view a where path like '%.dtd';
As a result, you get a list of available datatype definitions.
Press Enter.
6. Press Enter.
10. Check the import log files for errors, and press Enter when you have successfully performed
the import.
Leave the SQL*Plus session by typing exit, and check the log files for errors during
installation. The files are located in the installation folder. It is a best practice to keep these log
files for later analysis. Therefore, we recommend that you not use the same migration
directory twice in order to not overwrite existing log files by newer migrations on different
databases.
This installation step is complete.
SmartPlant 3D Data
In the sp3d_install folder, you can find a zipped script that can be used to fill standard SmartPlant
3D data for:
transfer types (SP3D 10.06)
sheet configurations (SP3D 10.07)
templates (SP3D 10.08)
The script prompts for the project ID and then inserts the standard data into this project or product
group.
13. The tablespace where this rollback segment is stored must have at least 1.4 * the size of the
largest table segment MB free, but not less than 1200 MB. This tablespace must be created
with the parameter SEGMENT SPACE MANAGEMENT MANUAL. (For further
information about rollback tablespaces, refer to the Oracle documentation).
You can find sample scripts for database creation in the
%SPMAT_DB_InstallFolder%\samples\oradata\SPMAT7\scripts\useful\migration\ folder.
14. The SmartPlant Materials application schema user M_SYS must not be currently connected to
the database.
15. No database logon/logoff triggers (other than the RDBMS standard ones) that could possibly
interfere with the SmartPlant Materials installation must exist in the database.
Start the migration script by entering @mig_SPMat70000.sql on the SQL*Plus command line.
Press Enter again; the migration progress is shown in the SQL window.
After all imports have terminated, check the log files for errors, and press Enter to continue the
migration.
When the migration is complete, check all log files for possible Oracle errors. The log files are
located in the installation_logs and import folders. Logs have the following extensions: *.log,
*.lst, and *.tmp. You can safely ignore all errors that refer to index creation with a specified
indexed column combination that is already indexed. It is a best practice to keep these log files for
later analysis. Do not use the same folder for more than one migration but copy it for each separate
database migration.
To allow Java access to local files, open a SQL*Plus session, and connect as SYS.
Enter the following command:
EXEC dbms_java.grant_permission('M_SYS','java.io.FilePermission','<your
PDB_REPORT_DEST_DB directory>','read,write,delete');
Example:
EXEC
dbms_java.grant_permission('M_SYS','java.io.FilePermission','C:\oradata
\SPMAT\utl','read,write, delete');
PL/SQL procedure successfully completed.
The path must match the PDB_REPORT_DEST_DB setting entered on the A.60.04 DBA
Settings screen in SmartPlant Materials. If you do not know this setting, you can perform this step
at any time later on.
Customer CIPs are saved to the installation_logs folder during migration. You may have to
modify and re-apply these procedures to the new SmartPlant Materials release.
The migration of your database is now finished and you can log on to your database.
Then, click SmartPlant Materials Application Server Installation to start the installation.
If you choose Custom and click Next, you can select the specific features that you want to
install.
SmartPlant Materials Printable Guides - Installs the necessary resources for the
SmartPlant Materials Printable Guides, which is a web page linking to the PDF
documentation. Select this feature if you want the Printable Guides to be available from the
SmartPlant Materials application server.
SmartPlant Materials 2011 Application Server Files - Contains all necessary components
to set up the application server for SmartPlant Materials. Note that the Online Reference
Library is not included automatically.
PDMS Macros - Installs additional macros to load PDMS files into SmartPlant Materials.
The setup procedure then asks for the location in which to install SmartPlant Materials.
Click Change, and specify an installation path that does NOT include spaces, for
example, c:\spmat7. Do not use the default installation location. Oracle Application Server
requires an installation path that does not have any spaces.
If there already is an existing installation of SmartPlant Materials, please use the same installation
folder for the upgrade location.
Click Install. The wizard now prepares your computer for the installation.
When the installation process is complete, the following screen appears. Click Finish to end the
installation program.
The SmartPlant Materials database server installation requires a running Oracle 11g R2 x64
database. The database server installation is a second step after the installation with
InstallShield. The 11g Fusion Middleware installation does not require the installation of
SmartPlant Materials on the database, nor does it require the installation of the database tier at
all. Intergraph recommends the installation of the database server, but if you have Fusion
Middleware installed without the database tier, you do not need to un-install the Fusion
Middleware.
On the Create Repository screen, select Create, and then click Next.
On the Schema Passwords screen, select Use same passwords for all schemas, and enter your
password. Then, click Next.
Click OK.
http://java.com/en/download/manual.jsp
On the Security Warning dialog box, click Run.
Click Finish.
On the Choose Middleware Home Directory screen, select Create a new Middleware Home.
Click Browse to specify the Middleware Home Directory.
If you have an Oracle Metalink account, you can enter your data here.
Then, click Next.
Select "I wish to remain uninformed...." if you do not want to be informed about security updates.
Then, click Continue.
On the JDK Selection screen, click Browse and select the home directory of your JAVA 64-bit
installation.
Click Next.
On the Install Windows Service screen, do NOT install Node Manager Service.
Click Next.
Before you exit the installer, you must clear the Run Quickstart option.
On the Select Installation Type screen, select Install Software - Do Not Configure.
On the Specify Installation Location screen, browse to select your Oracle Middleware Home.
On the Specify Security Updates screen, enter your information. Then, click Next.
During the installation, it may look like the computer is hanging. If this happens, please
wait.
Select the SPMAT FMW Wizard tab. Check all paths, and then click Configure Classic
Instance.
On the Select Domain screen, enter the password, and then click Next.
On the Specify Security Updates screen, enter your information. Then, click Next.
Click Next.
On the Specify Schema screen, enter the connect string, schema, and password, and then click
Next.
On the Specify Application OID screen, clear Use Application Level Identity Store.
If the webpage does not display, start the Admin Server from the Start menu.
Enter weblogic for the username, and then enter your password.
http://<your_application_server>:7001/console
Enter weblogic for the username, and then enter your password.
Click Deployments.
Click Install.
In the Path box, enter the iAS path, and select mar_jserv.war.
Then, click Next.
Click Next.
Select WLS_FORMS.
Click Next.
Click Finish.
Click Deployments.
Click Next.
Click Yes.
Click Next.
Click mar_jserv.
Click Testing.
Click mar_jserv.
If the server is not running, start it manually from the Start menu.
Click Start > Oracle Classic Instance - asinst_1 > Forms Services > Start Weblogic Server -
WLS_FORMS.
Enter weblogic for the username, and then enter your password.
Do not close this DOS window. Otherwise, the server process will stop.
Next, refresh the web site. WLS_FORMS is now running.
Click Deployments.
Click mar_jserv.
If you install a language other than the default language, you may get the message "Error
opening Oracle*Terminal file fmrweb." Make a backup of the resource file named
fmrweb<lang>.res. Copy the fmrweb<lang>_utf8.res file over fmrweb<lang>.res.
For example: If your forms server named NLS_LANG is: TRADITIONAL
CHINESE_TAIWAN.UTF8, copy the fmrwebzht_utf8.res file over fmrwebzht.res.
WebUtilArchive=frmwebutil.jar,jacob.jar
WebUtilLogging=off
WebUtilLoggingDetail=normal
WebUtilErrorMode=Alert
WebUtilDispatchMonitorInterval=5
WebUtilTrustInternal=true
WebUtilMaxTransferSize=16384
baseHTML=webutilbase.htm
baseHTMLjpi=webutiljpi.htm
pageTitle=SPMAT 7.0.0 with 11g
workingDirectory=C:\spmat7\fmx
form=logon.fmx
userid=m_login/m_login@spmat7
separateFrame=True
lookandfeel=Generic
width=1280
height=960
splashScreen=SPMaterials_SPlash2011.png
logo=AboutBx_Headere.jpg
background=SPMaterials_SPlash2011.png
[supplier_entry_spmat]
# Forms applet archive setting for other clients (Sun Java Plugin, Appletviewer, etc)
archive=frmall_2010.jar,spmaticon.jar
# Other Forms runtime arguments: grouped together as one parameter.
# These settings support running and debugging a form from the Builder:
otherparams= obr=%obr% record=%record% tracegroup=%tracegroup% log=%log%
term=%term% ssoProxyConnect=%ssoProxyConnect%
WebUtilArchive=frmwebutil.jar,jacob.jar
WebUtilLogging=off
WebUtilLoggingDetail=normal
WebUtilErrorMode=Alert
WebUtilDispatchMonitorInterval=5
WebUtilTrustInternal=true
WebUtilMaxTransferSize=16384
baseHTML=webutilbase.htm
baseHTMLjpi=webutiljpi.htm
pageTitle=SPMAT 7.0.0 Supplier Entry with 11g
workingDirectory=C:\spmat7\fmx
form=www_sup_entry.fmx
userid=m_login/m_login@spmat7
separateFrame=True
lookandfeel=Generic
width=1280
height=960
splashScreen=SPMaterials_SPlash2011.png
logo=AboutBx_Headere.jpg
background=SPMaterials_SPlash2011.png
(CONNECT_DATA =
(SID = SPMAT7)
(GLOBAL_NAME = SPMAT7.world)
)
)
Install WebUtil
Install the WebUtil Form
Download the JACOB – Java COM Bridge.
http://sourceforge.net/projects/jacob-project/files/jacob-project/1.10/jacob_1.10.zip/download
Edit <ORACLE_Middleware_HOME>\asinst_1\bin\sign_webutil.bat.
Edit
<ORACLE_Middleware_HOME>\asinst_1\config\FormsComponent\forms\server\webutil.cfg.
Connect to SQLPLUS.
Under Web Tier, click ohs1 > Oracle HTTP Server > Administration > Ports Configuration.
Restart the HTTP server: click ohs1 > Oracle HTTP Server > Control > Restart.
Click Restart.
The following screen appears to let you know that the Forms Services are running properly.
http://your_servername/forms/frmservlet?config=spmat7
The server starts in RUNNING mode. Do not close this DOS window.
The server starts in RUNNING mode. Do not close this DOS window.
The server starts in RUNNING mode. Do not close this DOS window.
Click Start > All Programs > Oracle Classic Instance – asinst_1 > Discoverer Services >
Start Weblogic Server – WLS_DISCO.
The server starts in RUNNING mode. Do not close this DOS window.
Printable Guides
The Printable Guides page is a web page with links to the PDF documentation. You can open this
page from the setup AutoPlay, or you can click Help > Printable Guides in the software.
Before using the Help > Printable Guides command, you must configure a database setting on
A.60.04 DBA Settings.
Enter a value for the ONLINE_REFERENCE_LIBRARY_URL as in the following example:
http://<your_application_servername>/web_entry/default.htm
You must have SmartPlant Materials running to accomplish this task.
Web Environment
A web environment (in the most simple configuration) inserts a new instance between the
database server and a client computer. While the database server remains, there is now an
application server on which Oracle Forms runs the application that used to run on the client
computer in client/server architecture. The user sits at a third computer with only a browser, which
is Java-enabled. This is the reason why this architecture is sometimes called three-tier technology.
Files going to and from the database server are there independent of the architecture, while files
that were going to and from the client computer in client/server mode now go to and from the
application server in web mode. Another step is needed for exchanging files between the
application server and browser client.
Most of the files to be processed by SmartPlant Materials must be placed on the database server.
Use FTP or a network share to copy the file to where you need it.
Application Server Files to SmartPlant Materials
Some import jobs transfer data into the database and can read files from the client. For that
purpose, the file is stored on the client and loaded into the database with the SQL*Loader. The
SQL*Loader is an Oracle tool that must be installed on the client computer.
Other files, placed on the client, are graphics that can be imported and stored within the database
with a click of a button on the associated screens. This is done with Forms functionality.
Note that the virtual path and the physical path end with a slash in the configuration file,
independent of the Windows or UNIX platform.
Procedure
1. To configure the web server to find the servlets in its repository, set the DBA setting called
SERVLET_PATH on A.60.04. If you install Oracle 11g Fusion Middleware as described in
this guide, the value is:
your_server_name/j2ee/servlet
The first part is your real server name. It could also be a domain name such as spmat.epc.com.
The second part is a constant string that you simply append to your server name. It is a virtual
path to the servlet classes, in the repository of the web server. Do not use an ending slash.
2. To tell the servlet where the document will be stored, set the DBA setting for destination path
information on A.60.04. The setting name depends on the SmartPlant Materials screen you
are on. Refer to Online Help to find the name. Here is an example for the value:
d:\spmat\uploaded_tags_and_terms\
You can use any path that exists on the application server. Directories that do not exist are not
created during upload.
A D
Administration of the Database • 40 Downloading (Receiving) Files from
Allowing for More than One Report Running SmartPlant Materials • 171
in Parallel (Optional) • 151
Analyze the Schema • 60 E
Applying Oracle Versions or Patches on Enabling the Web Server on the Application
Oracle 11g R1 Fusion Middleware • 7 Server • 171
Applying the SmartPlant Materials DTD Files Execute Prepared Database Creation Scripts •
• 44 34, 38
Assign a Static IP Address to the Application
Server • 83
F
B Fusion Middleware (Application Server) • 10
Back Up the Database • 53
G
C General Test of Forms • 155
Change Keyboard Mapping • 141
I
Client/Server Environment • 169
Comparing Client/Server to Web Import a Database Export Dump File • 54
Environment • 169 Important SmartPlant Materials Settings in
Configuration of the Oracle XML Database • the initrepo7.ora File • 37
42 Important SmartPlant Materials Settings in
Configure Classic Instance • 105 the initspmat7.ora File • 33
Configure the HTTP Port • 152 Install Forms, Reports, and Discoverer • 95
Configure the Oracle 11g Fusion Middleware Install Oracle 11g Fusion Middleware • 69
Repository • 72 Install Oracle 11g WebLogic 10.3.2.0 (64-bit)
Configure the Reports Server • 151 • 83
Configure WebLogic Server Install Oracle Database Software • 13
Deployment of mar_jservlet • 120 Install SmartPlant Materials Application
Create an Empty SmartPlant Materials Server Software • 61
Database • 32 Install SmartPlant Materials Database
Create an Entry for the SmartPlant Materials Software • 24
Home Page • 142 Install the WebUtil Form • 145
Create Oracle Fusion Middleware Repository Install WebUtil • 145
Database • 36 Installing and Configuring the Database
Create Path Mappings • 141 Server • 13
Create the Database • 36, 39 Installing SmartPlant Materials into an Empty
Create the Database Objects for WebUtil • Database • 48
148 Installing the Application Server • 61
Internationalization • 6