SAS 9.3 Web Applications: Clustering - Index of - SAS

More documents

Recommendations

Info

50 Chapter 5 / IBM WebSphere Application Server 7.0 Clustering that either a JDBC data source has been configured in the administration console, or know the network storage location that will be used. To reconfigure the SAS Messaging Bus and add SASCluster as a member, follow these steps: Add SASCluster as a Bus Member 1 Select Service integration � Buses � SAS Messaging Bus, and then select Bus members. 2 Click Add, select Cluster, and select the cluster name from the menu. Click Next. 3 Clear the check box for Enable messaging engine policy assistance? and click Next. 4 Choose either File store or Data store and click Next. 5 For deployments that use a network storage location for a file store, provide the path to the directory for log files and the directory for the message store. For deployments that use a JDBC data source as the data store, provide the JNDI name of the data source. Click Next. For more information about configuring a message store, see the WebSphere Application Server help. Create and Use Destinations on the Bus These steps describe creating new destinations on the service integration bus for the queues and topics that are used by the SAS Web applications. The new destinations are assigned to use the cluster as the bus member. 6 Select Resources � JMS � Queues. For each queue that is listed, follow these steps to reconnect the queue to the SAS Messaging Bus: a Click the queue name. b In the Administration area, copy the queue name, such as AlertQueue, to your clipboard. c Select Create Service Integration Bus destination from the Queue name menu. d Paste the queue name in the Identifier text field, add "SIB" to the end of the name, and click Next. e Select the cluster name from the Bus member menu and click Next. Click Finish. 6 Select Service integration � Buses � SAS Messaging Bus, and then select Destinations. 7 Delete the queue destinations that were originally used by the SAS Web applications. These destinations do not have names with the "QueueSIB" suffix.
Configure a Load Balancing HTTP Server Load balancing the HTTP requests to the application server instances can be accomplished in many ways, using hardware or software. One option for load balancing HTTP requests is to configure IBM HTTP Server for load balancing. For more information about performing this configuration, see Configuring IBM HTTP Server as a Reverse Proxy Server for SAS 9.3 Web Applications Deployed on IBM WebSphere Application Server or IBM documentation. WebSphere Application Server settings must be changed so that SAS Content Server is available from IBM HTTP Server. These changes enable IBM HTTP Server to accept content, such as attachments, with HTTP requests. Follow these steps in the WebSphere administrative console: 1 Change the virtual host for the SAS Content Server application to the default host. 2 Select Servers � Server Types � Web servers � webserver1 � Plug-in properties. 3 Select the Accept content for all requests check box 4 Click OK and then save the changes to the master configuration. After you configure the HTTP server, regenerate the Web server plug-in configuration file and propagate it. Perform Common Configuration Tasks Perform Common Configuration Tasks 51 To complete WebSphere Application Server clustering, perform the tasks in “Common Tasks” on page 53.
Page 1 and 2:
SAS ® Clustering 9.3 Web Applicati
Page 3 and 4:
Contents What’s New in SAS Web Ap
Page 5 and 6: What’s New in SAS Web Application
Page 7 and 8: Overview 1 Web Application Server C
Page 9 and 10: configuration tasks. As a result of
Page 11 and 12: Common Pre-Configuration Tasks Purp
Page 13 and 14: n For JBoss, edit the WEB-INF/jboss
Page 15 and 16: Reconfigure SAS Workflow Follow the
Page 17 and 18: false 20000 15000
Page 19 and 20: ${workflow.hibernate.dialect} true
Page 21 and 22: value="/opt/SAS/Config/Lev1/Web/Log
Page 23 and 24: JBoss Clustering 3 JBoss Clustering
Page 25 and 26: Create Additional JBoss Server Inst
Page 27 and 28:
Page 29 and 30: 2 For all servers except the stand-
Page 31 and 32: SAS Web applications and are config
Page 33 and 34: Configure JBoss to Use mod_jk At th
Page 35 and 36: Oracle WebLogic Server 11g Clusteri
Page 37 and 38: The tasks in the following sections
Page 39 and 40: 3 Click the link for the newly adde
Page 41 and 42: Create a JMS Module managed server,
Page 43 and 44: Name Local JNDI Name Remote JNDI Na
Page 45 and 46: Configure a Load Balancing HTTP Ser
Page 47 and 48: MatchExpression /SASBIDashboard Web
Page 49 and 50: IBM WebSphere Application Server 7.
Page 51 and 52: The tasks in the following sections
Page 53 and 54: Configure JVM Options Each server i
Page 55: Application Target SASThemes9.3 Do
Page 59 and 60: Common Tasks 6 Confirm the SAS Web
Page 61 and 62: metadata. Change the connection inf
Page 63 and 64: Start Software in the Correct Seque
show all

SAS 9.3 Web Applications: Clustering - Index of - SAS

Create successful ePaper yourself

Delete template?

Save as template?