Previous Page | Next Page

Working in the Middle-Tier Environment

Starting the Web Applications

Main Steps for Starting the Web Applications

To start the Web applications, follow these steps:

  1. Start the necessary servers and services in the correct order. For the correct start-up order, see Starting Servers in the Correct Order.

  2. Start a browser session and point the browser to the Web application that you want to access. For the correct URL, see the Instructions.html document, which resides in the Documents subdirectory of your configuration directory. The exact URL varies with the Web application server that you are using and the configuration that you have defined for your environment.

  3. Log on to the Web application. For instructions about logging on to a Web application, see the online Help that is provided with the application.

Required Servers

In order for clients to access the SAS Intelligence Platform, the following components must be running on network-accessible machines:

Depending on which SAS products you have installed, one or more instances of the following additional components might also be required to be running on network-accessible machines:

For example, the following table documents some SAS servers that can be involved when a user accesses a stored process or a report.

Examples of Server Interactions for Stored Processes and Reports
Object Type SAS Servers
Stored process

  • Metadata server

  • Workspace server (for package results) or stored process server (for streaming results)1
Report

  • Metadata server

  • Workspace server1 (for relational data)

  • OLAP server (for multidimensional data)

  • SAS Content Server (for retrieval from WebDAV)
1 Workspace servers and stored process servers have a dependency on the object spawner.

Starting Servers in the Correct Order

Because of dependencies, it is important to start the servers in the correct order. Server dependencies are explained in the SAS Intelligence Platform: System Administration Guide. The following is an example of a start-up order that meets the dependency requirements for servers:

  1. Start the SAS Metadata Server

  2. Start the SAS OLAP Server

  3. Start SAS object spawner

  4. Start the SAS/SHARE server

  5. Start the SAS/CONNECT server

  6. Start the SAS Table Server

  7. Start the SAS Services Application (Remote Services)

  8. Start the Web application server. (The SAS Content Server starts automatically when the application server is started).

The SAS OLAP Server, SAS/CONNECT Spawner, and SAS/SHARE Server can be started anytime after the SAS Metadata Server has been started.

Servers should be stopped in the inverse order, with the metadata server stopped last.

Deploying EAR Files in the Correct Order

The SAS Deployment Wizard deploys SAS Web applications to the Web application server. However, you can also deploy EAR files manually from the Web application server. EAR files reside in the SAS-configuration-directory\Lev1\Web\Staging directory.

There is no required start-up order for deploying the EAR files to JBoss or WebLogic. Although, you can deploy the EAR files in any order of your choice, it is highly recommended that you follow this sequence for WebSphere.

  1. SAS Web Application Themes (sas.themes.ear)

  2. SAS Flex Application Themes (sas.flexthemes.ear)

  3. SAS Web Infrastructure Platform Services (sas.wip.services9.2.ear)

  4. SAS Web Infrastructure Platform Applications (sas.wip.apps9.2.ear)

  5. SAS Content Server (sas.wip.scs9.2.ear)

  6. SAS Stored Process Application (sas.storedprocess9.2.ear)

  7. SAS Information Delivery Portal 4.3 (sas.portal4.3.ear)

  8. SAS Package Viewer 4.3 (sas.packageviewer4.3.ear)

  9. SAS Web Report Studio 4.3 (sas.webreportstudio4.3.ear)

  10. SAS Shared Services Application (sas.shared9.2.ear)

  11. SAS BI Dashboard 4.3 (sas.bidashboard4.3.ear)

  12. SAS BI Portlets (sas.biportlets4.3 ear)

  13. SAS Help Viewer Metadata Configuration (webdocmd9.2.ear)

Previous Page | Next Page | Top of Page

Copyright © 2010 by SAS Institute Inc., Cary, NC, USA. All rights reserved.