These are the properties which we have updated for LASR Authorization Service in Internal connection only.
where sasva001.ippbonline.net = Internal URL
report.ippbonline.net = External URL
I have also attached other properties excel here.
do we need to update External URLs only in our internal connection ?
@alexal No luck.
Can you help us out through webex if possible ?
Still the same error? I would like to review the output from a SAS program shown below:
data tcpip;
keep name port host protocol service;
length port host protocol objid service uri name $255;
nobj=0;
n=1;
do while (nobj >= 0);
nobj=metadata_getnobj("omsobj:TCPIPConnection?@Name='Connection URI' or @Name='External URI'",n,uri);
if (nobj >= 0) then do;
rc=metadata_getattr(uri,"Name",name);
if trim(name)='Connection URI' then name="Internal URI";
rc=metadata_getattr(uri,"CommunicationProtocol",protocol);
rc=metadata_getattr(uri,"HostName",host);
rc=metadata_getattr(uri,"Port",port);
rc=metadata_getattr(uri,"Service",service);
put name protocol"://"host":"port service;
output;
end ;
n = n + 1;
end;
run;
proc sort data=tcpip out=sorted;
by service;
run;
proc print data=sorted;
var name port host protocol service;
title 'Internal and External Connections (except SASThemes)';
title2 'Listed by Service';
run;
@alexal Yes it still the same.
I am attaching the program output.
External URI for /SASLASRAuthorization still incorrect. Please make sure that you have select "Use internal connection information" on the "External Connection" tab of LASR Authorization Service properties.
Please submit a problem via this form and our middle tier support will assist you. Do not forget to attach all of these files.
@alexal Since I've already raise a ticket for the same which i had shared with you.
Do i need to raise it again ?
@alexal Hi ! Issue resolved. Thanks a lot for you support & efforts.
Basically two additional JVM parameters we had to add in server.sh file in all web servers.
Regards,
Ashish
It looks like you did change the internal connection for LASR Authorization Service. Am I right?
Yes! We did change internal connection accordingly proxy host and port.
You aren't supposed to change internal connection for the LASR Authorization Service.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.