| **
Send your 5.1.2 license file to Remedy and they will send
you back a file in 6.3 format. You can then apply the Fixed
license keys to your Reporting Server. Go to SupportWeb ->
Issues and Solutions -> Upgrade License File. The file they send back
contains both your original 5.1.2 licenses and the 6.3 versions. The file
works on the 5.1.2 server and a 6.3 server.
This way you will already have the license file ready when
you are ready to upgrade your server to 6.3
I believe the definition of a fixed license is a
license granted to an individual person that is valid for any server in the
site.
Fred
**
Im being told by the server admin who maintains the
licenses that due to the version differential between the servers (v 5.1.2 in
production vs. v6.3 in Reporting) that the site license is not an
option.
----- Original Message -----
Newsgroups:
public.remedy.arsystem.general
Sent: Friday, May 12, 2006 9:06 AM
Subject: Re: DSO bypassing mapping
**
Since Fixed Licenses are licensed by site go ahead and
apply them to the reporting server. Then do Stephen's suggestion of a
filter to set them to Read after the push. That way the DSO transaction
will not fail and the users will have Read licenses.
Fred
**
Unfortunately no, because if the record is passed
with a Fixed license and there are none available on the server then the DSO
transaction will fail :(
----- Original Message -----
Newsgroups:
public.remedy.arsystem.general
Sent: Friday, May 12, 2006 8:58
AM
Subject: Re: DSO bypassing
mapping
**
Jim,
Could you create a Filter on the reporting server
User form that sets the License Type to Read as records are
inserted/updated/merged?
Stephen
**
Hopefully someone out there has seen this
before and has some insight.
We have DSO running between our production
system (5.1.2) and a reporting server (6.3) Overall it works
correctly. The requirement is to transfer EVERYTHING. So all
configuration data and yes even User form data gets DSO'd to the reporting
server.
Therein lies the problem. There are not
as many fixed licenses on the reporting server as the production, nor do we
want to issue fixed licenses as it is a read only environment.
Obviously a direct field mapping would try to copy the Fixed license and
error out the transfer as the license is not available.
We had set up a custom mapping which mapped all
the fields straight across except the License Type field. This is
mapped to a static value of Read. I had this working briefly (Im
pretty sure, it was a quick test a while ago, then the project got
stalled) Now when I am testing it to prepare for a rollout it is
taking the user data across but it seems to bypass the custom
map. If I filter log it I can see where it performs the DSO
process and the mapping is specified in the command line, but the license
field is still being carried across with its production system value, not
Read.
Any ideas, suggestions, etc are greatly
appreciated.
Jim __20060125_______________________This
posting was submitted with HTML in it___
__20060125_______________________This posting was submitted with HTML in
it___ __20060125_______________________This posting was submitted
with HTML in it___ __20060125_______________________This posting was submitted
with HTML in it___ __20060125_______________________This posting
was submitted with HTML in it___
__20060125_______________________This posting was submitted with HTML in it___
|
- Re: DSO bypassing mapping Grooms, Frederick W
-
