Servigistics InService Publishing and Loading > Using Publishing and Loading > Servigistics InService Environment Configuration > Split Server Configuration Steps
  
Split Server Configuration Steps
A split server configuration adds an additional server to the process. In addition to the Publisher and Viewer servers, a Preview server is added enabling you to perform runtime TAL. You initially load the content from the Publisher server into the Preview server where you can verify that the process has worked correctly. You can perform this process while maintaining the current content on a Runtime Viewer server.
In order to perform a runtime TAL on a split server, you must perform additional split server configuration steps, apart from the normal split server configuration:
Preview Server
1. Stop the coreServer, CoreCMIServer, and jboss on both the Publisher and Viewer servers.
2. Create a folder named StorePackets on the Publisher server and ensure that it is shared by mounting the directory on both the Publisher and Viewer with read and write access.
3. Ensure that the following three properties are present in the 3c.properties file on the Publisher server:
remote.host.name=ppumsv-smlpd04d.ptcnet.ptc.com – Viewer or Runtime server host name
remote.site.port=8080 – Viewer or Runtime server port
PackageDestinationFolder=/net/ppuwsv-pscqa13d/StorePackets – Shared location of the Publisher server
If these properties are not present, add them in the 3c.properties file located in the INSERVICE_HOME/InS_SW/SW directory.
4. Navigate to the following location on the Publisher server: INSERVICE_HOME/InS_SW/Config/System/Config.
5. Open the SitesDescriptor.xml file and update/replace it with the following content:
<SitesDescriptor>
<Sites>
<Site id="Preview">
<Distribution type="FS">
<Datatransfer OS="linux" path="file.system.path"/>
</Distribution>
<Communication url="${remote.host.name}:${remote.port}"" />
</Site>
<Site id="Runtime">
<Communication url="${remote.host.name}:${remote.site.port}" />
</Site>
</Sites>
<SiteGroups>
<Group id="Preview">
<Site siteType=:LOCAL"id="Preview" master="YES"/>
</Group>
<Group id="Runtime">
<Distribution type="FS">
<Datatransfer OS="linux" path="${PackageDestinationFolder}"/>
</Distribution>
<Site siteType="REMOTE" id="Runtime" master="YES"/>
</Group>

</SiteGroups>
</SitesDescriptor>
* 
The Communication url tag for Site id = Preview consists of the server host name on which Publisher is installed, while for Site id = Runtime, the Communication url consist of the server host name on which the Viewer or Runtime server is installed.
* 
The OS will vary depending whether you are running Windows or Linux. For Windows 2008 R2 it should be windowsXP, and for RHEL, it should be linux.
6. At the same location mentioned above, open the SiteInfo.conf.xml file and replace the Distribution tag with the following content:
<Distribution type="FS">
<Datatransfer OS="windowsXP" path="${PackageDestinationFolder}"/>
</Distribution>
* 
The OS will vary depending whether you are running Windows or Linux. For Windows 2008 R2 it should be windowsXP, and for RHEL, it should be linux.
Runtime Server
1. Stop the coreServer, CoreCMIServer, and jboss on both the preview and runtime servers of the Preview server.
2. Ensure that the following property is present in the 3C.properties file on the Viewer server:
PackageDestinationFolder=/net/ppuwsv-pscqa13d/StorePackets – Shared location of the Publisher server
If this property is not present, add it in the 3c.properties file located at INSERVICE_HOME under the <Preview_InService >/InS_SW/SW/ directory.
3. Navigate to the following location in your INSERVICE_HOME directory:
<Viewer_InService>/InS_SW/Config/System/Config
4. Open the SitesDescriptor.xml file and update/replace it with the following content:
<SitesDescriptor>
<Sites>
<Site id="Preview">
<Distribution type="FS">
<Datatransfer OS="windowsXP" path="file.system.path"/>
</Distribution>
<Communication url="ppumsv-wbm11t.ptcnet.ptc.com:8080" />
</Site>
</SitesDescriptor>
The OS will vary depending whether you are running Windows or Linux. For Windows 2008 R2 it should be windowsXP, and for RHEL, it should be linux.
5. At the same location mentioned above, open the SiteInfo.conf.xml file and replace the Distribution tag with the following content:
<Distribution type="FS">
<Datatransfer OS="windowsXP" path="${PackageDestinationFolder}"/>
</Distribution>
The OS will vary depending whether you are running Windows or Linux. For Windows 2008 R2 it should be windowsXP, and for RHEL, it should be linux.
6. Restart the coreServer, coreCMIServer, and jboss on both the Publisher and Viewer servers.