• No results found

Installing the Siebel Management Server

In document D53912GC11_ag (Page 66-73)

Goals To install and configure the Siebel Management Server Time 20 – 25 minutes

Instructions:

In this practice, you will install and configure the Siebel Management Server. Only one Management Server is required to support all the Management Agents in an enterprise. The Siebel Management Server provides support for ADM and hosts the Siebel Diagnostic Tool.

1. Install the Siebel Management Server:

a. Using Windows Explorer, navigate to

D:\Labs\8.1_Install\Installers\Server\Siebel_Management_Server.

b. Double-click setup.exe. You would normally run this on the machine that was designated to run the Management Server.

c. Click Next in the Welcome screen.

d. Specify a directory of D:\OUAgent\mgmtsrvr and click Next. While it is not necessary to co-locate the Management Agent and Server, putting them in the same directory is

convenient for this course.

e. Once installation completes, the Siebel Management Server Configuration Tool runs automatically.

2. Configure the Siebel Management Server:

a. Enter these parameters to configure the Siebel Management Server, clicking Next to proceed through the configuration:

Parameter Value Purpose

Siebel Enterprise OUEnt Used to monitor a particular Enterprise.

Siebel Gateway Name Server Host Name

<Machine Name> Used to contact the Gateway Name Server.

Siebel Gateway

Name Server Port 2320 Port number on which the Gateway Name Server is listening for connections.

Siebel User

Account SADMIN Used to obtain information about the Enterprise or particular servers.

Siebel User Account Password - and confirm

SADMIN Used to obtain information about the Enterprise or particular servers.

Diagnostic Tool

User Account SADMIN Used to log in to the Diagnostic Tool. This user must also be able to log in to the Siebel application.

Diagnostic Tool SADMIN Used to log in to the Diagnostic Tool.

Oracle Internal & Or acle Academy Use Only

Lesson 8: Installing the Siebel Management Agent and Server Password

- and confirm RC2 Password

Encryption? Not selected Whether to use RC2 encryption rather than Oracle proprietary encryption to encrypt the Siebel user account password in the Management Server properties file.

RMI Registry Port 1099 Port on which the Management Server listens for connections.

Diagnostic Tool

HTTP Port 8080 Port used for the Diagnostic Tool; note that the default (8080) is used by both the Diagnostic Tool and the Update Server, so you will need to change this value for the Update Server.

JRE Home D:\jre_16010 The Management Server uses the Java Runtime Environment. The JRE must be installed separately as a prerequisite. This has been done for you on your machine. If you do not find the specified directory, browse for it in your machine; JRE versions may differ.

Authentication Type Database The authentication system used by the Management Server. It must match that of the Management Agent. The Siebel User you entered above must be entered in the authentication system used by the Management Server.

Security Adapter

Configuration File D:\OUAgent\mgmtsrvr\

bin\odbcsecadp.cfg

Which security adapter file to use to obtain

connection information to the authentication system.

The default file name is set according to the authentication type you selected. Recommended practice is to accept this default name. These files are located in the bin subdirectory of the installation directory during installation, and must be edited post-configuration.

SSL Type NoSSL Use SSL for all communication, local communication only (loopback; for example, when communicating with the Siebel Server), or none at all

Windows User

Account <machine

name>\SEBLSRV

The Siebel Management Server runs as a non-system Windows service, hence needs a Windows user who has permission to log on as a service Windows User

Account Password SEBLSRV The password used to log in as the Windows user.

Oracle Internal & Or acle Academy Use Only

is monitoring.

Server Type Siebel Server The Siebel Management Server can listen to Management Agents connected to other types of servers.

Configure Second

Agent Not selected You can register all of the Agents using the Configuration Tool, or register them later using the Perl scripts provided with the application.

Start the Management Server Now

Not selected The security adapter must be configured before starting the Management Server

3. Execute the configuration and complete the installation.

4. If necessary, click Next then Finish to exit the After Intallation dialog box.

5. Configure the security adapter for the Siebel Management Server:

a. Use Notepad to open D:\OUAgent\mgmtsrvr\bin\odbcsecadp.cfg.

b. In the [ServerDataSrc] section, change the DSConnectString value to OUEnt_DSN. This is the ODBC connection created by your server for communicating with your database. If you were on a machine that did not have this ODBC connection already configured, you would have to configure it manually.

c. Save and close odbcsecadp.cfg.

6. Perform additional configuration for the Siebel Management Server. Three Perl scripts need to be run to generate the XML files necessary to support the Siebel Management Server:

getservers.pl connects to the Gateway Name Server and obtains a list of Siebel Servers in the Enterprise to generate configuration.globals.xml. Once that script has been run,

makeagentconfig.pl reads the information and generates a list of agents connected to the Management Server and their connection information. Finally, admconfig.pl copies that information to the Management Server’s registry to support ADM. Running the Perl scripts requires a Perl parser. ActiveState ActivePerl has been installed on your machine.

a. Copy the two files configuration.globals.xml and configuration.agents.xml from D:\OUAgent\mgmtsrvr\pref\system to D:\OUAgent\mgmtsrvr\bin.

b. Select Start > Run.

c. Enter cmd and click OK to open a command prompt.

Course Note: All of the text strings used in this course are contained in text files, allowing

Oracle Internal & Or acle Academy Use Only

Lesson 8: Installing the Siebel Management Agent and Server

you to copy and paste the strings instead of having to type them manually. The strings used for this practice are contained in D:\labs\8.1_Install\Solutions\ManagementAgentAndServer\

managementServer.txt.

d. Enter the command:

set PATH=%PATH%;D:\OUses\siebsrvr\bin

This adds the Siebel Server executable directory to the PATH environment variable of the command line.

e. Enter the command:

cd D:\OUAgent\mgmtsrvr\bin

This puts you in the Management Server directory.

f. Make sure the Siebel Server service is running, and then enter the command:

d:\perl\bin\perl.exe getservers.pl –g <machine name> -u SADMIN –p SADMIN – l enu –e OUEnt

This should successfully generate configuration.globals.xml. Leave the command prompt open.

g. In Windows Explorer, navigate to D:\OUAgent\mgmtsrvr\bin, right-click configuration.globals.xml, and select Open.

h. Note that configuration.globals.xml includes the Enterprise name (OUEnt) and the Gateway Name Server host name (your machine name).

i. Close configuration.globals.xml.

j. Return to the command prompt and enter the command:

D:\perl\bin\perl.exe makeagentconfig.pl OUEnt

This should successfully generate configuration.agents.xml.

k. Use Notepad++ to open configuration.agents.xml:

i. In Windows Explorer, navigate to D:\OUAgent\mgmtsrvr\bin.

ii. Right-click configuration.agents.xml and select Open With > Choose Program.

iii. Click Browse.

iv. Navigate to D:\Program Files\Notepad++ and select Notepad++.

Oracle Internal & Or acle Academy Use Only

This generates deploy_OUEnt.bat, which is used to deploy ADM packages.

o. Copy the configuration files to their correct locations:

i. Copy configuration.globals.xml from D:\OUAgent\mgmtsrvr\bin back to D:\OUAgent\mgmtsrvr\pref\system, replacing the orginal file.

ii. Copy configuration.agents.xml from D:\OUAgent\mgmtsrvr \bin back to D:\OUsea\mgmtsrvr\pref\system, replacing the original file.

p. Return to the Services window and start the Siebel Management Server service. This creates the WEB-INF directory that will contain the agent configuration file.

Note: If you do not see the Siebel Management Server service listed, select Action > Refresh to refresh the window.

q. Copy configuration.agents.xml from D:\OUAgent\mgmtsrvr\bin to D:\OUAgent\mgmtsrvr\tomcat\webapps\DiagTool\WEB-INF

7. Return to the Services window and restart the Siebel Management Server service. This loads the configuration information you just copied.

8. Confirm that the Siebel Management Server is operating successfully.

a. Use Notepad to open D:\OUAgent\mgmtsrvr\log\ManagementServer.log.

b. Examine the log for the following:

i. At the top of the log, the security manager should start, and then a section listing SADMIN’s roles should be shown. If there is an error in getting SADMIN’s roles, ensure that the Siebel Server service is started, and that you correctly spelled the ODBC connection name in odbcsecadp.cfg.

ii. Near the bottom should be a series of messages updated every 30 seconds that state that the Management Server is “refreshing system preferences”.

c. Close the log.

9. Confirm that you can log in to the Siebel Diagnostic Tool using the user you entered during installation:

a. Start Internet Explorer.

b. Enter an address of http://<machine name>:8080/DiagTool. Because this is a Java application, case is important.

c. Enter:

User ID SADMIN

Password SADMIN

d. If you are asked whether you want Windows to remember your password, click No.

e. Click the arrow.

f. If your configuration is successful, you should see the screen below. Note that the Server and Component fields are populated. If they are not, review your configuration, as this indicates a problem with communications between the management server, management agent, and

Oracle Internal & Or acle Academy Use Only

Lesson 8: Installing the Siebel Management Agent and Server

Siebel Server:

g. Click the Event Log Analysis tab.

h. Enter OUSrvr as the server.

i. If you are asked whether or not to turn AutoComplete on, click No.

j. Click Submit. Note that you can review server event logs from the Diagnostic Tool.

k. Log out of the Diagnostic Tool. Because you have not configured SARM on your Siebel Server, you cannot perform Server or User analysis.

10. Stop the Siebel Management Server service.

11. Stop the Siebel Management Agent service.

Oracle Internal & Or acle Academy Use Only

Oracle Internal & Or acle Academy Use Only

Lesson 9: Silent Installation

In document D53912GC11_ag (Page 66-73)