This java class converts Windchill Windu output (DomainPolicyRule.txt) to a LoadFromFile xml. One that can be used to export from one server & imported (LoadFromFile) into Windchill on a different server. The Windu putput works better than qml output (csv or xml), because the Windu output file had the exact correct [domain]/context output: [/wt.inf.container.OrgContainer=DJ_WC/wt.inf.library.WTLibrary=Library_DJ]/Default Steps for run: 1) From Windchill Shell: Windu. When app opens, make sure all are unselected, except for "Domain Policy Rule Report". Then select "Run". It creates a new folder in \WinDU\logs. I think the folder in date stamped. Just make sure you point the class to the latest folder created. Windu places a DomainPolicyRule.txt output file in that newly created folder. The only argument required for the ACL_Windu2XML class is the full path to that DomainPolicyRule.txt. It uses that file to parse. 2) Unzip & place class (maybe java src also) in the folder: \codebase\ext It imports no Windchill classes, so it should work from any ext folder, but might need -cp declared (-classpath). It was complied with jdk 1.6.0_16 3) From Windchill Shell: java ext.ACL_Windu2XML \WinDU\logs\08-28_15-04 You'll have different date stamped folder, in the Windu logs folder. It will create the LoadFromFile xml file in the same folder as the DomainPolicyRule.txt file. In the Windchil shell, the class will print the same content that will be in the xml. So you can actually pipe it to a local xml file, for test purposes. Like this: C:\temp\ext.ACL_Windu2XML> java -classpath . ext.ACL_Windu2XML C:\temp\ext.ACL_Windu2XML\ext java ext.ACL_Windu2XML \WinDU\logs\08-28_15-04 The new xml file (placed in Windu logs folder) will be named: DomainPolicyRule_ACL_LoadFromFile_083010_044914.xml It date stamps the name in this format: (MMddyy_HHmmss), with date_time of class run. Larry Jett cadjett@aol.com,datajett@aol.com