My normal way of creating scripted domains shown here. Doesn't work very well with OSR, for some reason the domain template created by the pack script is corrupt. It took me a lot of digging to figure out what the problem was. Apparently the template-info.xml file contained inside the domain template jar file is incorrect and therefore unparseable which is also indicated by the error shown.
The workaround was to unzip the domain template jar file and change the line shown later in the template-info.xml file. Then zip the resulting files into a new jar file. So something like this.
Then change the following line:
Notice the version number change. Then zip up the template jar file again with:
WLST should be able to read the resulting newtemplate.jar template file. Don't ask me why this is a problem, but at least that fixed it for me.
com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.ScriptException: unable to parse "template-info.xml" from template jar <TEMPLATE FILE NAME>
The workaround was to unzip the domain template jar file and change the line shown later in the template-info.xml file. Then zip the resulting files into a new jar file. So something like this.
$ mkdir template
$ unzip template.jar -d template
$ cd template
$ vi template-info.xml
Then change the following line:
<comp-ref name="Oracle Service Registry" symbol="Oracle_Service_Registry_11.1.1_registry111_ORACLE_HOME" version="11.1.1"></comp-ref>
<comp-ref name="Oracle Service Registry" symbol="Oracle_Service_Registry_11.1.1_registry111_ORACLE_HOME" version="11.1.1.0">
</comp-ref>
Notice the version number change. Then zip up the template jar file again with:
$ zip -r newtemplate.jar *
WLST should be able to read the resulting newtemplate.jar template file. Don't ask me why this is a problem, but at least that fixed it for me.