404 Not found

  • Profile / Purchases
  • €0.00 (0 items)

The Siebel Hub

Siebel Assignment Manager Quiz

This quiz is designed to test your knowledge of the venerable Siebel Assignment Manager. A very robust component with so many different options and functional capabilities, it deserves a place on the podium of top components. But it can catch everyone out from time to time – there are just so many options! If you are preparing to go into battle with Siebel Assignment Manager or just getting ready for an interview, then this is a good place to start.

Remember, you must register for free with LinkedIn and login before you will be able to start the Quiz.

Quiz Summary

0 of 11 Questions completed

Information

You have already completed the quiz before. Hence you can not start it again.

Quiz is loading…

You must sign in or sign up to start the quiz.

You must first complete the following:

Quiz complete. Results are being recorded.

0 of 11 Questions answered correctly

Time has elapsed

You have reached 0 of 0 point(s), ( 0 )

Earned Point(s): 0 of 0 , ( 0 ) 0 Essay(s) Pending (Possible Point(s): 0 )

  • Not categorized 0%

1 . Question

Assignment Rules are always executed in parallel with other rules for the same Assignment Object (True or False)

2 . Question

Which Assignment operating mode uses the Match method, followed by the Assign method?

  • Dynamic Mode
  • Interactive Mode

3 . Question

Which other Siebel Functionality can call Siebel Assignment Manager?

  • Siebel Appointment Booking System
  • Siebel Workflow
  • Siebel Scripting
  • Siebel Data Validation Manager
  • Siebel Email Response

4 . Question

What is Assignment Manager Reporting Mode?

  • The reporting mode stages the simulated assignments into a set of temporary results tables, known as reporting tables, rather than into the actual database tables.
  • The reporting mode prints a report of assignments which can be sent to the BI Publisher Server for processing
  • The reporting mode sends performance data to the Siebel Application Response Monitoring engine

5 . Question

In Email Activity Assignment Mode, Siebel Assignment Manager can assign inbound emails to agents (True or False)

6 . Question

In Assignment Criteria, there is a Criteria Inclusion Method called “Include All Matching”. Based on a criteria involving an Employee being able to speak multiple Languages, if the Employee speaks none of the Languages specified as Criteria Values, what will happen?

  • The Employee Candidate will fail the criteria. At least one Criteria Value must match.
  • The Employee Candidate will score 0 points but the criteria will not fail for this Candidate.

7 . Question

An Assignment Criteria can use the “Exclude” criteria inclusion method. Look at the following table and select the correct answer

The Employee Candidate does not speak Japanese, and the “Exclude” criteria passes. But what score is added to the Candidate Score?

8 . Question

If a criteria is “Required When Available”, this means…

  • In Compare to Object, a NULL value for the underlying Field will not cause the Criteria to fail
  • A NULL value for the underlying Field will not cause the Criteria to fail
  • In Compare Object to Person , a NULL value for the underlying Field will not cause the Criteria to fail

9 . Question

When creating Assignment Criteria Values, it is possible to use Wildcards (*, ?). True or False?

10 . Question

Assignment Criteria can, if correctly configured, accept a range of values. If a Criteria Value range is set to

From 1 To 9

Will the value 10 be in the range?

  • Yes, since the values are sorted lexicographically (in dictionary order) so 10 comes after 1 but before 9

11 . Question

What is the location of the rulecache.dat file if you have released Assignment Rules?

  • It can be found in SIEBSRVR_ROOT\bin
  • It can be found in SIEBSRVR_ROOT\ASSIGN
  • It can be found in SIEBSRVR_ROOT\WEBMASTER

how to create new components on siebel server.

hello all, I got two questions,1. I would like to know in a real time scenario why do we need to create a new component like wfprocess or assinmt mgr..etc.2. what is the process of creating them?on sitemap - server config admin- under enterprise I can see all the component groups listed.. like workflow management, assignment manager..etc and I can see their components listed below. there is a NEW button on component groups applet. can I riteaway click new and create a record? but that creates component groups... not a single component (like workflow process manager). I assume all the components as objects which has methods & parameters & perform some operation, if so how does siebel identify it as a component/method/process? how the logic will be build? (for exmple: workflow process manager/assignment manager.. logic to run the workflows) please let me know if any part of the question is unclear..i'll give more explanation.. i'm new to handling server jobs/components..I look forward...Thanks inadvace.Shafali.

User: spicehead-dqiibprk

Defending Against Evolving Ransomware Attacks

Author uma mahesh

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question .

Read these next...

Curated Snap! --  Moon Crater, Drunkonyms, Light-Powered Pacemaker, Emotion Recognition

Snap! -- Moon Crater, Drunkonyms, Light-Powered Pacemaker, Emotion Recognition

Your daily dose of tech news, in brief. Welcome to the Snap! Flashback: February 22, 1928: BASIC Co-Inventor Thomas Kurtz Born (Read more HERE.) Security News: • SMBs at Risk From SendGrid-Focused Phishing Tactics (Read more HERE.) ...

Curated Network cameras via POE switch or directly to NVR?

Network cameras via POE switch or directly to NVR?

Hello. It would be interesting to know what are the pros and cons connecting network cameras via POe switch vs. connecting them directly to the NVR? By the first method, only POE switch will connect to the NVR, and in theory, it should be able to see all ...

Curated Dear SpiceRex: Personalization versus Privacy

Dear SpiceRex: Personalization versus Privacy

In this series, we take questions that may be difficult for you to bring up in public and ask the Spiceworks Community on your behalf to give you the anonymity you want to find the answers you need. Interested? Send an email to [email protected]...

Curated Spark! Pro series - 22nd February 2024

Spark! Pro series - 22nd February 2024

Today in History: 1980 U.S. hockey team beats the Soviets in the “Miracle on Ice” In one of the most dramatic upsets in Olympic history, on February 22, 1980, the underdog U.S. hockey team, made up of college players, defeats the four-time defe...

Curated Disable MFA for 1 user on one windows 10 computer.

Disable MFA for 1 user on one windows 10 computer.

Hi I have a user that is sometimes in a place where phone or fob or any other mfa azure managed device is allowed.The device is secured away and remote access to it is disabled.I dont want to disable MFA for that user on all devices just one of the device...

  • System Administration Guide
  • What's New in This Release

10 Siebel Server Components and Parameters

Siebel server components and parameters.

This chapter identifies the Siebel Server component groups and components and describes some of the server parameters that you might have to set. It includes the following topics:

Siebel Server Component Groups

Siebel server components, siebel enterprise, server, and component parameters.

The following table lists some predefined Siebel Server component groups and the components they include. Many of the components, such as Application Object Manager components, are language-specific, although in most cases the full language-specific names are not shown in this table.

Table Predefined Siebel Server Component Groups

The following table lists some of the predefined Siebel Server components. Many of the components, such as Application Object Manager components, are language-specific, although in most cases the full language-specific names are not shown in this table.

Table Predefined Siebel Server Components

The table that follows lists some of the Siebel Enterprise Server, Siebel Server, and generic component parameters and their related attributes.

More complete descriptions of each listed parameter follow this table. In most cases, the parameters with *** shown as the default value are initially set during the initial configuration tasks (based on the input specified by the administrator). For the parameters with +++ shown as the default value, the actual default values differ from component to component. Review the documentation pertinent to the individual component for more information.

This topic contains the following topics:

Siebel Enterprise Server Parameters

Siebel server parameters, generic parameters.

Table Parameters and Attributes

This topic describes in detail the Siebel Enterprise Server parameters listed in Siebel Enterprise, Server, and Component Parameters .

Enterprise Server Description (alias EnterpriseDesc). A description of the Siebel Enterprise Server, used for identification in Server Manager views. The system prompts you for the value of this parameter during the configuration of the Siebel Enterprise Server after installation.

Indexspace Name (alias IdxSpace). The indexspace name for the Siebel database schema tables. This parameter specifies the name of the storage space in which to create the indexes for the Siebel database schema. The exact physical meaning of this parameter is database platform-specific. To determine whether this parameter applies to your database platform, see the Siebel Installation Guide for the operating system you are using .

ODBC Data Source (alias Connect). The ODBC data source name for the Siebel database schema connectivity. The default data source is created during the initial configuration of the Siebel Server, but can be overridden for a component or task. This data source must be created as a system DSN. Note that this parameter is case-sensitive.

Siebel File System (alias FileSystem). The Siebel File System path names. The specification of the File System paths must be valid relative to the computer on which the Siebel Server is installed. The value of the parameter cannot exceed 2048 characters. Multiple File System directories can be specified for this parameter by using commas to delimit each directory. For example, the following value specifies two directories hosted on different server computers running Microsoft Windows:

Siebel Repository (alias Repository). The name of the Siebel Repository for application configuration information. The default value is Siebel Repository. There can only be one active repository for each database.

Table Owner (alias TableOwner). The table owner for the Siebel database schema:

For Oracle Database, you are prompted for the default value for Table Owner during the Siebel Server initial configuration.

For Microsoft SQL Server, the value defaults to dbo.

Table Owner Password (alias TableOwnPass). The database password for the table owner account. This value must be set in order to run Siebel Server components that manipulate objects in the Siebel database schema.

Tablespace Name (alias TblSpace). The tablespace name for the Siebel database schema tables. This parameter specifies the name of the storage space in which to create the tables for the Siebel database schema. The exact physical meaning of this parameter is database platform-specific. To determine whether this parameter applies to your database platform, see the Siebel Installation Guide for the operating system you are using .

Upgrade Component (alias UpgradeComponent). Used by Siebel Anywhere to determine which Siebel Anywhere configuration is version-checked. By default, the value is Siebel HQ Server. On a regional Siebel Server, change this value to Siebel Regional Server.

This topic describes in detail the Siebel Server parameters listed in Siebel Enterprise, Server, and Component Parameters .

Auto Startup Mode (alias AutoStart). Indicates whether the Siebel Server components start automatically on Siebel Server startup. This parameter defaults to True, which indicates that the Siebel Server components are fully enabled and the default number of Siebel Server processes start when the Siebel Server system service starts (or the computer restarts). If Auto Startup Mode is set to False, then the Siebel Server components enter a shutdown state after the Siebel Server system service starts.

Communication Transport (alias Comm). The name of the transport type for network communications, for example, TCPIP.

Communication Type (alias CommType). The name of the communication type for network communications, for example, TLS or NONE. See also Siebel Remote and Replication Manager Administration Guide and Siebel Security Guide .

Component Priority Level Timeout (alias CompPriorityTime). The amount of time to wait before starting lower-priority components. Components are prioritized as follows:

Components in the System Management component group have the highest priority. These components start first.

Components in the Auxiliary System Management component group start next.

Components in the remaining component groups have the lowest priority.

The Siebel Server starts components in the System Management component group and waits for the maximum number of seconds, specified by the Component Priority Level Timeout parameter, for these components to initialize. If, at the expiry of Component Priority Level Timeout, the components fail to initialize, then the Siebel Server attempts to start the components in the Auxiliary System Management component group. If the components in this component group fail to initialize before the expiry of Component Priority Level Timeout, then the Siebel Server attempts to start the lowest priority components.

Compression Type (alias Compress). The type of compression (NONE or ZLIB) for network communications sent internally between the Application Object Manager and the Siebel Application Interface. See also the information about configuring Siebel Application Interface profiles using Siebel Management Console and about the setting HTTP 1.1-Compliant Firewall / Enable Web Compression, in the Siebel Installation Guide for the operating system you are using .

Encryption Type (alias Crypt). The type of encryption for network communications between Siebel modules such as Siebel Application Interface and the Application Object Manager. See also the information about configuring Siebel Server profiles using Siebel Management Console and about the setting Security Encryption Level or Type, in the Siebel Installation Guide for the operating system you are using . As of Siebel CRM 19.6 Update, you can use Transport Layer Security (TLS) for Siebel Remote, and you cannot use RSA. If Crypt is set to RSA for the Synchronization Manager, then you must change this value to NONE. See the description of the CommType parameter and see Siebel Remote and Replication Manager Administration Guide . For more information about encryption, see Siebel Security Guide .

Host Name (alias Host). The name of the host computer on which the Siebel Server is installed. The value is set automatically during the initial configuration of the Siebel Server, but can be changed if you want to route connection requests through a network card bound to a different host name.

Log Archive Keep (alias LogArchive). The number of log archive directories to keep in the logarchive directory. Each time the Siebel Server system service starts, the current log subdirectory moves to the logarchive subdirectory, tagged with the incarnation number of the Siebel Server. This parameter indicates the number of previous logarchive directories to retain. If this parameter is set to 0, then the current log subdirectory is not archived upon startup of the Siebel Server system service. If this parameter is set to -1, then the Siebel Server keeps logarchive subdirectories. After moving the log directory, a new log directory is created, inheriting the permissions from the parent siebsrvr directory.

Log Segment Size (alias LogSegmentSize). Determines how large a segment of the log file is, in 512 byte blocks. For example, if you set this parameter to 10, then the log segment will be 5 KB in size. A value of 0 turns off segmentation.

Log Maximum Segments (alias LogMaxSegments). Determines the number of log segments that are kept. If you set this parameter to 1, then only one segment is kept. When this segment reaches the size specified by the Log Segment Size parameter, the segment is overwritten. In general, set this parameter to a high value, such as 20. In this case, the twenty-first segment would overwrite the first segment, and so forth.

Server Description (alias ServerDesc). A description of the Siebel Server, used for identification in Siebel Server Manager views. The value of this parameter is prompted for during the initial configuration of the Siebel Server.

Server Shutdown Wait Time (alias ShutdownTime). The time to wait (in seconds) during a Siebel Server shutdown before killing component processes. When a Siebel Server is shut down (either from the Siebel Server Manager, when the Siebel Server system service is stopped, or when the computer is shut down or restarted), the currently running component tasks are notified. If the tasks do not shut down within the time specified by the Server Shutdown Wait Time parameter, then the Siebel Server kills the component processes directly and then finishes shutting down. The default value of this parameter is 60 seconds.

Siebel Root Directory (alias RootDir). The root installation directory for the Siebel Server. Every Siebel Server subdirectory is directly under this directory (such as admin , dbtempl , docking , log , logarchive , upgrade , and so on). Do not change the value for this parameter.

Siebel Server Name (alias Server). The name of the Siebel Server. This parameter is specified during the initial configuration of the Siebel Server. The name of the Siebel Server cannot be changed after it is initially configured. The Siebel Server Name parameter can contain only alpha characters, numerals, underscores, or a combination thereof. Parameter names must also lead with an alpha character and can be no longer than 12 characters. For more information about the name of the Siebel Server, see the Siebel Installation Guide for the operating system you are using .

Size of Error Buffer (alias ErrorBufferSize). The number of entries in the shared memory circular error buffer used by the Siebel Server. This buffer receives all level 0 and level 1 error messages.

Synchronization Port (alias SyncPort). The TCP/IP port number for the Synchronization Server component. The Mobile Web Clients that synchronize with this Siebel Server must be configured to connect to this port when initiating a synchronization session (in the DockConnString parameter of the client configuration file).

This topic describes in detail some of the generic parameters listed in Siebel Enterprise, Server, and Component Parameters . Many of these parameters can be set at the Siebel Enterprise Server, Siebel Server, or component levels.

Alert Level (alias AlertLevel). The level of logging to the Server Alert File. The value is set to 1 by default, but more detailed information can be specified by setting the parameter to a higher value. Currently, only levels 1 and 2 are supported. Level 1 sends only information about abnormal process and task terminations to the Alert File. Level 2 sends information about every process or task when it exits, whether normally or unexpectedly.

Application Datasource (alias CFGDatasource). The Application Object Manager default configuration data source. The value for this parameter is one of the values listed for the OM - Named Data Source name parameter.

Application Scripting Enabled (alias CFGEnableScripting). Determines whether the Application Object Manager server component can execute a server script. If you set this to True, then scripting DLL files are loaded and the application can then execute scripts. The default value for this parameter is True. Setting this parameter to False also disables browser scripts in addition to server scripts.

Application Shared Mode users directory (alias CFGSharedModeUsersDir). Specifies the users directory used in shared mode. Update the value of this parameter if you change the location of the Siebel File System.

Application * Font. Several parameters with names starting with Application and ending in Font specify fonts to use for Siebel application user interface elements unless these settings are overridden by font specifications in style sheets (CSS).

Auto Restart (alias AutoRestart). Indicates whether this component can be restarted automatically. This parameter works in conjunction with the Number of Restarts parameter to determine the number of attempts that are made to restart the target component.

Compressed File Download (alias CompressedFileDownload). By default, files are downloaded to a client's browser in a compressed form when using Siebel File System Manager. On certain versions of Microsoft Internet Explorer, this operation might result in the renaming of the file. If you want to disable compressed file download, then set this parameter to False for the Application Object Manager for which you want this feature to be disabled. The default value is True.

DB Multiplex - Max Number of Shared DB Connections (alias MaxSharedDbConns). One of two parameters that configure shared database connections. (The other parameter is DB Multiplex - Min Number of Shared DB Connections.) Shared connections are used by most Application Object Manager operations. DB Multiplex - Max Number of Shared DB Connections controls the maximum number of shared database connections, and is defined for each component. That is, DB Multiplex - Max Number of Shared DB Connections controls the maximum total number of shared database connections for the component on each Siebel Server, not an instance (task or process) of the component. A setting of -1 disables this parameter and is the default setting.

DB Multiplex - Min Number of Dedicated DB Connections (alias MinTrxDbConns). Controls the minimum number of dedicated database connections within an Application Object Manager process. Dedicated database connections are used primarily by specialized Siebel components, such as Siebel EAI, that need transactions to span multiple Application Object Manager operations. The DB Multiplex - Min Number of Dedicated DB Connections parameter is defined for each instance of the component. That is, DB Multiplex - Min Number of Dedicated DB Connections controls the minimum number of dedicated database connections for each instance (process) of the component, not for the entire component. This functionality is different from the parameters that configure shared database connections. A setting of -1 disables this parameter and is the default setting.

DB Multiplex - Min Number of Shared DB Connections (alias MinSharedDbConns). One of two parameters that configure shared database connections. (The other parameter is DB Multiplex - Max Number of Shared DB Connections.) Shared connections are used by most Application Object Manager operations. DB Multiplex - Min Number of Shared DB Connections controls the minimum number of shared database connections, and is defined for each component. That is, DB Multiplex - Min Number of Shared DB Connections controls the minimum number of shared database connections a component tries to maintain on each Siebel Server across all instances of this component. A setting of -1 disables this parameter and is the default setting.

Default Tasks (alias DfltTasks). The number of processes to start for a background mode component when the component is started explicitly through the Siebel Server Manager, or when the Siebel Server is started (if the component state was last set to Running). Components with a Default Tasks parameter set to a value greater than zero start automatically when the Siebel Server is started.

DefaultNavigation (alias DefaultNavigation). The default navigation control in the Siebel Web Client application, which can be NAVIGATION_SIDE, NAVIGATION_TAB, or NAVIGATION_TREE. The default setting is NAVIGATION_SIDE, which means that the application uses the Side Menu navigation control by default. The navigation control user preference, if set, takes precedence over the DefaultNavigation component parameter value. For Siebel Web Tools, Side Menu navigation is always enabled regardless of the parameter or user preference settings. This parameter was added in Siebel CRM 19.4 Update. For more information, see Siebel Fundamentals Guide and Siebel Applications Administration Guide .

EnabledTC (alias EnabledTC). When set to True for an Application Object Manager, enables a terms and conditions page that users must accept to be allowed into the Siebel application. Additional configuration steps apply, which are described on My Oracle Support in article 478253.1 (Article ID).

EnableMultiTab (alias EnableMultiTab). This parameter enables users to access the same applications over multiple tabs of the same browser session. You can also limit the number of tabs in which a user can access the Siebel CRM applications, by setting the Maximum Possible Tabbed Sessions value when you configure the Siebel Application Interface profile in the Siebel Management Console. This parameter was added in Siebel CRM 19.7 Update. For more information, see Configuring Siebel Open UI . See also the Siebel Installation Guide for the operating system you are using .

Enable Safe Boot (alias EnableSafeBoot). The out-of-the-box (OOTB) Siebel Runtime Repository is shipped as a loadable unit (DLL or SO file). When the EnableSafeBoot parameter is set to True, the application uses the OOTB Runtime Repository. You can use this parameter in testing or troubleshooting of your custom configurations. For Siebel Web Tools, SafeBoot is always enabled regardless of the parameter setting. This parameter was added in Siebel CRM 17.0. For more information, see Configuring Siebel Open UI .

Error Flags (alias ErrorFlags). Specifies the flags used for tracing error information. This parameter is used to turn on various types of component-specific error tracing.

Export Status Size (alias ExportStatusSize). Specifies the number of records to be exported in an export operation performed by the Application Object Manager component.

Honor MaxTasks (alias HonorMaxTasks). When the parameter value is True, a component process that reaches Max Tasks stops accepting requests from the Server Request Broker. If another request is sent, then an error message results. The process resumes accepting requests after some tasks finish. If the parameter value is False, then all of the requests are queued in the component process.

Language Code (alias Lang). The three-letter language code for the component processes. Translatable messages (including error messages) are output in the specified language. The translated message files for the language must exist in the locale subdirectory of the Siebel Server installation. For more information, see Siebel Global Deployment Guide .

Locale Code (alias LocaleCode). The three-letter locale code for the component processes. A locale is a set of rules guiding how common data is displayed to the user or is received from the user. Siebel CRM supports formatting of data, such as dates, time, numbers, and currency, based on locale settings. Locales are administered using the Locale view in the Administration - Data screen. For more information, see Siebel Global Deployment Guide .

Local load balancing upper threshold (alias UpperThreshold). Determines the load threshold at which a new Application Object Manager process starts, and is based on the load percentage of a given Application Object Manager process. For example, setting this parameter to 80 percent on an Application Object Manager that handles 50 concurrent sessions starts a new Application Object Manager process when 40 sessions become active. The default value is 100 percent. For more information about load balancing, see Siebel Deployment Planning Guide .

Log Print Timestamp (alias LogTimestamp). Specifies whether to print a timestamp on records written to the trace files. The value is set to True by default, but administrators might want to override it to False for components that perform a large amount of logging (or if a high value is set for the Trace Flags or SQL Trace Flags parameters).

Manifest Safe Load (alias ManifestSafeLoad). Set to True to start the application with only the Oracle-provided (out of the box, or OOTB) manifest records. When False (the default), the application starts with both customer (custom-configured) and seeded (Oracle-provided) manifest data. For Siebel Web Tools, the OOTB manifest is always used regardless of the parameter setting. This parameter was added in Siebel CRM 19.4 Update. For more information, see Configuring Siebel Open UI .

Maximum depth of the query (alias MaxDepthOfTheQuery). Allows you to increase the maximum parse depth of a query with a large search specification, including, for example, a large number of OR or AND clauses.

You might receive this error: The query could not be run because it is too big. If you receive errors indicating that a query cannot run because it is too big, then you might refine the query to be more selective or to use parentheses. Alternatively, you can try setting this parameter to a larger value to eliminate the error. The default value is 500.

If you need to adjust this parameter value, then the setting you choose must correlate to the default stack size for your server operating system. For example, a value of 800 will generally work on Microsoft Windows, for which the default stack size is 1 MB, while a value of 500 will generally work on Linux or UNIX operating systems, for which the default stack size is 512 KB. If you increase the stack size for your operating system, then you can use a higher setting for this parameter.

You can optionally set this parameter at the enterprise level or the server level. You can also set MaxDepthOfTheQuery in the application configuration file for the Siebel Mobile Web Client or Developer Web Client (in the [InfraObjMgr] section), or set it in the tools.cfg file for Siebel Tools.

Maximum MT Servers (alias MaxMTServers). Specifies the maximum number of multithreaded Siebel Server processes to be run concurrently for a component that has multithreading enabled. Note that only batch mode and interactive mode components can run with multithreaded set to True. Tasks and client sessions run as threads within the multithreaded Siebel Server processes.

The number of tasks that can run in each Siebel Server process is determined by the value of the Maximum Tasks parameter divided by Maximum MT Servers. Increase or decrease the value of Maximum MT Servers based on the number of users for the given component process. For more information about this parameter, see Siebel Performance Tuning Guide .

Maximum Processes (alias MaxProcs). Specifies the maximum number of concurrent running processes for a Siebel Server component. The Siebel Server must be restarted in order for any changes to this parameter to take effect.

Maximum Tasks (alias MaxTasks). Specifies the maximum number of background mode, batch mode, or interactive mode processes or threads that can run concurrently for a component. This value applies to threads for components that have multithreading enabled, or otherwise component processes. Increase or decrease this value based on the number of users for the given component process. This value also determines the number of tasks for each component that are tracked by the Siebel Server. For more information about this parameter, see Siebel Performance Tuning Guide .

Memory Usage Based Multithread Shell Recycling (alias MemoryBasedRecycle). If it is set to True, then processes for this component are recycled automatically when virtual memory usage reaches a specified threshold. The threshold is set using the parameter Process VM Usage Lower Limit. For example, when a component is set with this parameter and the memory usage has exceeded the configured threshold, the recycling procedure begins by disabling new tasks, spawning a new process, and commencing a normal shutdown (that is, waiting for all of the tasks to finish before shutting down). The default value is False. Use this parameter to remedy your application only if excessive memory usage created by memory leaks seems to be occurring.

Minimum MT Servers (alias MinMTServers). Specifies the default number of multithreaded Siebel Server processes that are started for a component that has multithreading enabled. These processes are brought up when the component is started explicitly through the Siebel Server Manager, or when the Siebel Server is started (if the component state was last set to Running).

Additional multithreaded Siebel Server processes are started as needed (namely, when the maximum number of threads that can run in a Siebel Server process has been reached), up to the value of the Maximum MT Servers parameter. Setting this parameter to 0 disables the component. For more information about this parameter, see Siebel Performance Tuning Guide .

Minimum Up Time (alias MinUpTime). Specifies the minimum time that a multithreaded server component such as an Application Object Manager must be up for a restart to be successful (in seconds). In order for the component restart to be considered successful, the component must be running for the duration specified by this parameter. This parameter works with the Number of Restarts parameter to determine the number of restart attempts in a time interval allowed for a component (NumRestart multiplied by MinUpTime). If a component instance cannot be restarted after this time interval, then no new restart is attempted (the component instance will not be running). The default value for this parameter is 60 seconds.

Multithreaded (alias Threaded). Specifies whether the component is multithreaded or multiprocess. This parameter only applies to batch mode and interactive mode components. Use the default value for this parameter.

Number of lines after which to flush the log file (alias LogFlushFreq). Specifies how often data is written to the log file. Set the value to n so that data is written to the log file every n lines. For example, set the value to 1 to write every line to the log file. Set the value to 0 (default value) to allow the operating system to determine when to write data to the log file.

Number of Restarts (alias NumRestart). Specifies the number of times that a multithreaded server component can be restarted if it exited with errors in less than the time set for Minimum Up Time. This parameter works with Auto Restart to determine whether multithreaded server components will be restarted. This parameter also works with the Minimum Up Time parameter to determine the number of restart attempts in a time interval allowed for a component (NumRestart multiplied by MinUpTime). If a component instance cannot be restarted after this time interval, then no new restarts are attempted. (In this situation, the component instance will not be running.) The default value for this parameter is 10.

Number of Retries (alias NumRetries). Specifies the number of retries for recovery. This parameter works with the Retry Interval and Retry Up Time parameters to reconnect multithreaded server components to the database if database connectivity has been lost.

Number of Sessions per SISNAPI Connection (alias SessPerSisnConn). Specifies how many sessions can be multiplexed (shared) through each SISNAPI connection, which helps to reduce the number of open network connections. SISNAPI connections are those between the Siebel Application Interface and the Application Object Manager. If Number of Sessions per SISNAPI Connection is -1, then all of the sessions are created through only one SISNAPI connection. The default value for this parameter is 20. However, while 20 is a good value to use for user sessions, it does not apply to incoming HTTP requests from other systems, for example, EAI HTTP Adapter access.

OM - Configuration File (alias ConfigFile). Specifies the configuration file used by the application associated to this component, such as siebel.cfg for Siebel Sales, uagent.cfg for Siebel Call Center, and so on. The setting of this parameter at the component level (such as an Application Object Manager, which is associated with an application) overrides the setting at the server level. See also Overview of Parameters in Siebel Application Configuration Files .

OM - Data Source (alias DataSource). Specifies the Application Object Manager data source.

OM - Named Data Source Name (alias NamedDataSource). Lists the named subsystems that the Application Object Manager preloads when it initializes. That is, all of the data sources that the Application Object Manager might use are listed in the value.

OM - Model Cache Maximum (alias ModelCacheMax). Specifies the size of the cache for model objects (also known as cached sessions) in object manager-based server components, such as Workflow Process Manager. Each model in the cache creates two database connections for the life of the model. (One connection is for insert, update, and delete operations. The other connection is for read-only operations.) The model cache improves performance for the object manager-based server components, and it is generally recommended not to disable this parameter. The default value is 10. A value of 0 disables this parameter, and the maximum setting for this parameter is 100. For more information about setting this parameter, see Siebel Performance Tuning Guide .

OM - Resource Language Code (alias ResourceLanguage). Specifies the language code used for Application Object Manager resources. Each language has its own three-letter code identifier. For example, ENU identifies U.S. English. For more information, see Siebel Global Deployment Guide .

OM - Timed Statistics (alias TimedStats). Enables the use of the statistics in the Administration - Server Management screen, Statistics view. Statistics include Average Connect Time (seconds), Average Response Time (milliseconds), and Average Think Time (seconds). Restart the Siebel Server for this parameter to take effect. The statistics are refreshed on completion of each task, so a specific user session must log out for the statistics for that session to be reflected in the Statistics screen. This is an advanced parameter.

When a task for a component completes its operation, both generic and component-specific statistics roll up to the component level. Only generic statistics roll up to the Siebel Server level. The statistics data will be reset when the component is restarted.

Password (alias Password). Specifies the database user password. This parameter specifies the password for the account referenced by the User Name parameter. Both the user name and password are prompted for during the initial configuration of the Siebel Server. The User Name and Password parameters are used to connect to the database for automatic startup of background mode components, for example. See also the description for the Auto Startup Mode parameter in Siebel Server Parameters and Siebel Enterprise, Server, and Component Parameters .

Process VM Usage Lower Limit (alias MemoryLimit). Sets the virtual memory usage threshold (in megabytes). A component process that reaches this threshold is recycled. The parameter to enable this feature is Memory Usage Based Multithread Shell Recycling. Use this parameter to remedy your application only if excessive memory usage created by memory leaks seems to be occurring.

Process VM Usage Upper Limit (alias MemoryLimitPercent). Specifies the percentage above the value of Process VM Usage Lower Limit at which a fast shutdown is triggered.

Retry Interval (alias RetryInterval). Defines the time interval before a series of retries are made for recovery. This parameter works with the Number of Retries and Retry Up Time parameters to reconnect multithreaded server components to the database if database connectivity has been lost.

Retry Up Time (alias RetryUpTime). Specifies the minimum up-time for a new set of retries for recovery. This parameter works with the Number of Retries and Retry Interval parameters to reconnect multithreaded server components to the database if database connectivity has been lost.

Session Keepalive Timeout (alias SessKeepAlive). Specifies the time that a task waits for a message from the client before timing out. When the time-out interval passes, the task ends the client session. The default value is 7200 seconds (two hours). This is a hidden parameter.

SISNAPI Connection Maximum Idle Time (alias ConnIdleTime). Configures the connection timeout between the Siebel Application Interface and the Siebel Server. Valid values are numeric, specifying the period of idle time (in seconds) after which the connection is disconnected by the component. See the following table for parameter setting descriptions. It is recommended that you set this parameter to a value slightly below the firewall connection timeout value. The default value is -1.

Table Values for ConnIdleTime Parameter

SISNAPI - Log Traffic (alias LogTraffic). Specifies whether the Application Object Manager records a log of all of the Siebel Internet Session API (application programming interface) messages. SISNAPI is a session-based remote procedure call (RPC) designed to support high responsiveness between the Siebel Server and client applications.

Sleep Time (alias SleepTime). Specifies the time to sleep between iterations (in seconds). This parameter is used for the sleep time of component processes running in background mode when the Siebel Server is idle.

SQL Trace Flags (alias SQLFlags). The flags for tracing of SQL statements. If this parameter is set to 1, then every SQL statement issued by the component tasks is logged to the information log file for each task. If this parameter is set to 2, then each SQL statement is logged in addition to information about the number of parse, execute, and fetch calls, and timing information about each type of call.

Static Port Number (alias PortNumber). Specifies the network port number on which a component listens for client requests. If no value is specified, then a unique port number is generated dynamically for each component, starting at port number 49150 and higher, depending on the number of components configured and the occupied ports above this number.

The Siebel Connection Broker component (alias SCBroker), which provides intraserver load balancing, listens on the port specified by this parameter. For more information, see About Siebel Connection Broker (SCBroker) .

This parameter applies to interactive, batch, and background mode components, with the exception of all of the Application Object Manager components. The port number, whether static or dynamic, is hidden from the end user and is provided primarily so that administrators can fix the port numbers used by a component, for firewall configuration. If you are configuring this parameter, then select a port number either below 49150 or high enough to make sure that there are no conflicts with dynamically generated port numbers.

Trace Flags (alias TraceFlags). Specifies the flags for component-specific tracing information. This parameter is used to turn on various types of component-specific tracing. See the documentation for individual Siebel Server components for a description of how to set this parameter for each component.

Use IP Address (alias UseIPAddress). Specifies whether to construct the SISNAPI connection strings using the IP address instead of the hostname. The default value is True. Changing the value to False affects performance because the hostname must be looked up each time it connects.

Use Shared Log File (alias LogUseSharedFile). Specifies whether all of the tasks within a component process log to a shared file. When set to False, one log file for each task is generated.

User Name (alias Username). Specifies the database user name. This parameter specifies the user name of the database account that is used by the Siebel Server or Siebel Server components that are not started interactively or in batch mode by the Siebel Server Manager. The password for this database account must be specified by the Password parameter. Both the user name and password are prompted for during the initial configuration of the Siebel Server. The User Name and Password parameters are used to connect to the database for automatic startup of background mode components and for other purposes. See also the description for the Auto Startup Mode parameter in Siebel Server Parameters and Siebel Enterprise, Server, and Component Parameters .

When you run component tasks from the Server Manager GUI, the value for the User Name parameter is used because the tasks are submitted as component jobs and started using the Server Request Broker server component, which uses the User Name parameter value. When you run component tasks from the Server Manager command-line interface, in the case of manually started batch or background mode components, the User Name parameter is that of the user who starts tasks on these components.

Assignment Manager Component Unavailable (Doc ID 1350956.1)

Last updated on AUGUST 11, 2022

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

IMAGES

  1. Siebel Innovation Pack 2014: About Siebel Assignment Manager Object

    assignment manager component in siebel

  2. Siebel Innovation Pack 2014: About Siebel Assignment Manager Object

    assignment manager component in siebel

  3. Siebel Assignment Manager

    assignment manager component in siebel

  4. Siebel Assignment Manager

    assignment manager component in siebel

  5. Siebel 2018: Managing the Siebel Deployment

    assignment manager component in siebel

  6. Siebel 2018: Configuring the Siebel Deployment

    assignment manager component in siebel

VIDEO

  1. August 30, 2023

  2. MODULE 1

  3. cloud nose pizza watch assignment manager

  4. assignment manager give confidence

  5. Database management system

  6. Database Management System : Introduction(CS)

COMMENTS

  1. Overview of Siebel Assignment Manager

    Siebel Assignment Manager routes business entities and work items to the most appropriate candidates by enforcing business rules set by sales, service, and marketing organizations. ... The Communications Server, that is, the Communications Inbound Manager server component, works in conjunction with Siebel Email Response to create inbound emails ...

  2. Essential Building Blocks of Siebel Assignment Manager

    In Siebel Assignment Manager, candidates represent the people who or organizations that are evaluated as potential assignees for objects. Depending on the assignment rule you use, and the object to which a candidate is assigned, candidates can be positions, employees, or organizations, and can be assigned as individuals or as members of a team. ...

  3. Assignment Manager and Batch Assignment Component Parameters

    This parameter controls the number of Assignment Manager server processes that are started when the Siebel Server starts up. If this value is set to zero, Assignment Manager is disabled.

  4. Preparing to Run Siebel Assignment Manager

    After configuring Siebel Assignment Manager objects and attributes or altering assignment policies, it is often necessary to stop and restart various server tasks and components. Table 9-2 summarizes the required server tasks and components that must be restarted based on the type of configuration process.

  5. What Is The Use Of Assignment Manager Component Parameter 'Assignment

    What Is The Use Of Assignment Manager Component Parameter 'Assignment History Cache Size' (Doc ID 2857891.1) Last updated on APRIL 06, 2022. Applies to: Siebel CRM - Version 15.0 [IP2015] and later Information in this document applies to any platform. Goal

  6. Assignment Manager Component

    Assignment Manager Component - Max Task Value Parameter Value (Doc ID 2546190.1) Last updated on OCTOBER 06, 2021. Applies to: Siebel Finance - Version 15.8 [IP2015] and later Information in this document applies to any platform. Goal. Can maximum Tasks (MaxTasks) Parameter be increased to a higher value from 20 for Assignment Manager ...

  7. Bookshelf v7.8: Configuring Assignment Object Properties

    Siebel Assignment Manager uses definitions in the Siebel repository to assign objects to assignment rules and candidates. ... Each of the corresponding business components has one or more fields that specify the owner or team. An assignment rule includes one or more assignment objects. When the rule is satisfied, specific columns underlying ...

  8. Configuring Siebel Assignment Manager Step By Step

    Assignment acting is a Siebel component that assigns certain Siebel entities on a (Position, Employee, and Organization) on predefined terms, when we talk about Siebel items here I means (Cases, Service Requests, Activities etc…) of track when AM assigns a record from case table to a assured your no the position assigned may see those record ...

  9. Assignment Manager (SBL-ASG-00030) (SBL-ESC-00106)

    Siebel Assignment Manager - Version 7.5.3.4 SIA [16180] and later Information in this document applies to any platform. This document was previously published as Siebel SR 38-1278712571. Symptoms. The Assignment Manager component in an UPGRADE environment moves to the Unavailable state after being in the Online state for about 6 seconds.

  10. Basic Configuration for Siebel Assignment Manager

    About Performing Basic Configuration Tasks for Siebel Assignment Manager. Using Siebel Tools, you can modify existing assignment object definitions or create new assignment object and assignment criteria definitions in the Siebel repository. After you deploy the changes, these definitions appear as criteria in the Criteria view or as skills in ...

  11. Bookshelf v7.8: Assignment Methodology

    Siebel Assignment Manager uses the following methodology to assign candidates to assignment objects. Assignment Manager finds assignment rules for an object. Assignment Manager finds active assignment rules for evaluation for the object being assigned. If there are no active rules for the assignment object, default assignees are assigned.

  12. Siebel Assignment Manager Quiz

    Welcome. This quiz is designed to test your knowledge of the venerable Siebel Assignment Manager. A very robust component with so many different options and functional capabilities, it deserves a place on the podium of top components. But it can catch everyone out from time to time - there are just so many options!

  13. Assignment Manager and Siebel Public Sector

    By default, cases are assigned to the user who creates the case. You can manually assign cases to multiple agents. You can also use Oracle's Siebel Assignment Manager to automatically assign cases, case activities, and submitted applications to agents. Additionally, you can automatically assign cases to organizations and case activities to case managers. To determine these assignments, you ...

  14. Assignment Manager

    Issue related to "Release" button of Assignment Manager Screen: New Partner Organizations created in Siebel via nightly feed from the data warehouse after which batch assignment running on the various entities such as Account,Contact, Promotion etc which should also consider these new Organizations for assignment purpose.

  15. how to create new components on siebel server

    3. Enable the component on Siebel servers. This will create component definitions in the respective siebel servers. (Enable button is available in the same screen) 4. Synchronise the component through synchronise button. 5. stop and re-start the siebel server. Now You can see ur new component in Siebel Server Management with running/online status.

  16. Siebel Server Components and Parameters

    To run Interactive Assignment, the Server Request Processor component must also be running. For more information, see Siebel Assignment Manager Administration Guide. Batch Assignment . AsgnBatch . Batch . No . Batch assigns positions, employees, and organizations to objects. For more information, see Siebel Assignment Manager Administration ...

  17. Assignment Manager Component Unavailable

    Siebel Assignment Manager - Version 8.1.1.4 SIA ... Assignment Manager Component Unavailable (Doc ID 1350956.1) Last updated on AUGUST 11, 2022. Applies to: Siebel Assignment Manager - Version 8.1.1.4 SIA [21225] and later Information in this document applies to any platform. Symptoms ...