1 Preparing For MetaSolv Solution

For best results installing this software product, Oracle recommends the following:

• Database tasks should be done by a database administrator who is familiar with Oracle software.

• Application server tasks should be done by a systems administrator who is familiar with Oracle WebLogic Server.

• For existing Oracle customers, the installation and configuration of the application server software and MetaSolv software should be done by an information technology specialist or another technical individual who is familiar with Oracle WebLogic Server and MetaSolv Solution.

• If you are a new customer installing for the first time, Oracle recommends that you contact Oracle Communications Consulting to set up the WebLogic Server and to migrate your data into the Oracle database.

Regardless of the platform you plan to use, considerable technical knowledge is required to set up and administer this software product. The application server needs a dedicated administrator who can oversee operations to ensure the system is running at its optimum capacity. This role is separate from that of the Oracle database administrator who maintains the database server and the integrity of the data.

This section contains information on tasks you must do or information you must review if you currently have a version of MetaSolv Solution that you plan on moving to the new release.

When upgrading to MSS 6.3.x, you must consider the following upgrade impacts:

• Database Software Changes

• WebLogic Server Changes

The following terms are used throughout this guide. They are basic terms necessary for the discussion of deploying an application intended for use over a network by many users.

Application server:

In a 3-tier client/server environment, the application server performs the business logic processing between the user's computer (first tier) and the database management system (third tier). A simple example is shown in Figure 1-1.

Figure 1-1 Application server

Description of "Figure 1-1 Application server"

Oracle WebLogic Server handles the interaction between the client, MetaSolv Solution, and the database.

The MetaSolv Solution software is deployed on the WebLogic application server, which facilitates communication between the client and the database. The following list shows the benefits of using an application server approach:

• Processing tasks are moved from the client workstations to the application server computer, which saves resources.

• More users can be supported, and you can set up your system so processing continues if a server fails.

• Delay between the application and the database server is minimized, increasing the efficiency for processing requests.

• Finite resources like database connections are managed in a more structured manner.

WebLogic Domain:

A domain is a group of application servers managed as a single unit. The domain contains at least one instance of WebLogic Server. If multiple server instances exist in the domain, one instance is designated as the administrative server, and the rest become managed servers. Managed servers are controlled from the administrative server console.

WebLogic Administrative Server:

The administrative server enables you to manage other servers in a domain. This server has a console that enables you to shut down and start up other servers, monitor the environment, and manage activities like security and transaction processing.

WebLogic Managed Server:

A managed server is under the control of the administration server.

WebLogic Clustering:

A cluster is part of a domain dedicated to some specific processing duty (for example, MetaSolv Solution processing). A cluster is different than a domain but is a subset of a domain. A cluster generally includes several server instances, and the servers work together as if they were one application. A single cluster or multiple clusters can exist in a domain, but you cannot spread a cluster across more than one domain. One advantage of clusters is their scalability; you can increase the number of servers in a cluster to handle increased processing needs. Clusters also give you high availability, which means if one server fails, another replaces it without the loss of data.

Client:

The client is the user workstation linked to MetaSolv Solution application so that a user can interact with the system to perform tasks. Some application code is loaded to the client to allow the execution of some MetaSolv Solution graphical features and other processing tasks.

JEE:

JEE is a standard for developing Java applications for a thin-client, multitiered environment. The conventions found in JEE help ensure applications are developed in such a way that communications are simplified between Java applications.

Machine or Computer:

The name of the physical computer that hosts an application server.

MetaSolv Solution contains three discrete software installation processes: database, application server, and client. The installation is completed in the following order:

1. Database installation

   For MSS 6.3.x, you must install Oracle Database Enterprise Edition. See Software Required to Install MetaSolv Solution for information on required software versions.

2. Application server installation

   The application server installation requires the most planning. You must decide which domain option you want for your installation and configure the application servers for the most benefit in terms of fail over, high availability, and scalability. Based on business and environment requirements, you should evaluate both hardware and software options for implementing your choice of the following domain options:

   • Single server

   • Administration server with managed servers in a cluster

   • Enable SSL

   You must determine which of these options applies to your business needs and meets the most secure operational fail over requirements.

   Oracle does not recommend the single server solution because it does not provide continuation of service if the server fails. There is no mechanism in this option to prevent the loss of data or service.

   For information on each of these options, see the documentation at:

   http://www.oracle.com/technetwork/middleware/weblogic/overview/index.html

3. Client installation

   The client files are bundled with the application server files in CAB files.

In a MetaSolv Solution installation, application files are divided among the following locations:

• Application server: MetaSolv Solution software that controls business logic and processing is loaded to a designated computer or computers. This software is designed to work with the Oracle WebLogic server software and improve the speed and efficiency of the information flow between the client workstation and the MetaSolv Solution database.

• Client workstation: The files loaded to the client workstation include executable files that allow the operation of MetaSolv Solution for the user interface and INI files that configure the software. Initially, these files are loaded onto the application server in CAB files.

• Citrix server (optional): If you are using a Citrix server, the client workstation files are loaded onto the Citrix server, and the client workstations use a Citrix browser to interact with MetaSolv Solution.

Figure 1-2 shows a simple MetaSolv Solution configuration.

Figure 1-2 Simple MetaSolv Solution configuration, showing where files are loaded

Description of "Figure 1-2 Simple MetaSolv Solution configuration, showing where files are loaded"

You can use a Citrix server to increase efficiency between the client workstation and the application server. In this configuration, the client workstation files are loaded to the Citrix server and a browser allows the user to access and use the application files on the Citrix server. The Citrix configuration is a good solution in cases where a wide area network (WAN) is used and users must communicate with the application server and database over great distances.

Figure 1-3 shows a MetaSolv Solution configuration with the Citrix server.

Figure 1-3 A MetaSolv Solution configuration, showing the Citrix server

Description of "Figure 1-3 A MetaSolv Solution configuration, showing the Citrix server"

Oracle has performed an appropriate testing cycle on the indicated platforms, specific software versions, and configurations indicated, and has confirmed that they have no adverse effect on MetaSolv Solution.

The following tables list certified software versions that can be used with MetaSolv Solution 6.3.x.

See "Minimum Technical Requirements" for a complete list and details of technical requirements.

Table 1-1 lists the certified software version for the database server.

Table 1-2 lists the certified software versions for the application server.

Table 1-3 lists the certified software versions for the workstation client.

Table 1-4 lists the software version information for the single sign-on functionality. Refer to the MSS Security Guide for more information.

Before you move MetaSolv Solution into production, you should run it in a test environment to ensure you understand how it works and to resolve any issues before you commit the application to your production computers. This document and other MetaSolv Solution documents explain how to set up for a production environment, but you can set up your test environment with some variations. The fail over requirements are not as strict for a test environment as they are for production.

For example, you can run MetaSolv Solution 6.3.x and MetaSolv Solution 6.2.x on the same test computer. You must keep each application separate and ensure that ports used for http communication, name services, and logging are unique for each instance. The Oracle client (tnsnames.ora) must be configured to connect to the appropriate database for each instance.

On UNIX, use separate users for each instance and set necessary configuration settings for each user. On Windows, you might need to alter some start scripts to ensure the correct paths are set for environment variables such as PATH, CLASSPATH, TNS.ADMIN, and so on.

To achieve optimum application server performance for individual business needs, load and performance testing in a test environment that represents your true production environment is required. The test environment should mimic how you use your production system, including the transaction mix, number of users, hardware and software infrastructures, database, network usage, and all other relevant factors. Setting up a test environment will allow you to determine the optimal application server settings that you should implement in your production environment for:

• Connection pool sizing

• Execute thread sizing

• Java memory management