Basically the usecase is we have IRC 3.4 data in form of Project/roundtrips folders in a machine A, now this machine A is getting very old and has to be replace with new machine B with upgraded IRC version i,e, WRC 4.1.
After copying the folder from Old A m/c to New B m/c in user folder and later imported the required project folder. Seems it works with many warning and error messages.
Warning/Error 1 : Many times continue Java related issues coming
Warning/Error 2 : Database lock issue coming
Warning/Error 3 : Identifiers are changed completely with Old and New m/c export operation
What is Expectation on this migration…
>> Copying of All IRC 3.4 project folders into new WRC 4.1 machine and achieve same Identifier whenever we perform further export operation.
Ex : Doc A exported in IRC 3.4(Old m/c) with Identifier “_9c27c8a1-75df-4876-b4f0-8e811fb20384” and when after copying all projects folder to new m/c, perform further export operation of Doc A in WRC 4.1(New m/c) the identifier should be same “_9c27c8a1-75df-4876-b4f0-8e811fb20384”.
Have few clarification needed,
1) If we are placing the old machine project folder to new machine, whether we need to maintain same user account(the old machine) for login or its fine with the new machine account. [Image 1]
2) What is mean by “Copy project into workspace” option in IRC/WRC. Its not clear.
3) How to maintain the same Identifier in new machine while exporting of document from same project roundtrip. As per process after copying of project files from Old to New machine the Identifiers should be same so that it will not impact on sharing with customer.
Image 1
Scenario A : ReqIf Export operation
1) Performed the ReqIf export operation in old m/c, and save the reqif file.
2) Performed the another ReqIf export operation in old m/c, and save the reqif file.
3) The Identifiers in both reqif export files will be exactly same even if we perform reqif export of same document from same roundtrip hundreds of time.
Scenario B : without selection of “Copy project into workspace”
1) Performed the ReqIf export operation in old m/c, and save the reqif file.
2) Document folder copied from OLD to NEW m/c and perform the import of workspace folder without selection of “Copy project into workspace”. 6) Performed the ReqIf export operation in new m/c, and save the reqif file.
3) The Identifiers in new m/c reqif export is not as identical as like available in old m/c exported reqif file.
Scenario C : with selection of “Copy project into workspace”
1) Performed the ReqIf export operation in old m/c, and save the reqif file.
2) Document folder copied from OLD to NEW m/c and perform the import of workspace folder with selection of “Copy project into workspace”
3) Performed the ReqIf export operation in new m/c, and save the reqif file.
4) The Identifiers in new m/c reqif export is not as identical as like available in old m/c exported reqif file.
Scenario D : ReqIf Export operation
1) Performed the ReqIf export operation in new m/c, and save the reqif file.
2) Performed the another ReqIf export operation in new m/c, and save the reqif file.
3) The Identifiers in both reqif export files will be exactly same even if we perform reqif export of same document from same roundtrip hundreds of time.
Image 2
Image 3
Kindly me know if anybody have any solution on this use case, let me know if you need any more detail on this, will connect for a short call.
Thanks
Regards,
Chittaranjan Pise
