Precautions for moving EAS Bos work areas and Development Platforms

When developing EAS Bos, we must first build the platform. To save time, we usually copy a development platform kinding630 and workspace630 from our colleagues. In the copy process. If the old guy put it on drive F, but I want to put it on drive D, drive F has no space. Okay. Finally, I copied it. In my heart. Open our development platform and start testing. But wait for half an hour. Still not moving at the original position. This is depressing ....

In fact, after the copy, we need to configure the runtime environment of the Work interval (the configuration to be modified is included in the runtime file ). For the development platform kingding630. Do not modify. Why? Because it is an exlipse. An exclipse with many plug-ins installed! Does exclipse Mobile affect the development work interval? No! Absolutely no. This is something you need to understand. Next, let's talk about the changes to the work interval.

1. Modify $ projectpath $ \ Runtime \ Server \ profiles \ server1 \ config \ bosconfig. xml
<Attribute key = "metadatapath" value = "D: \ workspace \ eWorld/metadata"/>
2. Modify $ projectpath $ \ Runtime \ Server \ profiles \ server1 \ config \ licensefile. xml
<URI> D: \ workspace \ eWorld \ Runtime \ Server \ profiles \ server1 \ config \ licenses \ license </uri>
3. Modify $ projectpath $ \ Runtime \ Server \ profiles \ server1 \ config \ portalconfig \ easwebconfig. xml
<! -- Local metadata loading path -->
<Attribute key = "metadatapath" value = "D: \ workspace \ eWorld \ metadata"/>
4. Modify $ projectpath $ \ eWorld \ Runtime \ apusic \ config \ Server. xml
<Server>
<Application name = "EAS. Ear" base = "D:/workspace/eWorld/runtime/Server/deploy/EAS. Ear" Start = "Auto"/>
</Server>

5. We need to modify the other part. change all the E drive letters in gpecsp_lib to the d drive letter to ensure that the BIM library in the build path is correct, that is, set the correct solution.