Professional Documents
Culture Documents
D70539GC21 Ag
D70539GC21 Ag
Activity Guide
D70539GC21
Edition 2.1
August 2014
D87753
Copyright © 2014, Oracle and/or its affiliates. All rights reserved.
Disclaimer
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and
print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way.
Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization
of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document, please
report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United
States Government, the following notice is applicable:
Trademark Notice
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective
owners.
Authors
Customer Experience Curriculum Development Team
Publisher
Jobi Varghese
Time
30 - 40 minutes
Overview
In this practice you will explore the Siebel architecture, starting with the Siebel Gateway Name
Server (GNS) and working your way all the way up to the Siebel Web client.
Tasks
1. Explore the Siebel Gateway Name Server service and installation directory.
Time
30 - 50 minutes
Overview
In this practice you will use the Enterprise Explorer to familiarize yourself with components and
component groups. You will then create your own custom component group for use in these
Tasks
1. Use the Siebel Developer Web (thick) Client to log in to the server database.
This is a useful technique when changing parameters, as you can stop and start
components, including any desired application object managers (AOMs), without having to
log out of the AOM you are configuring. Remember that the Siebel Gateway Name Server
must be running in order to be able to access the Server Configuration or Management
screens.
a. If necessary, start the Siebel Call Center Developer Web Client.
1) Double click the desktop shortcut: Siebel Call Center – ENU.
2) Enter:
User ID SADMIN
Password SADMIN
Connect to Server
3) Click OK.
Notice that the address bar reads http://localhost:8080/start.swe. Notice that a port
is listed, while an application name is not. This is a good indicator that you are
using the thick client. However, it is not a guarantee, as a network administrator
might configure the Web server to provide a similar result. For the classroom
environment, check for the port number when you need to verify that you are using
the thick client. In general, it is safer to select Help > Technical Support from within
the application and check whether the SRF is local (for example, in the Client
directory on your classroom machine) or remote (for example, in the siebsrvr
directory on your classroom machine).
2. Explore the enterprise.
a. Navigate to > Administration - Server Configuration > Enterprise Explorer. The explorer
tree is shown in the left pane. The top level of the explorer tree is the enterprise.
Throughout the course, you will be using the Administration - Server Configuration and
Administration - Server Management screens. Consider using Tools > User
Preferences > Tab Layout to make these tabs visible when you log in. (Deselect the
Hide checkbox next to items 44 and 45).
g. Notice there are already component groups currently enabled on your server, such as
Auxiliary System Management, Siebel Call Center, System Management, and more.
Note that you cannot enable or disable component groups from this view.
h. Now select the top-level Component Groups folder. Notice most of the component
groups in this view are enabled. These are component groups enabled for the
enterprise, rather than component groups enabled on the server.
i. Explore the other nodes of the Enterprise Explorer, not making any changes. In the
next few steps you will create a custom component group and a custom component.
3. Create a custom component group and a custom component definition.
You are creating a custom component group to contain a component definition for your new
custom application object manager, so you can safely modify its parameters without risking
making unrecoverable changes to your enterprise.
a. Navigate to Administration > Server Configuration > Enterprises.
The Enterprises > Component Groups view should be displayed by default.
b. Select the Component Groups applet.
c. Create a new Component Group with:
Name SSA Example Group
Alias SSAExampleGroup
Description Custom Component Group
n. Verify that your newly-created component now appears in your custom component
group.
1) Click the Component Groups tab.
2) Query for SSA Example Group.
3) Confirm that SSA Example Component is listed as a component in the SSA
Example Group.
Time
30 - 50 minutes
Overview
In this practice you will make changes to various parameters and verify functionality after
completing the effective requirements for each parameter
Tasks
1. Explore the Effective setting by changing some of your component’s parameters. Once
d. Conduct a query in the Component Parameters section for parameters including the
term “Security Adapter”.
Recall that since you disabled the automatic trailing wildcard, your query will have to be
of the form Security*.
The two parameters returned determine the Security Adapter Mode, which determines
which DLL will be used for application security, and the Security Adapter Name, which
is the name of the profile used to pass parameters to the DLL.
Time
15 - 20 minutes
Overview
In this practice, you enable Open UI in a custom application object manager (AOM) and verify
access without Internet Explorer.
Tasks
1. Enable Open UI in the thin client
d. Log in using:
User ID SADMIN
Password SADMIN
e. Verify you are able to login to Open UI, you should see the Siebel Home tab open by
default.
Time
5 - 10 minutes
Overview
In this practice you will first back up Enterprise configurations to the siebns.dat file. Then you
will cause an intentional error in the configuration of the Enterprise and then restore it to its
previous correctly configured state.
Tasks
Time
25 - 30 minutes
Overview
In this practice, you will use the Administration - Server Management screen to monitor the state
of the system. You will intentionally cause a problem in the system, and monitor how it appears
on the screen.
Tasks
k. Notice that all of the components except the e-Service Object Manager are either
online or running. These are the two “normal” states of components; any other state
should be investigated. (The e-Service Object Manager was set to Manual Start for this
course to preserve system resources).
l. Explore the Administration - Server Management > Tasks view.
This view shows all of the tasks that have run in the enterprise, with a maximum history
of 20 exited tasks per component (configurable using the advanced Maximum Historic
Tasks parameter of the Server Manager component). It also shows the logs,
parameters, state values, and statistics for each task.
m. Notice the Server Manager task; this is being used to support your navigation on the
Server Management screen.
n. Explore the Administration - Server Management > Sessions view.
This view shows a history of the user sessions that have run, up to 100 sessions
(configurable using the UsageTracking Session Cache Size parameter of the Server
Manager component). Note that it shows components Server Manager, SRBroker, and
SRProcessor sessions in addition to AOMs.
Time
10 - 15 minutes
Overview
In this practice, you will explore creating job templates and invoking and monitoring jobs. Note
that it is not necessary to create a job template before creating a job, but in this practice you will
create the template first so you can see how it appears in the list of batch components you can
run.
Time
15 - 20 minutes
Overview
In this practice you will familiarize yourself with the Siebel command-line interface.
Because of the importance of typing the commands correctly for the server manager, all of the
commands you will enter in this practice are contained in the file
Throughout this practice, you will frequently enter similar commands with almost-identical
formats. The keyboard up and down arrows can be used to move backwards and forward
through the server manager history buffer, and the right and left arrows move the cursor within
the current command. This can save you quite a bit of typing or cutting-and-pasting.
Tasks
1. Verify that the Siebel Gateway Name Server and Siebel Server services are both running.
The command-line interface can be used with only the Siebel Gateway Name Server
running. In this case, it is possible to perform enterprise-level operations such as setting
enterprise-level parameters, assigning servers to server groups, or enabling component
groups on servers. However, in this case it cannot set server- or component-level
parameters.
a. Return to or, if necessary, start the Services application by selecting Start >
Administrative Tools > Services.
b. In the Services window, confirm that both the Siebel Gateway Name Server and Siebel
Server [OUEnt_OUSrvr] services have a status of Started.
c. If either service is not started, right-click it and select Start from the context menu. Be
sure to start the Siebel Gateway Name Server before starting the Siebel Server.
2. Open a command prompt and change to the Siebel Server’s bin directory.
The command-line server manager is also available in the Gateway Name Server’s bin
directory.
a. Select Start.
b. In the "Search programs and files" field enter cmd and press Enter.
c. Verify that a command prompt is shown:
Time
5 - 10 minutes
Overview
In this practice, you will run a sample job from the command line, then run it from a script. This
will familiarize you with common job-based server administration tasks.
Tasks
Time
20 - 25 minutes
Overview
In this practice you will explore configuration files associated with the Siebel Enterprise,
including eapps.cfg, lbconfig.txt, gtwycfg.cfg, srvr.cfg, and uagent.cfg.
Tasks
Time
10 - 15 minutes
Overview
In this practice, you will first explore the uagent.cfg configured for the classroom image, and you
will then explore the tools.cfg configured for this classroom image.
Tasks
Time
50 - 90 minutes
Tasks
1. Enable AOM cache logging for the Siebel Call Center object manager.
This event was chosen because it provides clear, easy-to-read logs without having to
restart the component or server. Every component has dozens (or even hundreds) of
possible event types to log.
a. Ensure that the Siebel Gateway Name Server and Siebel Server services are running.
1) If necessary, start the Services application by selecting Start > Administrative
Tools > Services.
2) In the Services window, confirm that both the Siebel Gateway Name Server and
Siebel Server [OUEnt_OUSrvr] services have a status of Started.
3) If either service is not started, right-click it and select Start from the context menu.
Be sure to start the Siebel Gateway Name Server before starting the Siebel
Server.
b. Ensure that any Siebel clients from previous practices have been closed.
This ensures the caches will behave as described in this practice.
c. Start the Siebel Call Center Developer Web Client, connecting to the Server database.
1) On the desktop, double-click the Siebel Call Center - ENU shortcut.
2) Enter:
User ID SADMIN
Password SADMIN
Connect to: Server
Enable Siebel QuickStart <unchecked>
3) Click OK.
d. Navigate to Administration - Server Configuration > Servers > Components.
Time
10 - 15 minutes
Overview
In this practice, you will first enable client-side logging. You would normally do this on the client
machine. Client-side logging works for all client types. Once you have explored client-side
logging, you will explore additional options available to users of Siebel Open UI.
Time
15 - 20 minutes
Overview
In this practice, you will create a new event notification profile, and then generate an event to
confirm that the Siebel application is correctly notifying you of system events.
Tasks
1. Create a new event notification profile
Time
25 - 30 minutes
Overview
In this practice you will first enable SARM for an individual component on the server. This is
useful in situations where you suspect that a single component (such as an Application Object
Manager) is causing performance problems, and you do not want to be overwhelmed with
extraneous data. You will next enable SARM for the server itself and observe the differences in
Tasks
1. Enable SARM for the Siebel Call Center Object Manager (SCCObjMgr) component.
Since you will be logged into Siebel Call Center to do this, this guarantees that SARM data
will be generated.
a. If necessary, start the Siebel Call Center Web Client:
1) Select Start > Programs > Internet Explorer
2) Enter Address = http://<machine name>/callcenter_enu.
3) Enter:
User ID SADMIN
Password SADMIN
4) Click the blue arrow.
b. Navigate to Administration - Server Configuration > Servers > Components >
Parameters.
c. Select the Call Center Object Manager (ENU) component.
d. Query for Parameter = SARM.
e. Notice that the only parameter returned is SARM Granularity Level.
f. In the lower right, in the applet labeled SARM Granularity Level in the lower right,
notice that this change is effective immediately; SARM is activated as soon as you set
this parameter to a nonzero value.
g. Set Value = 2 and step off the record to save it.
This level will store detailed SARM information in the SARM file.
h. At the top of the Component Parameters applet, click Hidden.
i. Notice that SARM Enabled = False. This parameter is obsolete.
j. Notice that SARM Memory Size Limit = 4,000,000. You should not need to change this
parameter, which is why it is hidden.
k. Click Advanced.
Copyright © 2014, Oracle and/or its affiliates. All rights reserved.
Time
20 - 25 minutes
Overview
In this practice, you will experiment with the SARMQuery tool. SARMQuery has a large number
of options; you will explore a subset of these.
Practice Hint: Throughout this practice, you will be entering commands with almost-identical
formats. The keyboard up and down arrows can be used to move backwards and forward
through the command shell history buffer, and the right and left arrows move the cursor within
Tasks
1. Access the SARMQuery tips and help options. These are useful when first starting with
SARMQuery.
a. If necessary, open a command prompt be selecting Start > All Programs > Accessories
> Command Prompt.
b. Enter:
set PATH=%PATH%;D:\OUses\siebsrvr\bin
c. This adds the Siebel Server executables directory to the PATH environment variable.
d. Enter:
cd D:\OUses\siebsrvr\log
Recall that this is the directory containing all of your server-generated SARM files.
Choosing the log directory minimizes your typing because you don’t have to qualify the
SARM file names.
e. Enter:
SARMQuery
Case is not important.
f. Notice that SARMQuery provides you with a synopsis of command options.
g. Enter:
SARMQuery -tips
h. Notice the large number of tips listed. You could redirect this output to a file using the >
outputfile.txt suffix to examine this in a more convenient form. You will see a different
method for saving the output in a subsequent step.
i. Enter:
SARMQuery -help
j. Notice that this provides a much more robust help dialog, but there is so much
information it is hard to parse.
Time
20 - 25 minutes
Overview
In this practice you will first explore the Browser Health Check for both the Siebel Web Client
(thin client) and Siebel Developer Web Client (thick client). You will then remove the ActiveX
controls from Internet Explorer's cache and use the as-delivered predeploy.htm file to reinstall
them.
Time
20 - 30 minutes
Assumptions
This practice assumes you created a custom application object manager and assigned it to the
Sales virtual directory, so http://<machine name>/sales_enu should support Siebel Open UI. If
you did not perform that lab, configure Siebel Call Center to support Open UI:
• Navigate to Administration - Server Configuration > Enterprises > Component
Definitions.
Overview
In this practice, you will explore options for managing Siebel Open UI. While Siebel Open UI
should run on "any standards-compliant browser", you should be able to check whether or not a
browser is standards-compliant. Also, as the Siebel Open UI scripts are updated on the server,
you may need to clear the browser cache on the client or mark the files as expired on the web
server to force the updated files to be re-downloaded to the client. You will perform these steps
for the classroom image software. (Google Chrome and Microsoft Internet Information Services
(IIS)).
Note that many web sites exist to check whether a browser is standards-compliant. For
example, http://html5test.com/results/desktop.html or http://www.acidtests.org. Wikipedia
provides a table of which browser supports which version of JavaScript at
http://en.wikipedia.org/wiki/JavaScript. Unfortunately, most browsers support features rather
than version numbers so it can be hard to tell. The HTML5test web site provides the most
comprehensive lists of features supported by each browser.
Tasks
1. Test clearing the browser cache to load updated files.
a. Log in to the Siebel Open UI Web Client.
1) Select Start > All Programs > Google Chrome > Google Chrome.
2) Enter Address = http://<machine name>/sales_enu.
3) Enter:
User ID SADMIN
Password SADMIN
4) Save alarm.js.
5) Minimize Notepad++.
m. Log back in to the Siebel Web Client.
1) Select Start > All Programs > Google Chrome > Google Chrome.
2) Enter Address = http://<machine name>/sales_enu.
Copyright © 2014, Oracle and/or its affiliates. All rights reserved.
1) In the upper right, click the "Customize and control Google Chrome" icon .
2) Select Tools > Clear Browsing Data.
3) Verify that "Obliterate the following items from" = The past hour.
4) Verify that only "Empty the cache" is selected.
5) Click Clear browsing data.
6) Close the Settings tab.
p. If necessary, return to the Siebel Call Center tab.
q. Navigate to a different page, then back to the Home page.
1) Right-click anywhere in the browser window and select Inspect Element.
2) In the Property Inspector (bottom) pane, click the Sources tab.
3) Click Show Navigator.
4) If alarm.js is already open, close it.
5) Under sales_enu/23030/scripts, select alarm.js.
6) Notice that the updated file still isn't loaded.
Browsers cache information in two ways: On the filesystem and in memory.
Clearing the cache cleared the filesystem, but not from memory. You must clear
both the filesystem and memory to force Google Chrome to read the new file.
2. Explore techniques for clearing both the browser cache and memory.
a. Manually clear the browser cache and memory.
1) From the application-level menu, select File > Log Out.
2) In the upper right, click the "Customize and control Google Chrome" icon.
3) Select Tools > Clear Browsing Data.
4) Click Clear browsing data.
5) Close the Settings tab.
Copyright © 2014, Oracle and/or its affiliates. All rights reserved.
Time
25 - 30 minutes
Overview
In this practice, you will use the cfgmerge utility to compare two enterprise configuration files to
produce a parameter migration script. You will then examine the parameters that will be
changed when we run the migration script. Note that in the classroom we have only one Siebel
Enterprise and server setup. You will simulate merging with a second Enterprise by using two
Tasks
1. Create a siebns.dat file backup of the current Siebel Enterprise configuration.
a. If necessary, start the Siebel Developer Web Client, connecting to the Server
database.
1) Double click the desktop shortcut: Siebel Call Center – ENU.
2) Enter:
User ID SADMIN
Password SADMIN
Connect to Server
3) Click OK.
b. In the Siebel Developer Web client, navigate to Administration - Server Configuration >
Enterprise Explorer.
c. Click Backup Enterprise.
d. If necessary, open Windows Explorer.
e. Navigate to D:\OUses\gtwysrvr\ADMIN.
f. Sort by the date modified column, (to make it easier to spot your backup file) and
confirm that there is now a file named siebns.dat.<timestamp>, for example,
siebns.dat_20140619_231253.
Time
25 - 30 minutes
Overview
In this practice, you will review the Siebel migration script in a text editor. You should become
familiar with how each component definition is compared and how it is displayed in the script
Tasks
1. Review the migration script.
a. Right click the output_file.cmd and select Edit with Notepad ++.
b. Examine the file looking for any recommendations.
c. Notice that many of the component definitions are showing no recommendations.
When no recommendation is found the migration script will show a block such as this:
; Merging component definition SMObjMgr_enu
;
; ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
; //////////////////////////////////////////////////////////
;
; //////////////////////////////////////////////////////////
; ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
;
d. Review the recommendation near the top for "enterprise OUEnt".
e. Notice it is listed with a recommendation to update the MaxThreads parameter.
; Merging enterprise OUEnt
;
; ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
; //////////////////////////////////////////////////////////
;
; Value of parameter MaxThreads in the source configuration:
30
Copyright © 2014, Oracle and/or its affiliates. All rights reserved.
; //////////////////////////////////////////////////////////
; ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
;
You can also run the migration script when logging into the srvrmgr program by using
the /i or -i flag and specifying the input file name along with the other login parameters.
Copyright © 2014, Oracle and/or its affiliates. All rights reserved.
Time
30 - 40 minutes
Overview
Tasks
1. Enable the ADM, Workflow, and EAI component groups to support ADM.
The ADM and EAI component groups are only used when you are working with an
orchestration environment. The Workflow component group should be enabled for file-
based imports and exports.
a. If necessary log on to the Siebel Call Center Web Client (thin client).
1) Select Start > All Programs > Internet Explorer.
2) Set Address = http://<machine_name>/callcenter_enu.
3) Enter:
User ID SADMIN
Password SADMIN
4) Click the blue arrow.
b. Navigate to Administration - Server Configuration > Enterprises > Component Groups.
c. In the Component Groups (middle) applet, query for Name = ADM.
d. In the lower right applet, click Enable.
If the Enable button is disabled, check to see whether the component group is already
assigned to and enabled on the server.
e. In the Component Groups applet, query for Name = Workflow.
f. If necessary, in the lower right applet click Enable.
g. In the Component Groups applet, query for Name = EAI.
h. If necessary, in the lower right applet click Enable.
Time
15 - 20 minutes
Overview
In this practice, you will practice adjusting the parameters related to tuning Siebel Web clients.
Tasks
1. Ensure that the browser cache is enabled, has enough space, and maintains the cache
between sessions:
l. Click OK.
d. Set the View Cache Size to 0 and click the Save button.
e. Log out of Siebel Call Center and close Internet Explorer.
Copyright © 2014, Oracle and/or its affiliates. All rights reserved.
.
6) Click Set Common Headers in the top right corner.
7) Verify the "Expire Web content" checkbox is selected and set the content to expire
after 7 days.
Time
15 - 20 minutes
Overview
In this practice, you will explore other tuning options discussed in the lecture.
Tasks