(RDMLX) Document Server

[MegumiSawada]

Hi,

On the Document Server Setting screen of LongRange client app, it is written that "If no user is specified, your IBM i credential will be used when connecting to the document server". I wonder which user is actually pointed to. I mean, on LongRange for LANSA, there's no user provided explicitly.So I wonder which user will be used for the Document Server as a default.

I have another question.
Is there any way to make users use only LongRange Document server and to disable to use LongReach on their devices even if LongReach app is installed on these?
On LongReach(which is used for LongRange Document Server), you can allow/deny the useragent in httpd.xml. If you specify there like <deny useragent="longreach"/>,then both LongReach and Document Server get both disabled. So you cannot use this way,but do you know other way like this to achieve our requirement ?

Thank you in advance.

Best Regards,
Megumi

[Paul]

Hi Megumi,

In LongRange LANSA, if no user is explicitly specified, LRNGUSER is the default user. I would recommend explicity specifying a user in the Document Server details.

I spoke to LongReach development about your second question. There is an imbedded method, that is being planned for the future, that could be used to restrict requests to LongReach from specified applications, e.g. allow LongRange and deny LongReach. However, it is not fully implemented yet.

An alternative that can be used now is to restrict access to LongReach from the device-longreach.txt file in the system folder of the LongReach server installation. This file lists device ID / user profiles that access LongReach and allows new device/Users until the limit stated at the start of the file. LongRange doesn’t send device IDs. So to allow users BILL and FRED, for example, to use LongRange Document views but deny any access by LongReach you would edit the file to the following and restart LongReach;

Code: Select all

#LONGREACH,2
,BILL
,FRED

There would be no guarantee that this system won’t change in the future and this may have security risks involved so care would need to be exercised.

Regards, Paul

[MegumiSawada]

Hi Paul,

Thank you for your advice!
I'll try it!

Best Regards,
Megumi