Mixed Technology Topics (Remedy ARS, AJAX, Business Objects)

SAP acquired Business Objects in 2007 for approximately $6.8 billion. BO is now part of SAP's BI and analytics portfolio. IBM is a competitor in the analytics space.

While technically challenging, BO DOES allow combining data from different universes in reports using techniques like merged reports, linked universes, or multiple data providers. The statement is TRUE at the functionality level - you CAN show combined data from multiple universes in a single report, even if not by directly copying objects between universes.

Business Objects is primarily an OLAP (Online Analytical Processing) tool designed for multidimensional analysis, interactive reporting, and ad-hoc querying of data warehouses. It is NOT an ETL tool (that's Data Integrator) and while it produces reports, 'Reporting tool' is too narrow - OLAP captures its analytical capabilities better.

Business Objects provides a report conversion tool specifically designed to migrate Desktop Intelligence (DeskI) reports to Web Intelligence (WebI) format. This utility preserves most report logic, formulas, and formatting during the conversion process, enabling organizations to modernize their reporting infrastructure.

Web Intelligence reports are viewed through InfoView, a web-based portal that requires no client installation. Desktop Intelligence reports, however, need the BO client software to be installed on the user's machine. InfoView accommodates both report types, but only WebI reports are fully web-native.

AJAX relies on standard web technologies like HTML, CSS, JavaScript, and XML/JSON. Since these are natively supported by all modern web browsers across different operating systems, AJAX-based applications are independent of the specific browser or platform version used by the client.

In Internet Explorer 5 and 6, the XMLHttpRequest object was implemented as an ActiveX control rather than a native JavaScript object. The correct syntax is xmlhttp=new ActiveXObject("Microsoft.XMLHTTP"). Modern browsers use new XMLHttpRequest(), but this doesn't work in IE5/IE6.

The correct XMLHttpRequest methods are open() with method as first parameter (case-sensitive: "GET" or "POST"), not get() or post(). Options B and D correctly use xmlhttp.open() with proper method names. Options A and C incorrectly use lowercase get()/post() methods and uppercase "OPEN"/"POST" as parameters.

POST requests in AJAX (and HTTP generally) do not have a protocol-defined size limit. Unlike GET requests, which are constrained by URL length limits, POST sends data in the request body, allowing much larger payloads. Practical limits exist only due to server configuration (like PHP's post_max_size or IIS limits), not the POST method itself.

GET requests send data in the URL query string, which has practical limits. Browsers typically cap URLs around 2,000 characters, and servers also enforce maximum URL lengths. Therefore, GET requests DO have size limits, making the statement 'no size limit' false. POST should be used for larger data payloads.

Setting the third parameter of open() to false specifies a synchronous request, blocking further JavaScript execution until a response is received from the server. By contrast, asynchronous requests allow execution to continue immediately. Distractors describing runtime errors are incorrect.

The onreadystatechange event handler is triggered every time the readyState property of an XMLHttpRequest changes. In a complete cycle, the state transitions through four distinct values (1, 2, 3, and 4), triggering the event handler four separate times. Distractors specifying fewer triggers are incorrect.

In AJAX, readyState 4 indicates that the XMLHttpRequest transaction has completed, and status 200 signifies a successful HTTP response. Other status codes like 400 indicate client errors, and lower readyState values mean the request is still loading or processing.

P2 tickets typically represent high-priority issues that significantly impact business operations but don't completely halt production. The SLA of 1 business day allows time for investigation and resolution while maintaining urgency. P0 (critical) has shorter SLAs, while P3-P4 have longer response times.

P0 tickets represent the highest priority level - critical incidents that completely stop business operations, such as plant/factory shutdowns. 'Application Down' might be P0 depending on impact, and 'Large No of users affected' could be P1 or P0 depending on severity. 'Plant down' definitively indicates complete operational stoppage, making it the clearest P0 example.

In Remedy ARS database schema, forms use specific table prefixes: 'T' for the main data table (regular/form table), 'B' for attachment blob data, and 'H' for history/audit trail. Therefore 'T-Regular Table, B-attachment' (Option B) is correct, and 'H-history, T- regualr, B-attachment' (Option C) is also correct as it includes all three table types.

In ARS database, each attachment requires two tables: one for attachment metadata (fields, size, name, etc.) and one for the actual binary/blob data. This separation allows efficient storage and retrieval of attachment information without loading the entire binary content when only metadata is needed.

The arschema table is the core database table in ARS that contains schema definitions for all forms. It stores form structure, field definitions, and metadata. The other options are variations of this name but incorrect - the actual table name is 'arschema' (all lowercase, one word).

ARS database requires Unicode support to handle multiple languages properly. If the database is not in Unicode character set, it cannot store or display characters from different languages correctly. Multi-language support depends on the database collation and character set being Unicode (UTF-8 equivalent).

When installing ARS in a server group environment, secondary servers must share the same database and configuration as the primary. The 'Shared' option indicates this server joins an existing server group and shares resources, rather than a fresh install, upgrade, or overwrite which could break the group configuration.