WebLogic Server and IT Support Fundamentals

Journal search operations are performed on the HRH-ARCH Server, which is the designated archival server for journal/audit data. This is a True statement based on the system architecture described.

The statement is False because email-extender IS used for journal search functionality in this system. The extender component provides necessary integration between the email system and journal search capabilities.

HELPSTAR is a helpdesk ticketing system where PR (Personnel/Priority Requests) are routed to specific queues for monitoring and resolution. BlackBerry, EMAIL, and New User Setup are operational queues that handle different types of service requests. Saggita and Shared Point Services are not PR monitoring queues in this system.

Active Directory Organizational Unit (OU) placement for user accounts follows the organizational hierarchy where Profit Center and Location are the primary determinants. Department and City are not the deciding factors for OU movement in this directory structure design.

A user's new email ID is only considered ready for use after both the HRH and Willis IDs have been successfully created in the system. The Willis ID cannot be created before the HRH ID exists, so the completion of both IDs is the confirmation point. Primary/secondary designation happens after creation, not at the readiness confirmation stage.

A user's primary Organizational Unit and domain are determined by mapping their Location against their Profit Center in the organizational directory structure. Department, Title, and Role are not the attributes used for this OU/domain selection logic.

Termed (terminated employee) PST files and Journal search PST files must be archived to the designated network repository path \hrhw3kfs.hrh.com\pstrepository. The other server paths listed are not the correct storage locations for these specific archived mailbox files.

The ExMerge (Exchange Merge) utility for extracting mailbox data has a size limitation of 2 GB per mailbox. Attempting to extract mailboxes larger than 2 GB will fail or require alternative methods. 1GB, 3GB, and 4GB are not the correct limits for this tool.

Termed employee requests must be forwarded to the Client's queue after completion from your end, as these involve account closure and data handoff that require client-side action. Email, BB (BlackBerry), and New Setup requests do not follow this client forwarding workflow.

Willis ID creation is a process that takes more than 5 hours to complete after the HRH ID has been created. This is not a quick operation: the time required is significantly longer than 30 minutes, 1 hour, or 2 hours. This extended timeline is important for managing user expectations during the onboarding process.

BlackBerry (BB) accounts are managed through the dedicated BlackBerry administration console, not through Active Directory, Email-Extender, or ExMerge tools. The BB console is the specialized interface for BlackBerry device and account management.

The 'Reload' command is the correct command to reboot a hardware client such as a firewall during network troubleshooting. 'Boot -r' is not standard syntax, 'Restart' is a Windows command, and 'shut - r' is incorrect syntax for reboot commands on network hardware.

WebLogic Server provides two primary cluster services: HTTP Session State Clustering (for maintaining session state across servers) and Object Clustering (for clustering RMI and EJB objects). These ensure high availability and failover capabilities. File Service and Time Service are not primary clustering services in WebLogic.

EJBs (Enterprise Java Beans) can be homogeneously deployed across all servers in a WebLogic cluster, meaning the same EJB application is deployed on every cluster member. This enables load balancing and failover - any server can handle EJB requests. This is a standard deployment practice for clustered applications.

WebLogic Server 6.0 MDBs support concurrent processing for both Topics (pub/sub messaging) and Queues (point-to-point messaging). Multiple MDB instances can process messages concurrently, improving throughput. This is a key advantage of MDBs for handling high-volume JMS traffic.

A CMP (Container-Managed Persistence) entity bean on WebLogic requires one J2EE standard deployment descriptor (ejb-jar.xml) and TWO WebLogic-specific descriptors (weblogic-ejb-jar.xml and weblogic-cmp-jar.xml). The weblogic-cmp-jar.xml specifically defines CMP mapping and is required in addition to the standard descriptors.

Two JMS servers cannot share the same persistent store in WebLogic. Each JMS server must have its own dedicated persistent store (file or database) to maintain message integrity and avoid conflicts. This isolation ensures reliable message persistence and recovery.

WebLogic JMS with JDBC persistence supports multiple databases including Cloudscape, Oracle, Informix, and Microsoft SQL Server for persistent message storage. The JDBC store allows JMS to use any database with a compliant JDBC driver, providing flexibility in choosing the persistence backend.

WebLogic Server uses round-robin as the default load balancing algorithm for clustered object stubs when no algorithm is specified. Round-robin distributes requests sequentially across available server instances, providing even load distribution. Weight-based and Random are alternative algorithms that must be explicitly configured.

The 'Waiters' attribute in the JDBC connection pool monitoring shows the current number of clients waiting for a connection. 'Waiters high' is the peak value reached, not the current count. 'Connections high' tracks maximum connections used, and 'Wait seconds high' tracks maximum wait time.