I use this sort of syntax, explicitly giving the domain directory.
./pack.sh -managed=true -domain=/orclapps/oracle/middleware/user_projects/domains/SOADomain -template=/tmp/soa_domain_template.jar -template_name=soa_domain_template
and then on the 2nd node ( after copying the template jar )
./unpack.sh -domain=/orclapps/oracle/middleware/user_projects/domains/SOADomain -template=/tmp/soa_domain_template.jar
Thank you for your reply. I am using the same syntax but still don't have the config.xml file. Any other ideas?
update: I don't know if it is a bug or whatever but I solved this by manually editing startManagedWeblogic.sh on the second machine and changing the domain and admin url to the correct values. You would think the pack utility would take care of the variable substitution but it didn't in this case.
what variable substitution?
Also, does the template jar you generated on machine #1 contain config.xml?
Admin server on HOST_1 should be working. And Oracle itself copy config.xml from HOST_1 to HOST_2. (For example, when you try to extend domain with oim.)
Usually Oracle write
cfgfwk-64051: Select a specific domain
when you try to extend domain (step 2 select domain home directory) without config.xml