I am from a Java background and for one of the project that I am working on I am told to evaluate SAS Enterpise guide as a solusion. I am going through the tutorial and documetnation on it and trying to evaluate.
How dies the Deployment look like in SAS. In Java , we build the code using ANT script, then package the code using EAR, WAR files and embed the JSP files. How does the deployment look like in SAS. How do we port the code developed in EG to server.
Any help. Any information regarding the Architecture will also be useful to get complete picture.
You could have several different scenarios for using SAS Enterprise Guide (EG):
1) SAS EG and Foundation SAS on the same machine: this is the case when you have the SAS Learning Edition installed. In this case, there are no remote servers or external servers involved -- you execute all code on the Local computer. This is also the scenario if you have EG and a single-user copy of SAS (not the Learning Edition) on your Windows machine.
2) SAS EG on Windows and SAS on a server machine: this is the case when you may have 10 analysts, each using SAS EG on their personal machines, and the single copy of SAS (and other SAS products) and all the data is on a different server -- such as a Unix server. In this case, the EG users each have a copy of SAS EG installed on their Windows machines, SAS is running on the server and when the analysts submit code, there is a "pipeline" from their machine to the SAS server that takes their code, sends it to the server and receives the results back from the server.
3) SAS EG and Foundation SAS as part of the SAS Enterprise Intelligence Platform (Business Intelligence) software: EG is only one of the client applications used in this scenario. Other client applications include the SAS Add-in for Microsoft Office, SAS Web Report Studio and the SAS Information Delivery Portal (for end users); SAS Management Console, SAS Data Integration Studio, SAS Information Map Studio and SAS Olap Cube Studio (for data modelers and system administrators). In this scenario, there's still a "pipeline" that connects EG to the servers -- but the pipeline almost always goes through the SAS Metadata server for access and control information.
Deployment will be different depending on which of the scenarios corresponds to your particular configuration.
Your best resource for help would be to identify which of the above scenarios corresponds to your configuration and to contact Tech Support for more help.
Those were not "solutions" that I posted, they were possible Enterprise Guide usage/install scenarios. Deployment of SAS Enterprise Guide and of SAS components would need to be different depending on which of the 3 usage scenarios you were going to follow.
The issue of the kinds of applications/reporting structures/prompting interfaces that you could build is an entirely separate discussion from the discussion of how to deploy SAS EG. SAS Enterprise Guide is NOT an IDE like Eclipse or Visual Studio. SAS Enterprise Guide is a front-end to SAS -- it works with SAS in a variety of ways (the 3 scenarios described in the previous posting).
You could build a dynamic reporting system without using SAS EG at all. Many companies use the SAS/IntrNet product, which allows the development of web-based interfaces to SAS on a server. SAS/IntrNet has different capabilities than SAS/EG. Other companies use SAS/AF and the SAS Component Language to build a dynamic reporting or data maintenance system. And these days, other companies use SAS Integration Technologies within the context of the BI Platform to develop custom systems for enterprise wide business intelligence solutions. You can use JSP, ASP, .NET, Visual Basic, Visual C++ and other languages/methods to interact with SAS when you are writing your own custom application. In that scenario, you may or may not use SAS EG at all. Or you might design and develop your own custom tasks for SAS EG. Or you might use Eclipse and SAS AppDev Studio to develop JSPs that can be deployed within the SAS Enterprise Intelligence Platform.