Skip to main content

Set Up the SAS® Application Server


  1. Use the IntrNet Configuration Utility (also referred to as Inet Config) to define or set up the Application Server. Click on the Windows Start button and select All Programs or Programs ==> The SAS System (for Version 8) or SAS (for Version 9) ==> IntrNet ==> Create a New IntrNet Service
  2. When you see the SAS Service Configuration Utility (shown below) choose Create a Pool Service and click Next. You may also choose to Create a Socket Service, however creating a Pool Service is suggested.
  3. Follow the prompts:
    1. Specify appdisp for the name of the service.
    2. When prompted to enter Enter Admin Password, you can leave it blank for this install on your local PC.
The Configuration Utility will generate default Application Broker directives you need to add to your Application Broker configuration file.
  1. The Version 9 utility will create a readme.txt file containing the needed information. The folder that the readme file is saved in can be found by clicking on the Windows Start button and selecting All Programs or Programs ==> SAS ==> IntrNet ==> appdisp Service ==> Service Directory
  2. The Version 8 utility displays the information. You should save those values (e.g., cut-and-paste and save them as a text file).
For Pool Services, make sure you save the value for the SasCommand Application Broker Directive.



For More Info, Click Here

Comments

Popular posts from this blog

Call User-defined Function on Linked Server :SQL Server

If you try to invoke a user-defined function (UDF) through a linked server in SQL Server by using a "four-part naming" convention (server.database.dbo.Function), you may receive error message.  The reason is User-defined function calls inside a four-part linked server query are not supported in SQL Server. Thats why error message indicates that the syntax of a Transact-SQL statement is incorrect.  To work around this problem, use the Openquery function instead of the four-part naming convention. For example, instead of the following query Select * from Linked_Server.database.dbo.Function(10) run a query with the Openquery function: Select * from Openquery(Linked_Server,'select database.dbo.Function(10)') If the user-defined function takes variable or scalar parameters, you can use the sp_executesql stored procedure to avoid this behavior.  For example: exec Linked_Server.database.dbo.sp_executesql N'SELECT database.dbo.Function(@input)',N'@input

Microsoft SQL Server 2005 Service Pack 3 for Windows 7 (64 bit)

You can download from here Microsoft SQL Server 2005 Service Pack 3 Overview Service Pack 3 for Microsoft SQL Server 2005 is now available. SQL Server 2005 service packs are cumulative, and this service pack upgrades all service levels of SQL Server 2005 to SP3. You can use these packages to upgrade any of the following SQL Server 2005 editions: Enterprise Enterprise Evaluation Developer Standard Workgroup Download Size: 326.0 MB http://www.microsoft.com/downloads/details.aspx?FamilyID=ae7387c3-348c-4faa-8ae5-949fdfbe59c4&displaylang=en Microsoft SQL Server Management Studio Express Service Pack 3 Overview Microsoft SQL Server Management Studio Express (SSMSE) is a free, easy-to-use graphical management tool for managing SQL Server 2005 Express Edition and SQL Server 2005 Express Edition with Advanced Services. SSMSE can also manage instances of the SQL Server Database Engine created by any edition of SQL Server 2005. Note: SSMSE cannot manage SQL Server Analysis

Configuring CORS in IIS - Response to preflight request doesn't pass access control check: It does not have HTTP ok status

The Access-Control-Allow-Origin Header Explained – With a CORS Example Often times when calling an API, you may see an error in your console that looks like this: Access to fetch at 'http://somesite.com' from origin 'http://yoursite.com' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header has a value that is not equal to the supplied origin Add following in <system.webServer> <httpProtocol> <customHeaders> <add name="Access-Control-Allow-Methods" value="*" /> <add name="Access-Control-Allow-Origin" value="*" /> <add name="Access-Control-Allow-Headers" value="*" /> </customHeaders> </system.webServer> After adding the above code in web.config, received the following error in response. .... Has been blocked by CORS policy: Response to preflight request doesn’t pass access control check: