Need to copy category schema from one repository to other

Hi,

Whenever you get a generic message like that you need to look at the
logs. This means there was some lower error that occurred.

Rich

Hi,

We checked the logs and found the issue was because RTC server was down. Now we overcome this error and able to test successfully.
Can you please have a look at our requirements and the steps we are following to do it. We can't take any risks while doing it on Production, so want you to review it once before we go ahead.
Requirement :
There is already a library containing only that category schema in both the servers from where we need to export and import. We need to create a new version of that library in Production server and export it as a zip file. In Test server we need to import that schema. In Test server also there is already a library created with alone that category schema.
Note : the category schema which we are importing in Test server already contains the same name schema. We want to overwrite it with the schema which we are importing from Production server.
Steps to complete this requirement :
1) In Production server, create a new version of the already existing library and enable the new version.
2) Export the new version from production.
3) In Test Server, import this zip file.
4) Conflicts page will appear and its says that it is having the conflict with an existing library and will create a new version of that library. Then we clicked on "Next".
5) The new version of that library created and on that server.
6) We enable that new version also.

Results :
1) The already existing schema in Test server will be overwritten by the schema which is imported from Production server.
2) One issue which we found in testing is that the communities scoping is not done automatically by importing the schema.

Please let us know if our above steps are correct and if there are any risks involved in it.

Also please let us know if we should first take the backup of Test server category schema in case there are any issues in this task.

Thanks in advance for your help.

Hi,

I can't really answer your question with certainty. What you said is
true and is what is supposed to happen. But there can be problems when
there are conflicts.

Especially you must have at least testfix2 of 7202 on both the exporting
system and the importing system (you should go all of the way to testfix
6 on both exporting and importing because there are many other fixes),
or you need to be at 7.5. There are problems with category schema ids
being changed on import and on renaming. Importing on conflicts could
cause these problems to be even worse.

As for community scoping of schemas, that only occurs if the community
itself is exported. If the community is not exported then the community
scoping is not exported.

As for backup, if the schema in the test server (the one being imported
into) is already in a library then you have your backup. The library at
that current version contains the schema. That version can be re-enabled
to get that old version.

Rich

Hi Rich,

Thanks for the prompt response.
With all the complications which you mentioned, what is your suggestion now?
Shall we go ahead with this task after installing testfix6 on both importing and exporting servers? Are there any precautions we need to take?

If we face any issues in importing, we will be able to retrieve the old version through that schema library old version backup....is this right?

Hi,

This is an iRAM system right? In which case contact your IBM rep in RAM
to discuss this. I shouldn't be the only input for having a test fix
applied. You need to have a broader input for something like that.

Thanks,
Rich

In general, yes... make sure both system are on the same level.

Libraries pick up global def. If you want to pick up community specific type/s categories .. you will need to add assets from these communities to the library (work around), to pick up the overided elements).

Is there any way by which an asset can be exported out from a repository and imported back to another one with the same GUID preserved in both repositories. Is there any way by using the libraries we can do this?

You can export assets withing libraries... on an import it will preserve the GUID, and information around the packaging (attributes, categories ...). It will not preserver the history/activity for that asset, nor its lifecycle approvals.