Está en la página 1de 17

Applications in this Image (descriptions

and links to the client GUIs)


Overview (for logon information check
SAS_Client_Logon.docx on the desktop)
IMPORTANT

You need to verify that JBoss has powered up completely before starting up the
Analytical Platform service. You know that JBoss has started completely when the
memory usage of its Java process shows memory usage of 1.85-1.88Gb as shown in
the next screen shot. In addition, you can check the Application server log at: C:\jboss-
4.2.0.GA\server\SASServer1\log\server.log. When the size of this log reaches about
1030-1035Kbytes then JBoss has started. I would recommend that, if you shut down
JBoss, delete the above log and the file boot.log in the same directory, before re-
starting JBoss. This way you can use the size of the log as an indication of JBoss
status. If you do now allow for JBoss to start completely you will most likely have
problems with using the SAS applications.
2. Once you have verified that JBoss has started completely as per the instructions
above you can fire-up the Analytics Platform service:
Now you are ready to work with the solutions in the image:

The image has installed and configured the following Risk and Analytics solutions:
 Risk Management for Banking 2.1
 Risk Management for Insurance 1.2
 Credit Risk Management for Banking 4.6
 Enterprise Model Management 2.2
 Forecast Server 3.1
 DataFlux 8.1
 Platform LSF 7.0. LSF services have been set-up as Manual to limit the number
of concurrent processes running. Should one wish to demo scheduling features
then the following services should be started where the value for "log on
as"=.\lsfadmin
Please bear in mind that the remaining free disk space is relatively
small: <10Gb.

SAS Application Servers


To access the web client applications either select
from the links in the rest of the document or open the
folder "CLIENTS" on the Desktop
SASMeta - Metadata Server
Host
sasbi.demo.sas.com
machine
Port 8561
C:\SAS\Config\Lev1\SASMeta\MetadataServer\Logs
For more details about the initial logging configuration and how to modify it,
Log
see "Administering Logging for SAS Servers" in the SAS Intelligence
directory
Platform: System Administration Guide at
http://support.sas.com/92administration.
SASApp - OLAP Server
Host
sasbi.demo.sas.com
machine
Port 5451
C:\SAS\Config\Lev1\SASApp\OLAPServer\Logs
For more details about the initial logging configuration and how to modify it,
Log
see "Administering Logging for SAS Servers" in the SAS Intelligence
directory
Platform: System Administration Guide at
http://support.sas.com/92administration.
SASApp - Stored Process Server
Host
sasbi.demo.sas.com
machine
Port 8601
C:\SAS\Config\Lev1\SASApp\StoredProcessServer\Logs
For more details about the initial logging configuration and how to modify it,
Log
see "Administering Logging for SAS Servers" in the SAS Intelligence
directory
Platform: System Administration Guide at
http://support.sas.com/92administration.
SASApp - Workspace Server
Host
sasbi.demo.sas.com
machine
Port 8591
C:\SAS\Config\Lev1\SASApp\WorkspaceServer\Logs
For more details about the initial logging configuration and how to modify it,
Log
see "Administering Logging for SAS Servers" in the SAS Intelligence
directory
Platform: System Administration Guide at
http://support.sas.com/92administration.

SASApp - Pooled Workspace Server


Host machine sasbi.demo.sas.com
Port 8701
Log Directory 1. C:\SAS\Config\Lev1\SASApp\PooledWorkspaceServer\Logs

SASApp - SAS DATA Step Batch Server


Host
sasbi.demo.sas.com
machine
C:\SAS\Config\Lev1\SASApp\BatchServer\Logs
For more details about the initial logging configuration and how to modify it,
Log
see "Administering Logging for SAS Servers" in the SAS Intelligence
directory
Platform: System Administration Guide at
http://support.sas.com/92administration.

SAS Spawners
Object Spawner
Host
sasbi.demo.sas.com
machine
Port 8581
C:\SAS\Config\Lev1\ObjectSpawner\Logs
For more details about the initial logging configuration and how to modify it,
Log
see "Administering Logging for SAS Servers" in the SAS Intelligence
directory
Platform: System Administration Guide at
http://support.sas.com/92administration.
Connect Spawner
Host
sasbi.demo.sas.com
machine
Ports 7551
C:\SAS\Config\Lev1\SASApp\ConnectServer\Logs
For more details about the initial logging configuration and how to modify it,
Log
see "Administering Logging for SAS Servers" in the SAS Intelligence
directory
Platform: System Administration Guide at
http://support.sas.com/92administration.

SAS Table Server


Host
sasbi.demo.sas.com
machine
Port 2171
C:\SAS\Config\Lev1\SASTS\TableServer\Logs
For more details about the initial logging configuration and how to modify it,
Log
see "Administering Logging for SAS Servers" in the SAS Intelligence
directory
Platform: System Administration Guide at
http://support.sas.com/92administration.

SAS/SHARE Server
Host
sasbi.demo.sas.com
machine
Port 8551
C:\SAS\Config\Lev1\ShareServer\Logs
For more details about the initial logging configuration and how to modify it,
Log
see "Administering Logging for SAS Servers" in the SAS Intelligence
directory
Platform: System Administration Guide at
http://support.sas.com/92administration.

SAS Risk Management


SAS Risk Management for Banking
URL http://sasbi.demo.sas.com:8080/SASRiskManagementForBanking
Utility to
create To create the sample portal pages, see the section titled "Creating the SAS
sample Risk Management for Banking Sample Portal Pages" in the SAS Risk
portal Management For Banking 2.1 Administrator's Guide.
pages
SAS Risk Management for Insurance
URL http://sasbi.demo.sas.com:8080/SASRiskManagementForInsurance
Utility to To create the sample portal pages, see the section titled "Creating the SAS
create
sample Risk Management for Insurance Sample Portal Pages" in the SAS Risk
portal Management For Insurance 1.2 Administrator's Guide.
pages
SAS Credit Risk Studio Mid-Tier for CRMS 4.6
URL http://sasbi.demo.sas.com:8080/SASCreditRiskManagement
C:\SAS\Config\Lev1\Web\Logs\SASCreditRiskManagement4.6.log
For more details about how to modify your log format and to see what
Log file logging entails, see "Logging for SAS Web Applications" in the SAS
Intelligence Platform: Web Application Administration Guide at
http://support.sas.com/92administration.
1. Access the URL provided above.
Validation 2. Login using the valid credentials defined in the SAS Metadata
steps Server.

when you select the regulatory reports (as per the screen shot below) you will notice than when
you click in a non-PDF report you will be prompted TWICE for the logon credentials. Each time
submit the logon with the default logon: userid=demoadm and password=Orion123.
SAS Information Delivery Portal
URL http://sasbi.demo.sas.com:8080/SASPortal
C:\SAS\Config\Lev1\Web\Logs\SASPortal4.2.log
For more details about how to modify your log format and to see what logging
Log
entails, see "Logging for SAS Web Applications" in the SAS Intelligence
file
Platform: Web Application Administration Guide at
http://support.sas.com/92administration.

Here is a screen shot from the “unified” Portal. The first 4 tabs (from left to right) are for
RMB. The next 5 are for CRMS. The next two for RMI and the last one for Credit
Scoring. As you can see there are Flex based Dashboards.  You will notice that when
you click on any link once you are on the last tab (PD/LGD/CCF Modeling=Credit
Scoring 4.4) it asks you again for your login. One way to avoid this in a demo is to go to
the properties of each of these links and submit them from IE directly.
 
 

SAS Web Infrastructure Platform


Log directory C:\SAS\Config\Lev1\Web\Logs

SAS Content Server


C:\SAS\Config\Lev1\Web\Logs\SASContentServer.log
Log file For the Application Server (JBoss) the log file is lcoated in:
C:\jboss-4.2.0.GA\server\SASServer1\log
Locatio http://sasbi.demo.sas.com:8080/SASContentServer/dircontents.jsp?
n path=/sasdav

SAS Stored Process Web Application


URL http://sasbi.demo.sas.com:8080/SASStoredProcess/do
Log file C:\SAS\Config\Lev1\Web\Logs\SASStoredProcess9.2.log

SAS Web Report Studio


URL http://sasbi.demo.sas.com:8080/SASWebReportStudio
C:\SAS\Config\Lev1\Web\Logs\SASWebReportStudio4.2.log
For more details about how to modify your log format and to see what
Log
logging entails, see "Logging for SAS Web Applications" in the SAS
directory
Intelligence Platform: Web Application Administration Guide at
http://support.sas.com/92administration.
SAS Web OLAP Viewer for Java
URL http://sasbi.demo.sas.com:8080/SASWebOLAPViewer
C:\SAS\Config\Lev1\Web\Logs\SASWebOLAPViewer4.2.log
For more details about how to modify your log format and to see what logging
Log
entails, see "Logging for SAS Web Applications" in the SAS Intelligence
file
Platform: Web Application Administration Guide at
http://support.sas.com/92administration.;
SAS BI Portlets
Log C:\SAS\Config\Lev1\Web\Logs\SASBIPortlets4.2.log
file For more details about how to modify your log format and to see what logging
entails, see "Logging for SAS Web Applications" in the SAS Intelligence
Platform: Web Application Administration Guide at
http://support.sas.com/92administration.

SAS Shared Services


Log directory C:\SAS\Config\Lev1\Web\Logs
Notes:
SAS BI Dashboard 4.2
URL http://sasbi.demo.sas.com:8080/SASBIDashboard
C:\SAS\Config\Lev1\Web\Logs\SASBIDashboard4.2.log
For more details about how to modify your log format and to see what
Log
logging entails, see "Logging for SAS Web Applications" in the SAS
directory
Intelligence Platform: Web Application Administration Guide at
http://support.sas.com/92administration.

Analytics
SAS Analytics Platform
Host machine sasbi.demo.sas.com
HTTP server
6401
port
RMI Registry
6411
port
RMI service
6421
port
RMI security Use plain-text sockets for all RMI services.
Foundation
Services
Analytics Platform 1.5
deployment
name
Windows service
Execution type
SAS [Config-Lev1] Analytics Platform Server
Shortcuts Programs > SAS > SAS Configuration > Config - Lev1
Log directory C:\SAS\Config\Lev1\AnalyticsPlatform\Logs
Access in http://sasbi.demo.sas.com:6401/AnalyticsPlatform
Administrator's Additional information useful in administering the SAS Analytics
Platform can be found in the Administrator's Guide for SAS Analytics
Guide Platform 1.5 at
http://support.sas.com/documentation/onlinedoc/apcore/index.html.
SAS Model Manager
SAS
Analytics
sasbi.demo.sas.com
Platform
server
1. Using a web browser go to
http://sasbi.demo.sas.com:6401/AnalyticsPlatform
2. Click on the Applications tab; then under the Applications section
you should see:
Name Version Loaded Clients Java Webstart
ModelManager 2.2 Yes 0  Launch 
Access
via 3. Note: Additional information about SAS Model Manager startup
errors can be found in the SAS Analytics Platform's log file:
C:\SAS\Config\Lev1\AnalyticsPlatform\Logs\AnalyticsPlatform.log
and services log file:
C:\SAS\Config\Lev1\AnalyticsPlatform\Logs\wrapper.log.
 The "SAS Model Manager 2.2: Administrator's Guide" can be found
at http://support.sas.com/documentation/onlinedoc/modelmgr/.

SAS Forecast Server


SAS Analytics
sasbi.demo.sas.com
Platform server
Access to SAS
Forecast Studio
tasks by SAS
Add-In for Enabled
Microsoft Office
and SAS
Enterprise Guide
Reports are not enabled for environments that are created during a
new deployment or a migration. For more information about report
Report configuration including how to deploy the sample reports, see the
administration "SAS Forecast Server 3.1: Administrator's Guide to Report
Administration Tasks" at
http://support.sas.com/documentation/onlinedoc/forecast/.
Same as above=via the same link:
http://sasbi.demo.sas.com:6401/AnalyticsPlatform
Note: If there are any validation errors, see the SAS Analytics
Platform's log files located in
Access via C:\SAS\Config\Lev1\AnalyticsPlatform\Logs for additional
information.
For more information, see the "SAS Forecast Server 3.1:
Administrator's Guide to Post-installation Tasks" documentation at
http://support.sas.com/documentation/onlinedoc/forecast/.

SAS Enterprise Miner Client


Host machine sasbi.demo.sas.com
Port 6401
Shortcuts Programs > SAS > Analytics > SAS Enterprise Miner Client 6.1
C:\SAS\Config\Lev1\AnalyticsPlatform\apps\EnterpriseMiner\Logs
For more details about how to modify your log format and to see
Log directory
what logging entails, view the SAS 9.2 Logging Administration and
Programming Guide.
Additional information useful in administering the SAS Enterprise
Administrator's Miner can be found in the SAS Enterprise Miner 6.1 Online
Guide documents at
http://support.sas.com/documentation/onlinedoc/miner/index.html.

Validation Same as above=via the same link:


steps http://sasbi.demo.sas.com:6401/AnalyticsPlatform

If disk space is an issue, then use the SAS Backup wizard provided in the SAS
Management Console Metadata Manager or the %OMABAKUP macro to perform the
backup. Both of these tools copy all critical metadata server files and permit you to
specify a different backup destination. For more information, see "About the Backup
Wizard" and "About %OMABAKUP" in the SAS Intelligence Platform: System
Administration Guide at http://support.sas.com/92administration.
Regular metadata server backups using SAS backup tools are crucial to ensuring the
health of your SAS 9.2 Intelligence Platform configuration, but they are just one part of
backing up a SAS Intelligence Platform configuration. To devise a backup strategy for
your entire SAS Intelligence Platform configuration, see "Best Practices for Backing Up
and Restoring Your System" in the SAS Intelligence Platform: System Administration
Guide at http://support.sas.com/92administration.

Copyright © 2008-9 SAS Institute Inc., Cary, NC, USA. All Rights Reserved.

También podría gustarte