The 10.3.2 release of WebLogic Portal included changes to the file structure of the installation and packaging of the libraries. One impact to this is the need to manually update some of the legacy tools that are still included with the install but have not been updated for you. In this case, the XIP tool.
There is a support document that describes changes necessary to get the XIP tool working with 10.3.2, but it is not complete. Rather than making this entry longer and more confusing, I will ignore that article and simply list what I did to get it working.
The zip tools are located at [BEA_HOME]wlportal_10.3propagationbinxip. This is where the tool is run from and where the changes to make it work are done. All of changes are to the build.xml file. It starts with replacing the first block of two property declarations with a set of 5. For simplicity’s sake I hard-code the key definition though it is better to set this in a property file or pass it as an argument. The orginal block is:
<property name="wlserver.dir" value="@WL_HOME" /> <property name="wlportal.dir" value="@WLPORTAL_HOME" />
And the new block is:
<property name="bea.dir"
value="C:bea1032" />
<property name="wlserver.dir"
value="${bea.dir}wlserver_10.3" />
<property name="wlportal.dir"
value="${bea.dir}wlportal_10.3" />
<property name="workshop.dir"
value="${bea.dir}wlportal_10.3workshop"/>
<property name="modules.dir"
value="${bea.dir}modulescom.bea.p13n_10.3.2.0"/>
Next, under
<!-- Library locations, should not need to modify -->
We will make some major modifications. So much so that I will simply list the completed updates:
<property name="wls.classpath"
value="${wlserver.dir}/server/lib/wlclient.jar"/>
<property name="wlp.classpath"
value="${wlportal.dir}/light-portal/lib/system/
netuix_system.jar;${wlportal.dir}/p13n/lib/system/
p13n_system.jar"/>
<property name="wlp-library-dir"
value="${wlportal.dir}/portal/lib/j2ee-modules"/>
<property name="p13n-library-dir"
value="${wlportal.dir}/p13n/lib/j2ee-modules"/>
<property name="common-library-dir"
value="${workshop.dir}/common/deployable-libraries"/>
<property name="modules-library-dir"
value="${modules.dir}"/>
<property name="netuix-lib-app"
value="${wlportal.dir}/propagation/bin/xip/applib"/>
<target name="init.app.libs">
<libclasspath basedir="${netuix-lib-app}"
tmpdir="${templibdir}"
classpathproperty="libraries.classpath">
<librarydir dir="${wlp-library-dir}"/>
<librarydir dir="${p13n-library-dir}"/>
<librarydir dir="${common-library-dir}"/>
<librarydir dir="${modules-library-dir}"/>
</libclasspath>
</target>
If you have used the XIP tool before, once you have made the changes above, run the setDomainEnv script from a working WLP domain, then CD to the XIP path. From there, edit the xip.properties file to your needs and then run ant. The properties file is mostly self-explanatory, except that terms Import and Export are from the perspective of the database rather than where the script is being executed from. This means that if you want to get a .portal file from a running portal you would set the following in the xip.properties:
xip.command=export