I have a problem transferring user defined attribute types and groups from one ARIS 7.1 server to another. Sometimes (!) it happens for some attributes that have values by just restoring a DB that was backed up after the method changes, to the target server. And it's really for some attributes.
When using the “convert” function, all filters, fonts etc are successfully transferred with exception of attribute types and groups. When it is between LOCAL and Server it works fine but between two identical (=build, same RDBMS) servers, not. I don’t have a clue what am I doing wrong.
Ivo
Hi Ivo,
What you can try is by replacing the target server's config file with the source server's config file by using siteadmin - log on to the source server, backup the config file to a folder in your harddisk, logon to the target server and use the command replace config using the config file you have backed up. This will create an excact copy of the source server attribute, groups, symbols, filters ect.
Ciska
Hi Sabastian,
There are new attribute types and groups greated in the source server and converting them to another server didn't work. Now I did it again and it seems everything is fine. This is still strange as I did exactly the same thing. Anyway, will do some tests and will share if there are any issues.
Regards,
Ivo
Hi Ivo,
another way to transport method extension would be to create a filter which makes use of the attributes you like to have on a separate server, then export the filter and import it on the target server.
The filter is a container for the attributes, and so the will be imported on the target server as well and.
Regards, Marc
Ivo,
Generally, transferring the filter from one DB to another brings along all of the attributes information.
I don't know if this related to your problem but I recently encountered a problem with user-defined attributes not moving properly between 2 different 7.1 databases that were not the same versions. I took a filter that was orginally created in 7.1.0.295367 to a database in 7.1.0.333379. I updated the filter and imported back into the old database and it invalidated all of the defined user attributes. Fortunately, reinstalling the original filter fixed the problem. I've never had this problem in the past as long as the major version was the same.
Rick
