I'm new SAS VA and i'm installing sas va distribute.
I have installed following sas documents, when i installed below step, i was stuffed because i didn't understand 2 files: response.txt, config.txt.
$./setup.sh -deploy -record -responsefile /sas94/response.txt
$./setup.sh -deploy -record -responsefile /sas94/config.txt
These 2 files that I create available or they are in sas va 9.4 source? and these 2 file's content include what?
Please help me!
good question. Those are files that you create. Your option with -deploy and -record means that you will go through the deployment wizard (SDW), SDW will record your choices in this file, that you can use later on. And after you finish it will start the actual deployment.
You have the option also to run setup.sh -record -responsefile /sas94/response.txt first, it won't deploy anything. And then, when it is convenient for you, you may call to setup.sh -partialprompt -responsefile /sas94/response.txt or setup.sh -quiet -responsefile /sas94/response.txt
Please give a loog to the SDW guide http://support.sas.com/documentation/installcenter/en/ikdeploywizug/66034/PDF/default/user.pdf
Thanks for your answer!
Can i have some quesitons!
+ when i run this command () to install sas va by ui, it's OK, when click 'start', everything is finish without errors(green icon).
+ But i run this command () to config sas va by ui, it's not OK,when click 'start', everything is finish with errors(red icon) and in processing of configuration, i didn't see configing step of hadoop...
Please help me to fix them!
Installation is just the "copy" of the binaries, therefore quite standard. There are rarely problems with this step.
Configuration is the set up of every service and customise the thousands of scripts and configuration files for your selected deployment.
For your information:
SAS® Visual Analytics documentation: https://support.sas.com/documentation/onlinedoc/va/
For VA disributed (multiple nodes)
You have two options for where to locate your SAS analytics cluster:
I'm installing my sas va distribute 9.4 with 3 nodes (181: namenode/sasnode, 182: datanode, 183: datanode).
I have installed following sas va's document and everything is ok, but only configing step is finished with errors.
You can read my document which i follow.
Please tell me why!
Hi there @htin,
perhaps you can share with us the list of steps that have been successful, where the config stopped/gave errors, and the logs from the steps that gave errors.
Let's give it a go, and if it takes too much time from us or we cannot help you, at that point I will suggest you to contact SAS Technical Support.
Btw: o you have firewalls (firewalld and iptables) on or off?
In step as attached image, Must I choose which 'plan.xml'? I didn't know location's plan.xml in sasva source...
I have listed plan.xml in sasva source as below:
[root@sasnode1 ~]# find / -name plan.xml
Please help me!
Hi again @htin,
ah, now I get it. You need a Deployment Plan customised for your deployment. This must be provided to you by SAS Technical Support, a SAS Consultant.
Beware that whomever will help you with the deployment plan, they will need to know the details of the blueprint/design of your deployment, so you will need to get ready to provide as much information as possible.
probably you are getting a default directory for this path of signature files: /tmp? You may specify another location, but you will need to ensure proper permissions to write and read files and a umask, recommended 027
Server and Table Signature FilesWhen a SAS LASR Analytic Server connection is started in SAS Visual Analytics Administrator, a server signature file is created and stored in the
/tmpdirectory (Juan's note: by default.). The server signature file is accessed when the server connection is stopped in SAS Visual Analytics Administrator. When tables are loaded from SAS Visual Analytics Administrator or SAS Visual Data Builder to the SAS LASR Analytic Server, table signature files are created and stored in the
SAS LASR Analytic Server uses two types of signature files, server signature files and table signature files. These files are used as a security mechanism for server management and for access to data in a server. When a server instance is started, a directory is specified on the PATH= option to the LASR procedure. The specified directory must exist on the machine that is specified as GRIDHOST= environment variable. In order to start a server, the user must have Write access to the directory in order to be able to create the server signature file. In order stop a server, the user must have Read access to the server signature file so that it can be removed from the directory. In order to load and unload tables on a server, the user must have Read access to the server signature file in order to interact with the server. Write permission to the directory 6 Chapter 1 • Introduction to the SAS LASR Analytic Server is needed to create the table signature file when loading a table and to delete the table signature file when unloading the table.
In short, yeah 🙂
In a bit longer, please read (have this guide as your sacred one!):
Signature files location, specify the absolute path where the SAS LASR Analytic Server writes signature files. If you are using SAS LASR Analytic Server in distributed mode, specify a path located on the SAS High-Performance Analytics environment root node. If you are using a non-distributed SAS LASR Analytic Server, specify a path located on the local machine. It is important to carefully manage access to the signature files directory. User IDs under which certain activities are performed (for example, starting a server or loading data) must have Write access to the signature files directory. Access to a signature files directory can provide access to loaded data, so that the signature files directory should be protected against unauthorized access. For more information, see “Signature Files” in the SAS Visual Analytics: Administration Guide.
Look, i will answer you this one, but I decide to not guide you through that many steps of a deployment, specially since I miss several of your steps regarding integration.
It might be harsh, but please let me give you a free piece of advise, from my personal experience:
I firmly think that who installs a system in a customer, should be prepared enough and upfront, and have good understanding of the architecture and integration required, to ensure quality and delivery times. Of course that is your problem for your deployment, not mine, so do not get me wrong, just want to help here, not only technically (actually, the technical help, although important, it is just a minor thing compared to manage expectations).
And I understand this obligation might have come from your managers at your company (there good reasons will have: time, rush, understand you can do it, budget, whatever), but it is also important you understand that it is also your right and role to provide your professional advise: to get additional resources/consultants/ get training and resources (time, eg) upfront, and even to refuse the assignment, if needed. It is not only your face, or the face of your client, it is also the face of your company what is in the game.
I wanted to make this point clear... it is important. Not only to you, but also to other people whom might be reading us, or will be.
Now... if you have followed that guide of yours you posted at the beginning, probably you should input the same values on those boxes, i suppose. But I cannot give you good advise here since I am unaware of deviations you already took, sorry.
Anyway, the best you can do, for understanding what you do, is to follow the deployment/installation guide (explains a lot), and if you follow the steps of your own guide/pdf, be coherent with it and follow similar steps. I am not sure if that is the best quality, but at least you should get the same level of quality desired by your company when created that PDF.
Hope it helps, not only technically, but also for the future. As said, I fully understand your current situation. I have seen those situations many times before. But the sooner you get in control, the sooner you will see a great improvement in your professional career and with your professional relationships.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.
Find more tutorials on the SAS Users YouTube channel.