Servers

Published on June 2016 | Categories: Documents | Downloads: 38 | Comments: 0 | Views: 507
of 19
Download PDF   Embed   Report

Comments

Content

BO Servers

Web Application Server

Main function:  Act as a gateway between user’s web browser / web server and the XI R2 servers  Translate user’s web requests into XI R2 language and pass requests onto the CMS and other servers  Pass back answers from XI R2 servers directly back to the web browser and/or to the Web Server Used when:  All the transactions in the system initiated by the web browser need to be channeled through the WAS  Answers (e.g. viewable pages) get transferred back to the web browser and/or web server via WAS  Acts as a processing server for viewing OLAP requests Communicates with:  All servers in the system Additional information:  Two main types: Java, .NET  Web Component Adapter is an optional component (backward compatibility

Central Management Server

Main function:  Brains of the system  Manages all the aspects of the system: Groups, Users, Content, Security, Stores information about documents (actual documents saved on the Input and Output FRS) Used when:  All transactions require some sort of authorization performed by the CMS  All users logging in require some sort of authentication performed by the CMS  All servers when they start up register with the CMS (ip and name and port), which in turn acts as a traffic controller and allows other servers to talk to each other directly Communicates with:  Central common system database (and audit)  All servers in the system  Applications (Universe Designer, Desktop Intelligence, Crystal Reports Writer, Import Wizard, Publishing Wizard, etc … ) Additional information:  Have to have at least one CMS running for the system to be operational  For fault tolerance it is possible to install a second CMS on a different machine and point it to one central common system database (this constitutes CMS cluster)

Input File Repository Server

Main function:  Stores and manages published documents (.rep, .wid, .unw, .rpt, .exe, .bat, .doc, etc)  Stores and manages universe files (information about universes stored in the CMS System Database) Used when:  Documents are being published  Documents are being viewed (not instances)  Documents are being run by a schedule process  Universes need to be accessed by the processing servers or by Universe Designer application Communicates with:  All processing servers in the system including WAS  Applications (Universe Designer, Desktop Intelligence, Crystal Reports, Import Wizard, Publishing Wizard, etc …) Additional information:  You can have more than one Input FRS server running at any given time within the enterprise deployment  But only one of the Input FRS server services at any given time will be active (used by the CMS – which one? the one that has been registered with the CMS the longest)

Output File Repository Server

Main function:  Stores and manages document instances (.rep, .wid, .rpt, .exe, .bat, .doc, etc) Used when:  Document instances are being published at the time of migration  Document instances are being viewed  Documents are being run by a schedule process Communicates with:  All processing servers in the system  Applications (Import Wizard) Additional information:  You can have more than one Output FRS server running at any given time within the enterprise  deployment But only one of the Output FRS server services at any given time will be active (used by the CMS – which one? the one that has been registered with the CMS the longest)

Crystal Reports Page Server

Main function:  Generates viewable pages for Crystal Reports documents (objects or instances) Used when:  Crystal Reports are being viewed (objects or instances) and preferences for viewing Crystal Reports within user’s InfoView are set to DHTML or ActiveX or Java (Not Interactive Viewer) Communicates with:  CMS, WAS, CR Cache Server, Input, Output, RAS (cascading prompts generation) Additional information:  Can be memory and CPU intensive process  Viewable pages are created in a proprietary format (.epf)

Crystal Reports Cache Server

Main function:  Manages and stores viewable pages for Crystal Reports documents (objects or instances) that were generated by the CR PS  Useful especially when multiple users are viewing the same Crystal Report document Used when:  Crystal Reports are being viewed (objects or instances) and preferences for viewing Crystal Reports within user’s InfoView are set to DHTML or ActiveX or Java (Not Interactive Viewer) Communicates with:  CMS, WAS, CR Page Server Additional information:  Light on resources

Report Application Server

Main function:  Creates viewable pages for Crystal Reports documents (objects or instances)  Generates List of Values dialog boxes at the time of viewing or setting a schedule for Crystal Reports documents  Allows to modify or create brand new Crystal Reports documents over the web Used when:  Crystal Reports are being viewed (objects or instances) and preferences for viewing Crystal Reports within user’s InfoView are set to Interactive Viewer (Not ActiveX, DHTML or Java)  Crystal Reports are being modified via web InfoView  Crystal Reports that use List of Values objects are being viewed (regardless of preferences) or set to schedule Communicates with:  CMS, WAS, Input, Output, CR PS (generate List of Values), CR JS (generate List of Values) Additional information:  Can be memory and CPU intensive process

Crystal Reports Job Server

Main function:  Creates successful Crystal Reports document instances (in various formats) and sends them to various destinations after Crystal Reports objects have been scheduled Used when:  Crystal Reports are being processed after they have been scheduled Communicates with:  CMS, WAS, Input, Output, RAS (generate List of Values) Additional information:  Can be memory and CPU intensive process

Desktop Intelligence Report Server

Main function:  Generates viewable pages for Desktop Intelligence documents (objects or instances) Used when:  Desktop Intelligence are being viewed (objects or instances) and preferences for viewing Desktop Intelligence within user’s InfoView are set to DHTML (Not BusinessObjects Windows only) Communicates with:  CMS, WAS, Deski CS, Input FRS, Output FRS Additional information:  Can be memory and CPU intensive process

Desktop Intelligence Cache Server

Main function:  Manages and stores viewable pages for Desktop Intelligence documents (objects or instances) that were generated by the Deski RS  Useful especially when multiple users are viewing the same Desktop Intelligence document Used when:  Desktop Intelligence documents are being viewed (objects or instances) and preferences for viewing  Desktop Intelligence documents within user’s InfoView are set to DHTML (Not BusinessObjects format Windows only) Communicates with:  CMS, WAS, Deski RS Additional information:  Light on resources

Desktop Intelligence Job Server

Main function:  Creates successful Desktop Intelligence document instances (in various formats) after Desktop Intelligence objects have been scheduled Used when:  Desktop Intelligence documents are being processed after they have been scheduled Communicates with:  CMS, WAS, Input, Output Additional information:  Can be memory and CPU intensive process

Connection Server

Main function:  Executes SQL statements against the production database when Desktop Intelligence documents are viewed in 3-tier mode Used when:  Desktop Intelligence documents are being refreshed (objects or instances) and preferences for viewing Desktop Intelligence within user’s InfoView are set to BusinessObjects Format (Windows only) (Not DHTML)  Desktop Intelligence documents are being refreshed from within Desktop Intelligence application; and user when logging for the system dialog box decided to choose .NET Portal or Java Portal option Communicates with:  CMS, WAS  Indirectly with Desktop Intelligence application (windows) Additional information:  Can be memory and CPU intensive process  Makes it possible for end-users to avoid having to install middleware to communicate

Web Intelligence Report Server
Main function:  Generates viewable pages for Web Intelligence documents (objects or instances) Creates successful instances for Web Intelligence documents at the time of executing a schedule  request Used when:  Web Intelligence are being viewed (objects or instances) and preferences for viewing Web Intelligence  within user’s InfoView are set to DHTML or Interactive  Web Intelligence documents are being processed after they have been scheduled Communicates with:  CMS, WAS, Webi JS, Input FRS, Output FRS Additional information:  Can be memory and CPU intensive process

Web Intelligence job Server

Main function:  Passes a Web Intelligence schedule request to Web Intelligence Report Server Used when:  Web Intelligence documents are being processed after they have been scheduled Communicates with:  CMS, WAS, Webi JS Additional information:  Light on resources

Event Server

Main function:  Monitors whether certain file has been created and when that happens it is responsible to let the CMS know that the condition has been met Used when:  Various documents (.rpt, .rep, .wid, .exe) are scheduled with the File Event dependency (not Custom or Schedule, which are monitored by the CMS) Communicates with:  CMS, WAS Additional information:  Light on resources

Program Job Server

Main function:  Creates successful program instances after executable or batch object have been scheduled (executable or a batch file get spawned by Program JS)  The successful program instance is typically a log file of the transaction that has been spawned Used when:  Executable or batch process objects are being processed after they have been scheduled Communicates with:  CMS, WAS, Input, Output Additional information:  Light on resources

Destination Job Server
Main function:  Sends either document objects or successful instances to various destinations without processing them (does not connect to a production database)  Not used at the time of executing a schedule request Used when:  Objects or instances are being sent to various destinations (InfoView or CMC interface). It is not being  used when other Job Servers are executing schedule requests to various destinations. Other Job  Servers (Crystal Reports, Desktop Intelligence, Web Intelligence) can schedule respective objects to  various destinations without involvement of the Destination Server Communicates with:  CMS, WAS, Input, Output Additional information:  Light on resources

Thank You

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close