The following issues occurred during the automated portion of your configuration and must be addressed before proceeding.
SAS Management Console is required to complete many of the following steps.
The following is the general overview of the steps required to create the WebSphere dmgr "Dmgr01" profile:
At this point, the dmgr profile "Dmgr01" should be created.
The following is the general overview of the steps required to create the WebSphere custom managed node "AppSrv01" profile:
Create a new application server "server1" using the WAS Admin Console.
- Use Servers->Application servers->New navigation to create a new application server.
- Ensure that HOSTNAMENode01 node has been selected in the "Select node" drop-down menu.
- Enter "server1" in required "Server name" field.
- Select the "default" server template radio button.
- Check the "Generate unique ports" checkbox.
- Save your work after reviewing the summary page.
Set Http Ports for "server1" to the following values by either editing the
"C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\HOSTNAMECell01\nodes\HOSTNAMENode01\serverindex.xml"
file or using the WAS Admin Console by navigating to Application servers->server1->Ports to perform this function.
- Set server1 WC_defaulthost port to 9080
- Set server1 WC_defaulthost_secure port to 9443
Set the Http ports for the default_host virtualhost alias to match the Http ports for "server1".
The following Http port values should be set by either editing the
"C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\HOSTNAMECell01\virtualhosts.xml
file or using the WAS Admin Console by navigating to Environment->Virtual Hosts->default_host->Host Aliases to perform this task.
- Set the default_host alias for "*" to match the Http port 9080 for server1
- Set the default_host alias for "*" to match the Https port 9443 for server1
Set Generic JVM Arguments for server "server1" using the WAS Admin Console.
after navigating to Application servers->server1->Java and Process Management->Process Definition->Java Virtual Machine.
server1 Generic JVM Arguments (exclude the beginning and ending "quotes"):
- Set server1 "Initial Heap Size" to 1024
- Set server1 "Maximum Heap Size" to 2048
- Set server1 Generic JVM Arguments to: "-Xms1024m -Xmx2048m -Xss256k -Xmso256k -Xgcpolicy:optavgpause -Djavax.management.builder.initial= -Dcom.sun.management.jmxremote -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.awt.headless=true -Dsas.container.identifier=websphere -Dsas.auto.publish.port=9080 -Dcom.sas.services.logging.disableRemoteList=true -Dcom.sas.services.logging.disableRemoteLogging=true -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false -Dmulticast_udp_ip_ttl=0 -Dmulticast.address=235.1.1.1 -Dmulticast.port=31001 -Dcom.sas.log.config.url=file:///C:/SAS/Config/Lev1/Web/Common/LogConfig/ " (NOTE: remember to exclude the beginning and ending quotes.)
Disable Java 2 Security for server "server1" using the WAS Admin Console.
Using the "Secure administration, applications, and infrastructure" menu in the WAS Admin Console, disable Java 2 Security by unchecking the "Java 2 security" checkbox.
Set the required Web Container custom properties for server "server1" using the WAS Admin Console.
Using the Application servers->server1->Web Container Settings->Web container->Custom Properties menu in the WAS Admin Console,
there are two custom properties that must be set for proper SAS web application function.
- Create a new property with a name of "prependSlashToResource" and a value of "true" (without the "quotes").
- Create a new property with a name of "com.ibm.ws.webcontainer.channelwritetype" and a value of "sync" (again, without the "quotes").
Create the Service Integration Bus for server "server1" using the WAS Admin Console.
Using the Service integration menu in the WAS Admin Console, create a new bus with the name "SAS Messaging Bus" (without the "quotes").
Add server "server1" as a member on the Service Integration Bus "SAS Messaging Bus" created in the step above using the WAS Admin Console.
From the the Service integration->Buses menu in the WAS Admin Console, select "SAS Messaging Bus", use the Bus members link to add "HOSTNAMENode01:server1" as a new member of the bus.
The "Server" radio button should be selected with the "HOSTNAMENode01:server1" (without the "quotes") drop-down menu item.
Choose all the pre-selected and pre-filled defaults on the remaining definition pages.
After saving your work, perform a Full Resynchronize of the dmgr and nodeagent using the WAS Admin Console.
From the the System administration menu, choose the "HOSTNAMENode01" and perform a Full Resynchronize to ensure all new server definitions
are propagated from the master repository to the nodeagent.
Creation of server "server1" should now be complete.
The base JVM and Web Container configuration for the new "server1" has been completed. All remaining configuration steps will use these base
server definitions to complete the customization of the J2EE server functions for the SAS web applications.
Create a Mail Session named "SASMailSession" for server "server1"
Use the Resources->Mail->Mail sessions menu on the WAS Admin Console to create Mail Session "SASMailSession"
- Before clicking New, be sure the scope is set to "Node=HOSTNAMENode01, Server=server1" for the new Mail Session definition.
- On the new Mail Session defintion page, the Provider drop-down menu can be left set to the WebSphere default "Built-in Mail Provider".
- Complete the required input fields as follows:
- Enter "SASMailSession" (without the "quotes") for the Mail Session Name.
- Set the JNDI name to "sas/mail/Session" (without the "quotes").
- Set the Mail transport host to "mailhost.example.com" (without the "quotes").
- Set the Mail transport protocol to "smtp" (without the "quotes").
- If the SMTP Mail tranport host requires authentication, a valid Mail transport user ID and Mail transport password must be entered.
- All remaining fields on the page should be remain unaltered - empty or pre-filled default values for the remaining input fields are adequate.
| Values for the Create Mail Session |
| Scope: |
Node=HOSTNAMENode01, Server=server1 |
| Mail Session Name: |
SASMailSession |
| JNDI Name: |
sas/mail/Session |
| SMTP Host Name: |
mailhost.example.com |
| Mail Debug: |
false |
| Mail Transport Protocol: |
smtp |
| Mail SMTP Host Requires Authentication: |
false |
Add the JAAS Alias "PFS" for JAAS Application Login Module "com.sas.services.security.login.OMILoginModule" to the cell configuration.
Use the WAS Admin Console to add JAAS Login Module Alias "PFS" for the JAAS Login Module "com.sas.services.security.login.OMILoginModule" to the Application logins at the cell level.
NOTE: surrounding "quotes" for any of the following values should NOT be entered in the input fields!
- Navigate to Security->Secure administration, applications, and infrastructure->Java Authentication and Authorization Service->Application logins.
- If the "PFS" alias name does not already exist, create a new "PFS" Alias (without the "quotes").
- Whether you have just created a new "PFS" Alias, or it was already present, click the "PFS" Alias link.
- Click the "JAAS login modules" link.
- On the JAAS login modules page, create a new Module class name with a value of "com.sas.services.security.login.OMILoginModule" (without the "quotes").
- Be sure to select "sufficient" from the Authentication strategy drop-down menu.
- Click the new JAAS Module class name link for "com.sas.services.security.login.OMILoginModule" on the JAAS login modules page.
- Select the "Custom properties" link for "com.sas.services.security.login.OMILoginModule".
- Use the following Custom Properties for JAAS Login Module "com.sas.services.security.login.OMILoginModule"
table and enter the name-value pairs for each row following the
"Custom Property Name:" and "Custom Property Value:"
headings as a custom property for the JAAS Login Module.
- Be sure to save your work and perform a full resynchronization.
| Values for JAAS Login Module general settings: |
| JAAS Application logins alias: |
PFS |
| JAAS Module Class name: |
com.sas.services.security.login.OMILoginModule |
| JAAS Authentication strategy: |
sufficient |
| Custom Properties for JAAS Login Module "com.sas.services.security.login.OMILoginModule" |
|---|
| Custom Property Name: | Custom Property Value: |
|---|
| host | HOSTNAME.example.com |
| port | 8561 |
| repository | Foundation |
| domain | DefaultAuth |
| debug | false |
| trusteduser | Enter the SAS trusted user ID |
| trustedpw | Enter the SAS-encoded password for the SAS trusted user ID. (Use this SAS program to encode the value: PROC PWENCODE IN='password'; RUN;) |
Add the JAAS Alias "PFS" for JAAS Application Login Module "com.sas.services.security.login.TrustedLoginModule" to the cell configuration.
Use the WAS Admin Console to add JAAS Login Module Alias "PFS" for the JAAS Login Module "com.sas.services.security.login.TrustedLoginModule" to the Application logins at the cell level.
NOTE: surrounding "quotes" for any of the following values should NOT be entered in the input fields!
- Navigate to Security->Secure administration, applications, and infrastructure->Java Authentication and Authorization Service->Application logins.
- If the "PFS" alias name does not already exist, create a new "PFS" Alias (without the "quotes").
- Whether you have just created a new "PFS" Alias, or it was already present, click the "PFS" Alias link.
- Click the "JAAS login modules" link.
- On the JAAS login modules page, create a new Module class name with a value of "com.sas.services.security.login.TrustedLoginModule" (without the "quotes").
- Be sure to select "optional" from the Authentication strategy drop-down menu.
- Click the new JAAS Module class name link for "com.sas.services.security.login.TrustedLoginModule" on the JAAS login modules page.
- Select the "Custom properties" link for "com.sas.services.security.login.TrustedLoginModule".
- Use the following Custom Properties for JAAS Login Module "com.sas.services.security.login.TrustedLoginModule"
table and enter the name-value pairs for each row following the
"Custom Property Name:" and "Custom Property Value:"
headings as a custom property for the JAAS Login Module.
- Be sure to save your work and perform a full resynchronization.
| Values for JAAS Login Module general settings: |
| JAAS Application logins alias: |
PFS |
| JAAS Module Class name: |
com.sas.services.security.login.TrustedLoginModule |
| JAAS Authentication strategy: |
optional |
| Custom Properties for JAAS Login Module "com.sas.services.security.login.TrustedLoginModule" |
|---|
| Custom Property Name: | Custom Property Value: |
|---|
| host | HOSTNAME.example.com |
| port | 8561 |
| repository | Foundation |
| domain | DefaultAuth |
| aliasdomain | MidtierInternal |
| debug | false |
| trusteduser | Enter the SAS trusted user ID |
| trustedpw | Enter the SAS-encoded password for the SAS trusted user ID. (Use this SAS program to encode the value: PROC PWENCODE IN='password'; RUN;) |
Add the JAAS Alias "UsernamePassword" for JAAS Application Login Module "com.platform.SASLogin.UsernamePasswordLogin" to the cell configuration.
Use the WAS Admin Console to add JAAS Login Module Alias "UsernamePassword" for the JAAS Login Module "com.platform.SASLogin.UsernamePasswordLogin" to the Application logins at the cell level.
NOTE: surrounding "quotes" for any of the following values should NOT be entered in the input fields!
- Navigate to Security->Secure administration, applications, and infrastructure->Java Authentication and Authorization Service->Application logins.
- If the "UsernamePassword" alias name does not already exist, create a new "UsernamePassword" Alias (without the "quotes").
- Whether you have just created a new "UsernamePassword" Alias, or it was already present, click the "UsernamePassword" Alias link.
- Click the "JAAS login modules" link.
- On the JAAS login modules page, create a new Module class name with a value of "com.platform.SASLogin.UsernamePasswordLogin" (without the "quotes").
- Be sure to select "required" from the Authentication strategy drop-down menu.
- Click the new JAAS Module class name link for "com.platform.SASLogin.UsernamePasswordLogin" on the JAAS login modules page.
- Select the "Custom properties" link for "com.platform.SASLogin.UsernamePasswordLogin".
- Use the following Custom Properties for JAAS Login Module "com.platform.SASLogin.UsernamePasswordLogin"
table and enter the name-value pairs for each row following the
"Custom Property Name:" and "Custom Property Value:"
headings as a custom property for the JAAS Login Module.
- Be sure to save your work and perform a full resynchronization.
| Values for JAAS Login Module general settings: |
| JAAS Application logins alias: |
UsernamePassword |
| JAAS Module Class name: |
com.platform.SASLogin.UsernamePasswordLogin |
| JAAS Authentication strategy: |
required |
| Custom Properties for JAAS Login Module "com.platform.SASLogin.UsernamePasswordLogin" |
|---|
| Custom Property Name: | Custom Property Value: |
|---|
| debug | false |
Add the JAAS Alias "SCS" for JAAS Application Login Module "com.sas.services.security.login.OMILoginModule" to the cell configuration.
Use the WAS Admin Console to add JAAS Login Module Alias "SCS" for the JAAS Login Module "com.sas.services.security.login.OMILoginModule" to the Application logins at the cell level.
NOTE: surrounding "quotes" for any of the following values should NOT be entered in the input fields!
- Navigate to Security->Secure administration, applications, and infrastructure->Java Authentication and Authorization Service->Application logins.
- If the "SCS" alias name does not already exist, create a new "SCS" Alias (without the "quotes").
- Whether you have just created a new "SCS" Alias, or it was already present, click the "SCS" Alias link.
- Click the "JAAS login modules" link.
- On the JAAS login modules page, create a new Module class name with a value of "com.sas.services.security.login.OMILoginModule" (without the "quotes").
- Be sure to select "required" from the Authentication strategy drop-down menu.
- Click the new JAAS Module class name link for "com.sas.services.security.login.OMILoginModule" on the JAAS login modules page.
- Select the "Custom properties" link for "com.sas.services.security.login.OMILoginModule".
- Use the following Custom Properties for JAAS Login Module "com.sas.services.security.login.OMILoginModule"
table and enter the name-value pairs for each row following the
"Custom Property Name:" and "Custom Property Value:"
headings as a custom property for the JAAS Login Module.
- Be sure to save your work and perform a full resynchronization.
| Values for JAAS Login Module general settings: |
| JAAS Application logins alias: |
SCS |
| JAAS Module Class name: |
com.sas.services.security.login.OMILoginModule |
| JAAS Authentication strategy: |
required |
| Custom Properties for JAAS Login Module "com.sas.services.security.login.OMILoginModule" |
|---|
| Custom Property Name: | Custom Property Value: |
|---|
| host | HOSTNAME.example.com |
| port | 8561 |
| repository | Foundation |
| domain | DefaultAuth |
| debug | false |
| holdopenconnection | true |
| trusteduser | Enter the SAS trusted user ID |
| trustedpw | Enter the SAS-encoded password for the SAS trusted user ID. (Use this SAS program to encode the value: PROC PWENCODE IN='password'; RUN;) |
Starting WebSphere Application Server "server1"
If you haven't already done so, it's a good idea to perform a Full Resynchronize using the WAS Admin Console
before starting server "server1".
This can be done from the the System administration menu, choose the "HOSTNAMENode01" and perform a Full Resynchronize to ensure any new server definitions
are propagated from the master repository to the nodeagent.
Start the server "server1" using the "startServer" command.
Command to start server "server1": "C:\Program Files\IBM\WebSphere\AppServer\bin\startServer.bat" "server1" -profileName "AppSrv01"
Server "server1" should now be started.
You should see a process running representing the JVM for this server.
Create a JMS Topic Connection Factory "SASTopicConnectionFactory" at the "CELL" level.
Create a new JMS Topic Connection Factory "SASTopicConnectionFactory" definition at scope "HOSTNAMECell01" level.
- Navigate to Resources->JMS->Topic connection factories on the WAS Admin Console.
- Ensure the Scope is set to "Cell=HOSTNAMECell01" before clicking New.
- Be sure the "Default messaging provider" radio button is selected.
- There are 3 required fields (marked with "asterisks") on the "Configuration" page:
- Enter "SASTopicConnectionFactory" (without the "quotes") into the required "Name" field.
- Enter "sas/jms/TopicConnectionFactory" (without the "quotes") into the required "JNDI name" field.
- Select the "SAS Messaging Bus" from the required "Bus name" drop-down menu.
- Click the "Connection pool properties" link to set the following connection pool settings for this JMS Connection Factory:
- Connection timeout: 180
- Maximum connections: 10
- Minimum connections: 1
- Reap time: 180
- Unused timeout: 1800
- Aged timeout: 0
- Purge policy: EntirePool
- All remaining fields on the page should be remain unaltered - empty or pre-filled default values are for the remaining input fields are adequate.
- Be sure to Save your work.
You should perform a Full Resynchronize to ensure the new JMS Topic Connection Factory definition is propagated from the dmgr to the nodeagent.
Create a JMS Queue Connection Factory "SASQueueConnectionFactory" at the "CELL" level.
Create a new JMS Queue Connection Factory "SASQueueConnectionFactory" definition at scope "HOSTNAMECell01" level.
- Navigate to Resources->JMS->Queue connection factories on the WAS Admin Console.
- Ensure the Scope is set to "Cell=HOSTNAMECell01" before clicking New.
- Be sure the "Default messaging provider" radio button is selected.
- There are 3 required fields (marked with "asterisks") on the "Configuration" page:
- Enter "SASQueueConnectionFactory" (without the "quotes") into the required "Name" field.
- Enter "sas/jms/QueueConnectionFactory" (without the "quotes") into the required "JNDI name" field.
- Select the "SAS Messaging Bus" from the required "Bus name" drop-down menu.
- Click the "Connection pool properties" link to set the following connection pool settings for this JMS Connection Factory:
- Connection timeout: 180
- Maximum connections: 10
- Minimum connections: 1
- Reap time: 180
- Unused timeout: 1800
- Aged timeout: 0
- Purge policy: EntirePool
- All remaining fields on the page should be remain unaltered - empty or pre-filled default values are for the remaining input fields are adequate.
- Be sure to Save your work.
You should perform a Full Resynchronize to ensure the new JMS Queue Connection Factory definition is propagated from the dmgr to the nodeagent.
Create a JMS Queue "AlertQueue" and Service Integration Bus Destination "AlertQueue"
at the "CELL" level.
Create a new JMS Queue "AlertQueue" and Service Integration Bus Destination "AlertQueue" at scope "HOSTNAMECell01"
on SIBus "SAS Messaging Bus".
- Create the Service Integration Bus Queue destination "AlertQueue", if it doesn't already exist.
- Navigate to Service integration->Buses->, click the "SAS Messaging Bus" link, then click "Destinations".
- Click New and ensure the Queue radio button is selected.
- Enter "AlertQueue" (without the "quotes") in the required "Identifier" field.
- On the Assign the queue to a bus member page, select the entry for "Node=HOSTNAMENode01:Server=server1" from the Bus member drop-down menu.
- Next, create the JMS Queue with a Name of "AlertQueue" to be associated with the destination just created.
- Navigate to "Resources->JMS->Queues" menu on the WAS Admin Console.
- On the Queues page, be sure the scope setting "Cell=HOSTNAMECell01" is selected from the drop-down menu and click New.
- Make sure the "Default messaging provider" radio button is selected and click Ok.
- For the input fields on the Queues->Default messaging provider->New configuration page, complete the following fields:
- Name: AlertQueue
- JNDI Name: sas/jms/AlertQueue
- Bus name: Select "SAS Messaging Bus" from the drop-down menu.
- Queue name: Select "AlertQueue" from the drop-down menu. (The name of the new destination created above).
- Time to live: not-set (If "not-set", leave the field empty; otherwise enter time in milliseconds).
- Priority: not-set (If "not-set", leave the field empty; otherwise enter priority in range 0-9).
- Leave all other fields on the page empty or with their default pre-filled values and click Ok.
- Be sure to save your work and perform a Full Resynchronize to ensure the new definitions are propagated from dmgr to nodeagent.
Create a JMS Queue "WorkflowQueue" and Service Integration Bus Destination "WorkflowQueue"
at the "CELL" level.
Create a new JMS Queue "WorkflowQueue" and Service Integration Bus Destination "WorkflowQueue" at scope "HOSTNAMECell01"
on SIBus "SAS Messaging Bus".
- Create the Service Integration Bus Queue destination "WorkflowQueue", if it doesn't already exist.
- Navigate to Service integration->Buses->, click the "SAS Messaging Bus" link, then click "Destinations".
- Click New and ensure the Queue radio button is selected.
- Enter "WorkflowQueue" (without the "quotes") in the required "Identifier" field.
- On the Assign the queue to a bus member page, select the entry for "Node=HOSTNAMENode01:Server=server1" from the Bus member drop-down menu.
- Next, create the JMS Queue with a Name of "WorkflowQueue" to be associated with the destination just created.
- Navigate to "Resources->JMS->Queues" menu on the WAS Admin Console.
- On the Queues page, be sure the scope setting "Cell=HOSTNAMECell01" is selected from the drop-down menu and click New.
- Make sure the "Default messaging provider" radio button is selected and click Ok.
- For the input fields on the Queues->Default messaging provider->New configuration page, complete the following fields:
- Name: WorkflowQueue
- JNDI Name: sas/jms/WorkflowQueue
- Bus name: Select "SAS Messaging Bus" from the drop-down menu.
- Queue name: Select "WorkflowQueue" from the drop-down menu. (The name of the new destination created above).
- Time to live: not-set (If "not-set", leave the field empty; otherwise enter time in milliseconds).
- Priority: not-set (If "not-set", leave the field empty; otherwise enter priority in range 0-9).
- Leave all other fields on the page empty or with their default pre-filled values and click Ok.
- Be sure to save your work and perform a Full Resynchronize to ensure the new definitions are propagated from dmgr to nodeagent.
Create a JMS Queue "WorkflowCommandQueue" and Service Integration Bus Destination "WorkflowCommandQueue"
at the "CELL" level.
Create a new JMS Queue "WorkflowCommandQueue" and Service Integration Bus Destination "WorkflowCommandQueue" at scope "HOSTNAMECell01"
on SIBus "SAS Messaging Bus".
- Create the Service Integration Bus Queue destination "WorkflowCommandQueue", if it doesn't already exist.
- Navigate to Service integration->Buses->, click the "SAS Messaging Bus" link, then click "Destinations".
- Click New and ensure the Queue radio button is selected.
- Enter "WorkflowCommandQueue" (without the "quotes") in the required "Identifier" field.
- On the Assign the queue to a bus member page, select the entry for "Node=HOSTNAMENode01:Server=server1" from the Bus member drop-down menu.
- Next, create the JMS Queue with a Name of "WorkflowCommandQueue" to be associated with the destination just created.
- Navigate to "Resources->JMS->Queues" menu on the WAS Admin Console.
- On the Queues page, be sure the scope setting "Cell=HOSTNAMECell01" is selected from the drop-down menu and click New.
- Make sure the "Default messaging provider" radio button is selected and click Ok.
- For the input fields on the Queues->Default messaging provider->New configuration page, complete the following fields:
- Name: WorkflowCommandQueue
- JNDI Name: sas/jms/WorkflowCommandQueue
- Bus name: Select "SAS Messaging Bus" from the drop-down menu.
- Queue name: Select "WorkflowCommandQueue" from the drop-down menu. (The name of the new destination created above).
- Time to live: not-set (If "not-set", leave the field empty; otherwise enter time in milliseconds).
- Priority: not-set (If "not-set", leave the field empty; otherwise enter priority in range 0-9).
- Leave all other fields on the page empty or with their default pre-filled values and click Ok.
- Be sure to save your work and perform a Full Resynchronize to ensure the new definitions are propagated from dmgr to nodeagent.
Create a JMS Queue "WorkflowEventsQueue" and Service Integration Bus Destination "WorkflowEventsQueue"
at the "SERVER" level.
Create a new JMS Queue "WorkflowEventsQueue" and Service Integration Bus Destination "WorkflowEventsQueue" at scope "HOSTNAMECell01.HOSTNAMENode01.server1"
on SIBus "SAS Messaging Bus".
- Create the Service Integration Bus Queue destination "WorkflowEventsQueue", if it doesn't already exist.
- Navigate to Service integration->Buses->, click the "SAS Messaging Bus" link, then click "Destinations".
- Click New and ensure the Queue radio button is selected.
- Enter "WorkflowEventsQueue" (without the "quotes") in the required "Identifier" field.
- On the Assign the queue to a bus member page, select the entry for "Node=HOSTNAMENode01:Server=server1" from the Bus member drop-down menu.
- Next, create the JMS Queue with a Name of "WorkflowEventsQueue" to be associated with the destination just created.
- Navigate to "Resources->JMS->Queues" menu on the WAS Admin Console.
- On the Queues page, be sure the scope setting "Node=HOSTNAMENode01, Server=server1" is selected from the drop-down menu and click New.
- Make sure the "Default messaging provider" radio button is selected and click Ok.
- For the input fields on the Queues->Default messaging provider->New configuration page, complete the following fields:
- Name: WorkflowEventsQueue
- JNDI Name: sas/jms/app/WorkflowEventsQueue
- Bus name: Select "SAS Messaging Bus" from the drop-down menu.
- Queue name: Select "WorkflowEventsQueue" from the drop-down menu. (The name of the new destination created above).
- Time to live: not-set (If "not-set", leave the field empty; otherwise enter time in milliseconds).
- Priority: not-set (If "not-set", leave the field empty; otherwise enter priority in range 0-9).
- Leave all other fields on the page empty or with their default pre-filled values and click Ok.
- Be sure to save your work and perform a Full Resynchronize to ensure the new definitions are propagated from dmgr to nodeagent.
Create Data Source "SharedServices" at the "SERVER" level.
Use the "Resources->JDBC" menu on the WAS Admin Console to create the "SharedServices" JDBC Data Source definition.
NOTE: surrounding "quotes" for any of the following settings should NOT be entered into the WAS Admin input fields.
- Before creating the JDBC provider SharedServices SAS JDBC Provider and JDBC Data source SharedServices, you will need to create a "JAAS - J2C authentication data Alias"
entry named "SASJAASAlias". This will contain the User ID and password used to authenticate the connection to the "SharedServices" data source.
This alias will be referenced by during creation of the new JDBC data source "SharedServices".
- Navigate to the Security->Secure administration, applications, and infrastructure->Java Authentication and Authorization Service->J2C authentication data link.
- Create a new JAAS - J2C Alias entry for "SASJAASAlias" (without the "quotes").
- On the JAAS - J2C authentication data New page, enter the information below into the required fields:
- Alias: SASJAASAlias
- User ID: <Enter the user ID for connection to the database (Use the SAS trusted user ID when datasource is for SAS TableServer)>
- Password: <Enter the password for connection to the database (Use the unencoded-password for the SAS trusted user ID when datasource is for SAS TableServer)>.
NOTE: WAS will store this password using it's own encoding mechanism.
- Next, navigate to Resources->JDBC->JDBC Providers link.
- Ensure scope is set to "SERVER" level scope (HOSTNAMECell01.HOSTNAMENode01.server1) before creating the new "SharedServices SAS JDBC Provider" JDBC Provider.
- Enter the following values into the required fields:
- Database type: Choose "User-defined" from the drop-down menu
- Implementation class name: "com.sas.tkts.TKTSConnectionPoolDataSource" (without the "quotes")
- Name: "SharedServices SAS JDBC Provider" (without the "quotes")
- On the "Enter database class path information" page, enter each of the following classpath entries as a separate, new-line delimited string into the Classpath input box:
- C:\SAS\Config\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers\icu4j.jar
- C:\SAS\Config\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers\log4j.jar
- C:\SAS\Config\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers\sas.core.jar
- C:\SAS\Config\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers\sas.core.nls.jar
- C:\SAS\Config\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers\sas.icons.contents.jar
- C:\SAS\Config\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers\sas.icons.jar
- C:\SAS\Config\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers\sas.icons.nls.jar
- C:\SAS\Config\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers\sas.intrnet.javatools.jar
- C:\SAS\Config\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers\sas.intrnet.javatools.nls.jar
- C:\SAS\Config\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers\sas.nls.collator.jar
- C:\SAS\Config\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers\sas.oda.tkts.jar
- C:\SAS\Config\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers\sas.oda.tkts.nls.jar
- C:\SAS\Config\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers\sas.security.sspi.jar
- C:\SAS\Config\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers\sas.svc.connection.jar
- C:\SAS\Config\Lev1\Web\Applications\SASSharedServices9.2\JDBCDrivers\sas.svc.connection.nls.jar
- After reviewing the Summary information, you should be placed back on the JDBC providers page.
- Ensure server scope is set to "Node=HOSTNAMENode01,Server=server1" and click the link for the newly created "SharedServices SAS JDBC Provider" JDBC provider.
- From the "JDBC Providers->SharedServices SAS JDBC Provider" page, click the "Data sources" link.
- Create a data source "SharedServices" using the following values for the required fields:
- Data source name: "SharedServices" (without the "quotes")
- JNDI name: "sas/jdbc/SharedServices" (without the "quotes")
- Component-managed authentication alias and XA recovery authentication alias: SASJAASAlias
(i.e. choose the JAAS - J2C authentication data alias created above in the drop-down menu)
- Leave the "Data store helper class name" field as-is, it has been pre-filled with the WebSphere default helper class.
- Be sure to uncheck the "Use this data source in container managed persistence (CMP) checkbox".
- Review the Summary, you should be transferred back to the "JDBC providers->SharedServices SAS JDBC Provider->Data sources" page.
- Click the link for the newly created "SharedServices".
- Click the Custom Properties link. Enter a custom property name and value for the "SharedServices" data source to match each row in the following table.
NOTE: A custom property with a name of "connectionSharing" and a value of "1" may already be present.
Although this property does not appear in the table, it is optional and can safely remain. With exception of this property,
ensure that only those with names and values matching rows in the table are present. If required, delete any that do not match using the WAS Admin Console.
- After entering all custom properties and checking for accuracy, save your work and perform a Full Resynchronize to ensure the dmgr and nodeagent are updated.
| Custom Properties for Data Source "SharedServices" |
|---|
| Custom Property Name: | Custom Property Value: |
|---|
| user | Enter the SAS trusted user ID |
| password | Enter the unencoded-password for the SAS trusted user ID |
| serverName | HOSTNAME.example.com |
| portNumber | 2171 |
| serverUrl | jdbc:sastkts://HOSTNAME.example.com:2171 |
| dataSourceName | SharedServices |
| databaseName | SharedServices |
| serverName | HOSTNAME.example.com |
| portNumber | 2171 |
| stmtPooling | 0 |
| constring | (DSN=SharedServices) |
Deployment for application "SASWebInfrastructurePlatformServices9.2" on "server1".
Because you have NOT requested auto-configuration of WAS, or have NOT requested auto-deployment of the SAS web applications,
you must use the WAS Admin Console to manually deploy the "SASWebInfrastructurePlatformServices9.2" SAS web application.
Perform the following steps to deploy this application and make it ready for SAS operations:
- Navigate to Enterprise Applications->Install and under the Local file system radio button, enter "C:\SAS\Config\Lev1\Web\Staging\sas.wip.services9.2.ear" to locate the EAR for the SAS "SASWebInfrastructurePlatformServices9.2" application.
- Allow all other fields on this page to remain with the pre-filled values and click Next.
- On the "Select installation options" page, allow all fields to remain with pre-filled defaults, with exception of
"Deploy Web services" checkbox. Check this box to ensure the Web services deploy tool wsdeploy runs during application installation.
- Enter "SASWebInfrastructurePlatformServices9.2" (without the "quotes") into the Application name field.
- On the "Map modules to servers page", make sure the fully-qualified target server has been selected from the drop-down menu. It should be named
"WebSphere:cell=HOSTNAMECell01,node=HOSTNAMENode01,server=server1".
- Examine the summary page for accuracy, click Finish, and save your work after WAS indicates the application has been successfully deployed.
- Update the Classloader policy and mode for the EAR and the Classloader mode for EACH WAR module contained in the EAR.
- From the Enterprise Applications menu, select the "SASWebInfrastructurePlatformServices9.2" link.
- Click the "Classloading and update detection" link for the application EAR and ensure the "Classes loaded with application class loader first"
radio button is selected for this EAR.
NOTE: By default, the WAR Classloading policy at the EAR level is set to "MULTIPLE", so no action is required.
- You may be forced to enter a value in the "Polling intervalfor updated files", if so please enter "3" (without the "quotes"),
since 3 seconds is the WAS default.
- Back on the Enterprise Applications page for this application, click the "Manage Modules" link.
- You now must select EACH WAR module, choosing "Classes loaded with application class loader first" (i.e. "PARENT_LAST") from the drop-down menu for "Class loader order".
- You may wait until all WAR module Classloader modes have been set to "PARENT_LAST" before saving your work
- Set the application startup order to 2.
- From the Enterprise Applications menu, select the "SASWebInfrastructurePlatformServices9.2" link.
- Click the "Startup behavior" link.
- Enter "2" (without the "quotes") in the required "Startup order" field.
- Allow all other fields should remain empty or with their pre-filled values.
- You should perform a Full Resynchronize to ensure the new application definition is propagated between dmgr and the nodeagent.
- NOTE: Wait until all SAS web applications have been successfully deployed, then use the WAS Admin Console to start them by
selecting all applications and clicking Start.
Deployment for application "SASWebInfrastructurePlatformApplications9.2" on "server1".
Because you have NOT requested auto-configuration of WAS, or have NOT requested auto-deployment of the SAS web applications,
you must use the WAS Admin Console to manually deploy the "SASWebInfrastructurePlatformApplications9.2" SAS web application.
Perform the following steps to deploy this application and make it ready for SAS operations:
- Navigate to Enterprise Applications->Install and under the Local file system radio button, enter "C:\SAS\Config\Lev1\Web\Staging\sas.wip.apps9.2.ear" to locate the EAR for the SAS "SASWebInfrastructurePlatformApplications9.2" application.
- Allow all other fields on this page to remain with the pre-filled values and click Next.
- On the "Select installation options" page, allow all fields to remain with pre-filled defaults, with exception of
"Deploy Web services" checkbox. Check this box to ensure the Web services deploy tool wsdeploy runs during application installation.
- Enter "SASWebInfrastructurePlatformApplications9.2" (without the "quotes") into the Application name field.
- On the "Map modules to servers page", make sure the fully-qualified target server has been selected from the drop-down menu. It should be named
"WebSphere:cell=HOSTNAMECell01,node=HOSTNAMENode01,server=server1".
- Examine the summary page for accuracy, click Finish, and save your work after WAS indicates the application has been successfully deployed.
- Update the Classloader policy and mode for the EAR and the Classloader mode for EACH WAR module contained in the EAR.
- From the Enterprise Applications menu, select the "SASWebInfrastructurePlatformApplications9.2" link.
- Click the "Classloading and update detection" link for the application EAR and ensure the "Classes loaded with application class loader first"
radio button is selected for this EAR.
NOTE: By default, the WAR Classloading policy at the EAR level is set to "MULTIPLE", so no action is required.
- You may be forced to enter a value in the "Polling intervalfor updated files", if so please enter "3" (without the "quotes"),
since 3 seconds is the WAS default.
- Back on the Enterprise Applications page for this application, click the "Manage Modules" link.
- You now must select EACH WAR module, choosing "Classes loaded with application class loader first" (i.e. "PARENT_LAST") from the drop-down menu for "Class loader order".
- You may wait until all WAR module Classloader modes have been set to "PARENT_LAST" before saving your work
- Set the application startup order to 3.
- From the Enterprise Applications menu, select the "SASWebInfrastructurePlatformApplications9.2" link.
- Click the "Startup behavior" link.
- Enter "3" (without the "quotes") in the required "Startup order" field.
- Allow all other fields should remain empty or with their pre-filled values.
- You should perform a Full Resynchronize to ensure the new application definition is propagated between dmgr and the nodeagent.
- NOTE: Wait until all SAS web applications have been successfully deployed, then use the WAS Admin Console to start them by
selecting all applications and clicking Start.
Deployment for application "SASStoredProcessApplication9.2" on "server1".
Because you have NOT requested auto-configuration of WAS, or have NOT requested auto-deployment of the SAS web applications,
you must use the WAS Admin Console to manually deploy the "SASStoredProcessApplication9.2" SAS web application.
Perform the following steps to deploy this application and make it ready for SAS operations:
- Navigate to Enterprise Applications->Install and under the Local file system radio button, enter "C:\SAS\Config\Lev1\Web\Staging\sas.storedprocess9.2.ear" to locate the EAR for the SAS "SASStoredProcessApplication9.2" application.
- Allow all other fields on this page to remain with the pre-filled values and click Next.
- On the "Select installation options" page, allow all fields to remain with pre-filled defaults, with exception of
"Deploy Web services" checkbox. Check this box to ensure the Web services deploy tool wsdeploy runs during application installation.
- Enter "SASStoredProcessApplication9.2" (without the "quotes") into the Application name field.
- On the "Map modules to servers page", make sure the fully-qualified target server has been selected from the drop-down menu. It should be named
"WebSphere:cell=HOSTNAMECell01,node=HOSTNAMENode01,server=server1".
- Examine the summary page for accuracy, click Finish, and save your work after WAS indicates the application has been successfully deployed.
- Update the Classloader policy and mode for the EAR and the Classloader mode for EACH WAR module contained in the EAR.
- From the Enterprise Applications menu, select the "SASStoredProcessApplication9.2" link.
- Click the "Classloading and update detection" link for the application EAR and ensure the "Classes loaded with application class loader first"
radio button is selected for this EAR.
NOTE: By default, the WAR Classloading policy at the EAR level is set to "MULTIPLE", so no action is required.
- You may be forced to enter a value in the "Polling intervalfor updated files", if so please enter "3" (without the "quotes"),
since 3 seconds is the WAS default.
- Back on the Enterprise Applications page for this application, click the "Manage Modules" link.
- You now must select EACH WAR module, choosing "Classes loaded with application class loader first" (i.e. "PARENT_LAST") from the drop-down menu for "Class loader order".
- You may wait until all WAR module Classloader modes have been set to "PARENT_LAST" before saving your work
- Set the application startup order to 100.
- From the Enterprise Applications menu, select the "SASStoredProcessApplication9.2" link.
- Click the "Startup behavior" link.
- Enter "100" (without the "quotes") in the required "Startup order" field.
- Allow all other fields should remain empty or with their pre-filled values.
- You should perform a Full Resynchronize to ensure the new application definition is propagated between dmgr and the nodeagent.
- NOTE: Wait until all SAS web applications have been successfully deployed, then use the WAS Admin Console to start them by
selecting all applications and clicking Start.
Deployment for application "SASContentServer9.2" on "server1".
Because you have NOT requested auto-configuration of WAS, or have NOT requested auto-deployment of the SAS web applications,
you must use the WAS Admin Console to manually deploy the "SASContentServer9.2" SAS web application.
Perform the following steps to deploy this application and make it ready for SAS operations:
- Navigate to Enterprise Applications->Install and under the Local file system radio button, enter "C:\SAS\Config\Lev1\Web\Staging\sas.wip.scs9.2.ear" to locate the EAR for the SAS "SASContentServer9.2" application.
- Allow all other fields on this page to remain with the pre-filled values and click Next.
- On the "Select installation options" page, allow all fields to remain with pre-filled defaults, with exception of
"Deploy Web services" checkbox. Check this box to ensure the Web services deploy tool wsdeploy runs during application installation.
- Enter "SASContentServer9.2" (without the "quotes") into the Application name field.
- On the "Map modules to servers page", make sure the fully-qualified target server has been selected from the drop-down menu. It should be named
"WebSphere:cell=HOSTNAMECell01,node=HOSTNAMENode01,server=server1".
- Examine the summary page for accuracy, click Finish, and save your work after WAS indicates the application has been successfully deployed.
- Update the Classloader policy and mode for the EAR and the Classloader mode for EACH WAR module contained in the EAR.
- From the Enterprise Applications menu, select the "SASContentServer9.2" link.
- Click the "Classloading and update detection" link for the application EAR and ensure the "Classes loaded with application class loader first"
radio button is selected for this EAR.
NOTE: By default, the WAR Classloading policy at the EAR level is set to "MULTIPLE", so no action is required.
- You may be forced to enter a value in the "Polling intervalfor updated files", if so please enter "3" (without the "quotes"),
since 3 seconds is the WAS default.
- Back on the Enterprise Applications page for this application, click the "Manage Modules" link.
- You now must select EACH WAR module, choosing "Classes loaded with application class loader first" (i.e. "PARENT_LAST") from the drop-down menu for "Class loader order".
- You may wait until all WAR module Classloader modes have been set to "PARENT_LAST" before saving your work
- Set the application startup order to 4.
- From the Enterprise Applications menu, select the "SASContentServer9.2" link.
- Click the "Startup behavior" link.
- Enter "4" (without the "quotes") in the required "Startup order" field.
- Allow all other fields should remain empty or with their pre-filled values.
- You should perform a Full Resynchronize to ensure the new application definition is propagated between dmgr and the nodeagent.
- NOTE: Wait until all SAS web applications have been successfully deployed, then use the WAS Admin Console to start them by
selecting all applications and clicking Start.
Deployment for application "SASThemes9.2" on "server1".
Because you have NOT requested auto-configuration of WAS, or have NOT requested auto-deployment of the SAS web applications,
you must use the WAS Admin Console to manually deploy the "SASThemes9.2" SAS web application.
Perform the following steps to deploy this application and make it ready for SAS operations:
- Navigate to Enterprise Applications->Install and under the Local file system radio button, enter "C:\SAS\Config\Lev1\Web\Staging\sas.themes.ear" to locate the EAR for the SAS "SASThemes9.2" application.
- Allow all other fields on this page to remain with the pre-filled values and click Next.
- On the "Select installation options" page, allow all fields to remain with pre-filled defaults, with exception of
"Deploy Web services" checkbox. Check this box to ensure the Web services deploy tool wsdeploy runs during application installation.
- Enter "SASThemes9.2" (without the "quotes") into the Application name field.
- On the "Map modules to servers page", make sure the fully-qualified target server has been selected from the drop-down menu. It should be named
"WebSphere:cell=HOSTNAMECell01,node=HOSTNAMENode01,server=server1".
- Examine the summary page for accuracy, click Finish, and save your work after WAS indicates the application has been successfully deployed.
- Update the Classloader policy and mode for the EAR and the Classloader mode for EACH WAR module contained in the EAR.
- From the Enterprise Applications menu, select the "SASThemes9.2" link.
- Click the "Classloading and update detection" link for the application EAR and ensure the "Classes loaded with application class loader first"
radio button is selected for this EAR.
NOTE: By default, the WAR Classloading policy at the EAR level is set to "MULTIPLE", so no action is required.
- You may be forced to enter a value in the "Polling intervalfor updated files", if so please enter "3" (without the "quotes"),
since 3 seconds is the WAS default.
- Back on the Enterprise Applications page for this application, click the "Manage Modules" link.
- You now must select EACH WAR module, choosing "Classes loaded with application class loader first" (i.e. "PARENT_LAST") from the drop-down menu for "Class loader order".
- You may wait until all WAR module Classloader modes have been set to "PARENT_LAST" before saving your work
- Set the application startup order to 1.
- From the Enterprise Applications menu, select the "SASThemes9.2" link.
- Click the "Startup behavior" link.
- Enter "1" (without the "quotes") in the required "Startup order" field.
- Allow all other fields should remain empty or with their pre-filled values.
- You should perform a Full Resynchronize to ensure the new application definition is propagated between dmgr and the nodeagent.
- NOTE: Wait until all SAS web applications have been successfully deployed, then use the WAS Admin Console to start them by
selecting all applications and clicking Start.
Deployment for application "SASPortal4.2" on "server1".
Because you have NOT requested auto-configuration of WAS, or have NOT requested auto-deployment of the SAS web applications,
you must use the WAS Admin Console to manually deploy the "SASPortal4.2" SAS web application.
Perform the following steps to deploy this application and make it ready for SAS operations:
- Navigate to Enterprise Applications->Install and under the Local file system radio button, enter "C:\SAS\Config\Lev1\Web\Staging\sas.portal4.2.ear" to locate the EAR for the SAS "SASPortal4.2" application.
- Allow all other fields on this page to remain with the pre-filled values and click Next.
- On the "Select installation options" page, allow all fields to remain with pre-filled defaults, with exception of
"Deploy Web services" checkbox. Check this box to ensure the Web services deploy tool wsdeploy runs during application installation.
- Enter "SASPortal4.2" (without the "quotes") into the Application name field.
- On the "Map modules to servers page", make sure the fully-qualified target server has been selected from the drop-down menu. It should be named
"WebSphere:cell=HOSTNAMECell01,node=HOSTNAMENode01,server=server1".
- Examine the summary page for accuracy, click Finish, and save your work after WAS indicates the application has been successfully deployed.
- Update the Classloader policy and mode for the EAR and the Classloader mode for EACH WAR module contained in the EAR.
- From the Enterprise Applications menu, select the "SASPortal4.2" link.
- Click the "Classloading and update detection" link for the application EAR and ensure the "Classes loaded with application class loader first"
radio button is selected for this EAR.
NOTE: By default, the WAR Classloading policy at the EAR level is set to "MULTIPLE", so no action is required.
- You may be forced to enter a value in the "Polling intervalfor updated files", if so please enter "3" (without the "quotes"),
since 3 seconds is the WAS default.
- Back on the Enterprise Applications page for this application, click the "Manage Modules" link.
- You now must select EACH WAR module, choosing "Classes loaded with application class loader first" (i.e. "PARENT_LAST") from the drop-down menu for "Class loader order".
- You may wait until all WAR module Classloader modes have been set to "PARENT_LAST" before saving your work
- Set the application startup order to 5.
- From the Enterprise Applications menu, select the "SASPortal4.2" link.
- Click the "Startup behavior" link.
- Enter "5" (without the "quotes") in the required "Startup order" field.
- Allow all other fields should remain empty or with their pre-filled values.
- You should perform a Full Resynchronize to ensure the new application definition is propagated between dmgr and the nodeagent.
- NOTE: Wait until all SAS web applications have been successfully deployed, then use the WAS Admin Console to start them by
selecting all applications and clicking Start.
Deployment for application "SASPackageViewer4.2" on "server1".
Because you have NOT requested auto-configuration of WAS, or have NOT requested auto-deployment of the SAS web applications,
you must use the WAS Admin Console to manually deploy the "SASPackageViewer4.2" SAS web application.
Perform the following steps to deploy this application and make it ready for SAS operations:
- Navigate to Enterprise Applications->Install and under the Local file system radio button, enter "C:\SAS\Config\Lev1\Web\Staging\sas.packageviewer4.2.ear" to locate the EAR for the SAS "SASPackageViewer4.2" application.
- Allow all other fields on this page to remain with the pre-filled values and click Next.
- On the "Select installation options" page, allow all fields to remain with pre-filled defaults, with exception of
"Deploy Web services" checkbox. Check this box to ensure the Web services deploy tool wsdeploy runs during application installation.
- Enter "SASPackageViewer4.2" (without the "quotes") into the Application name field.
- On the "Map modules to servers page", make sure the fully-qualified target server has been selected from the drop-down menu. It should be named
"WebSphere:cell=HOSTNAMECell01,node=HOSTNAMENode01,server=server1".
- Examine the summary page for accuracy, click Finish, and save your work after WAS indicates the application has been successfully deployed.
- Update the Classloader policy and mode for the EAR and the Classloader mode for EACH WAR module contained in the EAR.
- From the Enterprise Applications menu, select the "SASPackageViewer4.2" link.
- Click the "Classloading and update detection" link for the application EAR and ensure the "Classes loaded with application class loader first"
radio button is selected for this EAR.
NOTE: By default, the WAR Classloading policy at the EAR level is set to "MULTIPLE", so no action is required.
- You may be forced to enter a value in the "Polling intervalfor updated files", if so please enter "3" (without the "quotes"),
since 3 seconds is the WAS default.
- Back on the Enterprise Applications page for this application, click the "Manage Modules" link.
- You now must select EACH WAR module, choosing "Classes loaded with application class loader first" (i.e. "PARENT_LAST") from the drop-down menu for "Class loader order".
- You may wait until all WAR module Classloader modes have been set to "PARENT_LAST" before saving your work
- Set the application startup order to 100.
- From the Enterprise Applications menu, select the "SASPackageViewer4.2" link.
- Click the "Startup behavior" link.
- Enter "100" (without the "quotes") in the required "Startup order" field.
- Allow all other fields should remain empty or with their pre-filled values.
- You should perform a Full Resynchronize to ensure the new application definition is propagated between dmgr and the nodeagent.
- NOTE: Wait until all SAS web applications have been successfully deployed, then use the WAS Admin Console to start them by
selecting all applications and clicking Start.
Deployment for application "SASWebReportStudio4.2" on "server1".
Because you have NOT requested auto-configuration of WAS, or have NOT requested auto-deployment of the SAS web applications,
you must use the WAS Admin Console to manually deploy the "SASWebReportStudio4.2" SAS web application.
Perform the following steps to deploy this application and make it ready for SAS operations:
- Navigate to Enterprise Applications->Install and under the Local file system radio button, enter "C:\SAS\Config\Lev1\Web\Staging/sas.webreportstudio4.2.ear" to locate the EAR for the SAS "SASWebReportStudio4.2" application.
- Allow all other fields on this page to remain with the pre-filled values and click Next.
- On the "Select installation options" page, allow all fields to remain with pre-filled defaults, with exception of
"Deploy Web services" checkbox. Check this box to ensure the Web services deploy tool wsdeploy runs during application installation.
- Enter "SASWebReportStudio4.2" (without the "quotes") into the Application name field.
- On the "Map modules to servers page", make sure the fully-qualified target server has been selected from the drop-down menu. It should be named
"WebSphere:cell=HOSTNAMECell01,node=HOSTNAMENode01,server=server1".
- Examine the summary page for accuracy, click Finish, and save your work after WAS indicates the application has been successfully deployed.
- Update the Classloader policy and mode for the EAR and the Classloader mode for EACH WAR module contained in the EAR.
- From the Enterprise Applications menu, select the "SASWebReportStudio4.2" link.
- Click the "Classloading and update detection" link for the application EAR and ensure the "Classes loaded with application class loader first"
radio button is selected for this EAR.
NOTE: By default, the WAR Classloading policy at the EAR level is set to "MULTIPLE", so no action is required.
- You may be forced to enter a value in the "Polling intervalfor updated files", if so please enter "3" (without the "quotes"),
since 3 seconds is the WAS default.
- Back on the Enterprise Applications page for this application, click the "Manage Modules" link.
- You now must select EACH WAR module, choosing "Classes loaded with application class loader first" (i.e. "PARENT_LAST") from the drop-down menu for "Class loader order".
- You may wait until all WAR module Classloader modes have been set to "PARENT_LAST" before saving your work
- Set the application startup order to 100.
- From the Enterprise Applications menu, select the "SASWebReportStudio4.2" link.
- Click the "Startup behavior" link.
- Enter "100" (without the "quotes") in the required "Startup order" field.
- Allow all other fields should remain empty or with their pre-filled values.
- You should perform a Full Resynchronize to ensure the new application definition is propagated between dmgr and the nodeagent.
- NOTE: Wait until all SAS web applications have been successfully deployed, then use the WAS Admin Console to start them by
selecting all applications and clicking Start.
Deployment for application "SASSharedServices9.2" on "server1".
Because you have NOT requested auto-configuration of WAS, or have NOT requested auto-deployment of the SAS web applications,
you must use the WAS Admin Console to manually deploy the "SASSharedServices9.2" SAS web application.
Perform the following steps to deploy this application and make it ready for SAS operations:
- Navigate to Enterprise Applications->Install and under the Local file system radio button, enter "C:\SAS\Config\Lev1\Web\Staging\sas.shared9.2.ear" to locate the EAR for the SAS "SASSharedServices9.2" application.
- Allow all other fields on this page to remain with the pre-filled values and click Next.
- On the "Select installation options" page, allow all fields to remain with pre-filled defaults, with exception of
"Deploy Web services" checkbox. Check this box to ensure the Web services deploy tool wsdeploy runs during application installation.
- Enter "SASSharedServices9.2" (without the "quotes") into the Application name field.
- On the "Map modules to servers page", make sure the fully-qualified target server has been selected from the drop-down menu. It should be named
"WebSphere:cell=HOSTNAMECell01,node=HOSTNAMENode01,server=server1".
- Examine the summary page for accuracy, click Finish, and save your work after WAS indicates the application has been successfully deployed.
- Update the Classloader policy and mode for the EAR and the Classloader mode for EACH WAR module contained in the EAR.
- From the Enterprise Applications menu, select the "SASSharedServices9.2" link.
- Click the "Classloading and update detection" link for the application EAR and ensure the "Classes loaded with application class loader first"
radio button is selected for this EAR.
NOTE: By default, the WAR Classloading policy at the EAR level is set to "MULTIPLE", so no action is required.
- You may be forced to enter a value in the "Polling intervalfor updated files", if so please enter "3" (without the "quotes"),
since 3 seconds is the WAS default.
- Back on the Enterprise Applications page for this application, click the "Manage Modules" link.
- You now must select EACH WAR module, choosing "Classes loaded with application class loader first" (i.e. "PARENT_LAST") from the drop-down menu for "Class loader order".
- You may wait until all WAR module Classloader modes have been set to "PARENT_LAST" before saving your work
- Set the application startup order to 100.
- From the Enterprise Applications menu, select the "SASSharedServices9.2" link.
- Click the "Startup behavior" link.
- Enter "100" (without the "quotes") in the required "Startup order" field.
- Allow all other fields should remain empty or with their pre-filled values.
- You should perform a Full Resynchronize to ensure the new application definition is propagated between dmgr and the nodeagent.
- NOTE: Wait until all SAS web applications have been successfully deployed, then use the WAS Admin Console to start them by
selecting all applications and clicking Start.
Deployment for application "HOSTNAMEDashboard4.2" on "server1".
Because you have NOT requested auto-configuration of WAS, or have NOT requested auto-deployment of the SAS web applications,
you must use the WAS Admin Console to manually deploy the "HOSTNAMEDashboard4.2" SAS web application.
Perform the following steps to deploy this application and make it ready for SAS operations:
- Navigate to Enterprise Applications->Install and under the Local file system radio button, enter "C:\SAS\Config\Lev1\Web\Staging/sas.bidashboard4.2.ear" to locate the EAR for the SAS "HOSTNAMEDashboard4.2" application.
- Allow all other fields on this page to remain with the pre-filled values and click Next.
- On the "Select installation options" page, allow all fields to remain with pre-filled defaults, with exception of
"Deploy Web services" checkbox. Check this box to ensure the Web services deploy tool wsdeploy runs during application installation.
- Enter "HOSTNAMEDashboard4.2" (without the "quotes") into the Application name field.
- On the "Map modules to servers page", make sure the fully-qualified target server has been selected from the drop-down menu. It should be named
"WebSphere:cell=HOSTNAMECell01,node=HOSTNAMENode01,server=server1".
- Examine the summary page for accuracy, click Finish, and save your work after WAS indicates the application has been successfully deployed.
- Update the Classloader policy and mode for the EAR and the Classloader mode for EACH WAR module contained in the EAR.
- From the Enterprise Applications menu, select the "HOSTNAMEDashboard4.2" link.
- Click the "Classloading and update detection" link for the application EAR and ensure the "Classes loaded with application class loader first"
radio button is selected for this EAR.
NOTE: By default, the WAR Classloading policy at the EAR level is set to "MULTIPLE", so no action is required.
- You may be forced to enter a value in the "Polling intervalfor updated files", if so please enter "3" (without the "quotes"),
since 3 seconds is the WAS default.
- Back on the Enterprise Applications page for this application, click the "Manage Modules" link.
- You now must select EACH WAR module, choosing "Classes loaded with application class loader first" (i.e. "PARENT_LAST") from the drop-down menu for "Class loader order".
- You may wait until all WAR module Classloader modes have been set to "PARENT_LAST" before saving your work
- Set the application startup order to 100.
- From the Enterprise Applications menu, select the "HOSTNAMEDashboard4.2" link.
- Click the "Startup behavior" link.
- Enter "100" (without the "quotes") in the required "Startup order" field.
- Allow all other fields should remain empty or with their pre-filled values.
- You should perform a Full Resynchronize to ensure the new application definition is propagated between dmgr and the nodeagent.
- NOTE: Wait until all SAS web applications have been successfully deployed, then use the WAS Admin Console to start them by
selecting all applications and clicking Start.
Deployment for application "SASWebDoc9.2" on "server1".
Because you have NOT requested auto-configuration of WAS, or have NOT requested auto-deployment of the SAS web applications,
you must use the WAS Admin Console to manually deploy the "SASWebDoc9.2" SAS web application.
Perform the following steps to deploy this application and make it ready for SAS operations:
- Navigate to Enterprise Applications->Install and under the Local file system radio button, enter "C:\SAS\Config\Lev1\Web\Staging\sas.webdocmd9.2.ear" to locate the EAR for the SAS "SASWebDoc9.2" application.
- Allow all other fields on this page to remain with the pre-filled values and click Next.
- On the "Select installation options" page, allow all fields to remain with pre-filled defaults, with exception of
"Deploy Web services" checkbox. Check this box to ensure the Web services deploy tool wsdeploy runs during application installation.
- Enter "SASWebDoc9.2" (without the "quotes") into the Application name field.
- On the "Map modules to servers page", make sure the fully-qualified target server has been selected from the drop-down menu. It should be named
"WebSphere:cell=HOSTNAMECell01,node=HOSTNAMENode01,server=server1".
- Examine the summary page for accuracy, click Finish, and save your work after WAS indicates the application has been successfully deployed.
- Update the Classloader policy and mode for the EAR and the Classloader mode for EACH WAR module contained in the EAR.
- From the Enterprise Applications menu, select the "SASWebDoc9.2" link.
- Click the "Classloading and update detection" link for the application EAR and ensure the "Classes loaded with application class loader first"
radio button is selected for this EAR.
NOTE: By default, the WAR Classloading policy at the EAR level is set to "MULTIPLE", so no action is required.
- You may be forced to enter a value in the "Polling intervalfor updated files", if so please enter "3" (without the "quotes"),
since 3 seconds is the WAS default.
- Back on the Enterprise Applications page for this application, click the "Manage Modules" link.
- You now must select EACH WAR module, choosing "Classes loaded with application class loader first" (i.e. "PARENT_LAST") from the drop-down menu for "Class loader order".
- You may wait until all WAR module Classloader modes have been set to "PARENT_LAST" before saving your work
- Set the application startup order to 100.
- From the Enterprise Applications menu, select the "SASWebDoc9.2" link.
- Click the "Startup behavior" link.
- Enter "100" (without the "quotes") in the required "Startup order" field.
- Allow all other fields should remain empty or with their pre-filled values.
- You should perform a Full Resynchronize to ensure the new application definition is propagated between dmgr and the nodeagent.
- NOTE: Wait until all SAS web applications have been successfully deployed, then use the WAS Admin Console to start them by
selecting all applications and clicking Start.
Deployment for application "SASWebOLAPViewer4.2" on "server1".
Because you have NOT requested auto-configuration of WAS, or have NOT requested auto-deployment of the SAS web applications,
you must use the WAS Admin Console to manually deploy the "SASWebOLAPViewer4.2" SAS web application.
Perform the following steps to deploy this application and make it ready for SAS operations:
- Navigate to Enterprise Applications->Install and under the Local file system radio button, enter "C:\SAS\Config\Lev1\Web\Staging\sas.webolapviewer4.2.ear" to locate the EAR for the SAS "SASWebOLAPViewer4.2" application.
- Allow all other fields on this page to remain with the pre-filled values and click Next.
- On the "Select installation options" page, allow all fields to remain with pre-filled defaults, with exception of
"Deploy Web services" checkbox. Check this box to ensure the Web services deploy tool wsdeploy runs during application installation.
- Enter "SASWebOLAPViewer4.2" (without the "quotes") into the Application name field.
- On the "Map modules to servers page", make sure the fully-qualified target server has been selected from the drop-down menu. It should be named
"WebSphere:cell=HOSTNAMECell01,node=HOSTNAMENode01,server=server1".
- Examine the summary page for accuracy, click Finish, and save your work after WAS indicates the application has been successfully deployed.
- Update the Classloader policy and mode for the EAR and the Classloader mode for EACH WAR module contained in the EAR.
- From the Enterprise Applications menu, select the "SASWebOLAPViewer4.2" link.
- Click the "Classloading and update detection" link for the application EAR and ensure the "Classes loaded with application class loader first"
radio button is selected for this EAR.
NOTE: By default, the WAR Classloading policy at the EAR level is set to "MULTIPLE", so no action is required.
- You may be forced to enter a value in the "Polling intervalfor updated files", if so please enter "3" (without the "quotes"),
since 3 seconds is the WAS default.
- Back on the Enterprise Applications page for this application, click the "Manage Modules" link.
- You now must select EACH WAR module, choosing "Classes loaded with application class loader first" (i.e. "PARENT_LAST") from the drop-down menu for "Class loader order".
- You may wait until all WAR module Classloader modes have been set to "PARENT_LAST" before saving your work
- Set the application startup order to 100.
- From the Enterprise Applications menu, select the "SASWebOLAPViewer4.2" link.
- Click the "Startup behavior" link.
- Enter "100" (without the "quotes") in the required "Startup order" field.
- Allow all other fields should remain empty or with their pre-filled values.
- You should perform a Full Resynchronize to ensure the new application definition is propagated between dmgr and the nodeagent.
- NOTE: Wait until all SAS web applications have been successfully deployed, then use the WAS Admin Console to start them by
selecting all applications and clicking Start.
Starting the WebSphere Server(s)
- Starting the Dmgr server: Issue "C:\Program Files\IBM\WebSphere\AppServer\bin\startManager.bat" -profileName "Dmgr01" or, if on Windows, by starting the the Windows service.
- Starting the Node Agent server: Issue "C:\Program Files\IBM\WebSphere\AppServer\bin\startNode.bat" -profileName "AppSrv01" or, if on Windows, by starting the Windows service.
- Starting the Application Server: Issue "C:\Program Files\IBM\WebSphere\AppServer\bin\startServer.bat" "server1" -profileName "AppSrv01"
SAS Web Applications
SAS Themes
| Validation steps |
SAS Themes are used by SAS theme-enabled web applications. If you go to the logon screen for the Portal or Web Report Studio and see images then SAS Themes are working properly.
|
SAS Web Infrastructure Platform
| Log directory |
C:\SAS\Config\Lev1\Web\Logs
|
| Validation steps |
The SAS Web Infrastructure Platform is used by other SAS web applications, so if the validation steps for SAS web applications are successful, then the SAS Web Infrastructure Platform is working properly.
|
SAS Content Server
| Log file |
C:\SAS\Config\Lev1\Web\Logs\SASContentServer.log
|
| Validation steps |
- In the SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node.
- Highlight the SAS Content Server.
- Right mouse click this server and select Validate.
- Log in using valid credentials for an unrestricted user defined in the SAS Metadata Server.
- You should see a Validation Successful message.
|
SAS Stored Process Web Application
| URL |
http://HOSTNAME.example.com:9080/SASStoredProcess/do |
| Log file |
C:\SAS\Config\Lev1\Web\Logs\SASStoredProcess9.2.log
|
| Validation steps |
- Access the URL provided above.
- Log in using the HOSTNAME\sasdemo credentials provided during configuration.
- On the Welcome page, click the "Sample: Shoe Sales by Region" link to access the custom input form for this sample stored process.
- Select an ODS style or accept the default value, and click the "Display SAS Output" button.
- The output from the stored process is a static table and a clickable chart. Click a bar segment on the chart to drill down to the data for that country.
|
SAS Web Report Studio
SAS Web OLAP Viewer for Java
SAS Information Delivery Portal
| URL |
http://HOSTNAME.example.com:9080/SASPortal |
| Log file |
C:\SAS\Config\Lev1\Web\Logs\SASPortal4.2.log
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. |
| Validation steps |
- Access the URL provided above.
- Login using the HOSTNAME\sasdemo credentials provided during configuration.
- Since the Portal samples were installed, verify that a Home page was created and contains two portlets, My Collections and Bookmarks.
- Perform a search to verify that you have access to SAS content.
|
Notes:
- The SAS Portlets are located at: C:\SAS\Config\Lev1\Web\Applications\SASPortlets4.2\Deployed
- If your network has a proxy server, you must specify the following parameters on the
Application Server start-up command so that syndication channels and the
URL Display Portlet can access content outside of your network.
- -Dhttp.proxyHost=host
- -Dhttp.proxyPort=port
SAS Shared Services
Notes:
SAS BI Dashboard 4.2
| URL |
http://HOSTNAME.example.com:9080/HOSTNAMEDashboard |
| Log directory |
C:\SAS\Config\Lev1\Web\Logs\HOSTNAMEDashboard4.2.log
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. |
| Validation steps |
- Grant the user SAS Demo User access to SAS BI Dashboard 4.2. In SAS Management Console, on the Plug-ins tab, click on the User Manager node.
- Right click on "BI Dashboard Administrators" and select "Properties."
- Click on the "members" tab
- Double click on SAS Demo User to add it to the group.
- Click OK.
- Access the URL provided above.
- Login using the HOSTNAME\sasdemo credentials provided during configuration.
- Create a new indicator using the New Indicator option.
- Add this indicator to a new or existing dashboard and verify that you have access to this dashboard by adding
the BI Dashboard Portlet to a Portal page.
|
Notes:
SAS Help Viewer Metadata Configuration
Web Application Custom Content
If you wish to add custom content into SAS web applications,
you may do so by placing your custom content into the appropriate custom content directory structure
for the given application, and then running the SAS Deployment Manager to rebuild web applications.
The custom content root directory for a given web application is
C:\SAS\Config\Lev1\Web\Common\Server Name\Application Name\CustomContent
For example,
C:\SAS\Config\Lev1\Web\Common\SASServer1\SASWebReportStudio4.2\CustomContent
Within that directory, there are subdirectories (for example, ears or wars) corresponding
to specific archive types (ear and war files, respectively).
Under the archive type directories, there are subdirectories for each specific archive—these are the root directories
for each archive within the application. Custom content should be placed in the archive's directory tree corresponding
to where the content should appear within the archive.
For example, to add the ear_addon.xml file into the
addons directory in the sas.webreportstudio ear file, create the
...\CustomContent\ears\sas.webreportstudio\addons
directory, and place ear_addon.xml in it.
Our process knows which war files are contained within ear files, so if you want to add war_addon.jar into
the WEB-INF/lib directory in the sas.webreportstudio war file within the
sas.webreportstudio ear file, then create
...\CustomContent\wars\sas.webreportstudio\WEB-INF\lib
directory, and place war_addon.jar in it.
Once all your custom content is ready to be consumed, run the
SAS Deployment Manager and choose to rebuild web applications. Doing so will rebuild the web applications,
inserting the custom content into the archives under the appropriate paths. Note that if custom content has the
same path and name of content normally included in the archive, then the custom content takes precedence.
SAS Metadata Bridges
The SAS Metadata Import or Export function of SAS Management Console and SAS Data Integration Studio will prompt for the location of a SAS license file. Therefore, a valid SAS license file must be accessible from the client machine. The license file may be available in the sid_files directory at the root of your SAS Software Depot or it may be included with your SAS Software Order E-mail. If it is with your SAS Software Order E-mail, then you should follow the instructions included in that e-mail for where and how to store your SAS license file.
Completing Your Deployment
In order to complete your deployment on this machine, certain manual steps have to be performed. The SAS Content Server must be running before you attempt these steps.
Loading Content to the SAS Content Server
Since you selected to not automatically deploy your SAS Web Applications, manual steps are required to ensure the proper content is loaded to the SAS Content Server. The file, C:\SAS\Config\Lev1\Web\Utilities\manualLoadContent.bat, has been created to facilitate this process.
Click here to run this script to automatically load content for the SAS Web Applications that require it.
The steps detailed above resulted in the creation of log files, which can be found in C:\SAS\Config\Lev1\Logs\Configure. Review the contents of the scripts you executed for the name of the log files that were created. Review these logs and make sure there were no errors. Each execution of these scripts results in the logs from previous executions being overwritten. Therefore, prior to rerunning these scripts, you may wish to make appropriate backups of the logs.
These manual steps required the use of the SAS Administrator account. The scripts contain the SAS Administrator's credentials with the password encrypted at the sas002 level. The scripts are not intended for further use once your deployment is complete. Since these scripts contain the SAS Administrator's credentials, it is highly recommended that you delete them once your deployment is complete.
Obtaining Additional Information
Additional SAS Intelligence Platform documentation is available from the SAS 9.2 administration documentation web site.
There may be additional configuration steps required for your SAS Foundation software. Consult the SAS Foundation Configuration instructions available for your operating system for product-specific post-installation steps. The configuration instructions are available from the SAS Install Center web site.
Backing up your SAS Metadata Server
After completing your SAS Intelligence Platform configuration, we strongly recommend that you create a backup of your newly configured SAS Metadata Server. If you have adequate disk space to accommodate a copy of all of your metadata repositories on the metadata server host, use the MetadataServer.bat script provided in the C:\SAS\Config\Lev1\SASMeta\MetadataServer directory. To execute the script, type:
MetadataServer.bat backup
The script copies all critical metadata server files to a SASBackup subdirectory of the MetadataServer directory.
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.
