Local Replication

Hi Amit,

Did your follow the PTC guide to the T? In your steps, you don't mention about the masterpub.key that is updated and exported from your site then place in your wt.properties for your replica site which is also your master. Then you perform a broadcast of your replica site to see if there is proper connectivity in your vaulting configuration.

Replication doesn't guarantee better performance over the WAN expecially over oceans. You have to look at your business information and where everything is created. Best to put the master applicaiton and database where the majority of information is created. Oh yes, it is really a bad assumption that it is based on the number of users. You need to keep the majority of the"flow"both meta data and content contained locally. A user working on a complex large assembly sometimes doesn't evenconnect to windchill till the end of the daywhen they need ot save their work. Basic 101experienceof implementingWindchill.

good luck,

Patrick

In Reply to amit lonkar:

Hi All,

STEPS:

1) Load local replica vaults, folders and mount them using Fvloader.
Syntax to create local replica vault: LRV,
Syntax to create local replica folder (same as creation of normal folder): RF,,
Syntax to mount folder (same as creation of normal mount): RM,,,
Enable replica folder: RFE,
Enable replica vault: RVE, (Introduced in 8.0 release)

2) Set the following property on master site:

3) Specify replication rules on these local vaults and run schedules.

4) Use the following CSV with Fvloader to move all local vaults to replica site: LRMV,,,,

5) Set the following property on master site:

6) Manually move content from master host to specified replica host.

7) Schedule replication on the new vaults - should show status "0 of 0 runs completed".

However, during replication at setp3, i am observing that nothing is getting replicated.

Has anyone come across this issue earlier? How to resolve this?

Thanks in advance!

~Amit

one more thing,

if you are installing a local file server, which is separate server and method server on the same machine as the master application and database server, you have to use a different port numbers and server aliases for you file server process.

You don't want your master server and foreground client methodservers in conflict.

good luck,

Patrick

In Reply to Patrick Chin:

Hi Amit,

Did your follow the PTC guide to the T? In your steps, you don't mention about the masterpub.key that is updated and exported from your site then place in your wt.properties for your replica site which is also your master. Then you perform a broadcast of your replica site to see if there is proper connectivity in your vaulting configuration.

Replication doesn't guarantee better performance over the WAN expecially over oceans. You have to look at your business information and where everything is created. Best to put the master applicaiton and database where the majority of information is created. Oh yes, it is really a bad assumption that it is based on the number of users. You need to keep the majority of the"flow"both meta data and content contained locally. A user working on a complex large assembly sometimes doesn't evenconnect to windchill till the end of the daywhen they need ot save their work. Basic 101experienceof implementingWindchill.

good luck,

Patrick

In Reply to amit lonkar:

Hi All,

STEPS:

1) Load local replica vaults, folders and mount them using Fvloader.
Syntax to create local replica vault: LRV,
Syntax to create local replica folder (same as creation of normal folder): RF,,
Syntax to mount folder (same as creation of normal mount): RM,,,
Enable replica folder: RFE,
Enable replica vault: RVE, (Introduced in 8.0 release)

2) Set the following property on master site:

3) Specify replication rules on these local vaults and run schedules.

4) Use the following CSV with Fvloader to move all local vaults to replica site: LRMV,,,,

5) Set the following property on master site:

6) Manually move content from master host to specified replica host.

7) Schedule replication on the new vaults - should show status "0 of 0 runs completed".

However, during replication at setp3, i am observing that nothing is getting replicated.

Has anyone come across this issue earlier? How to resolve this?

Thanks in advance!

~Amit