<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>JDS Media &#187; TEPS</title>
	<atom:link href="http://www.jdsmedia.net/category/itm-documentation/itm6x/teps/feed" rel="self" type="application/rss+xml" />
	<link>http://www.jdsmedia.net</link>
	<description>Tivoli deployment and integration</description>
	<lastBuildDate>Fri, 25 Nov 2011 00:46:10 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>TEPS 6.2 Client Java Upgrade</title>
		<link>http://www.jdsmedia.net/itm-documentation/itm6x/teps/teps-62-client-java-upgrade#utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/itm-documentation/itm6x/teps/teps-62-client-java-upgrade#comments</comments>
		<pubDate>Thu, 21 Aug 2008 17:45:42 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[TEPS]]></category>
		<category><![CDATA[browser]]></category>
		<category><![CDATA[browser session]]></category>
		<category><![CDATA[compatible logo]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[java plug]]></category>
		<category><![CDATA[JRE]]></category>
		<category><![CDATA[progress bar]]></category>
		<category><![CDATA[Select]]></category>
		<category><![CDATA[trust content]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/tivoli/itm6/teps/teps-62-client-java-upgrade/</guid>
		<description><![CDATA[In order for clients to access to TEPS upgraded to ITM6.2 for the first time, they&#8217;ll need to have the IBM JRE 1.5 installed on their system. It&#8217;s a very straightforward process, but if you need some guidance, the steps are outlined below. Have client access TEPS via a browser session: http://&#60;teps_server&#62;:1920///cnp/kdh/lib/cnp.html TEPS will detect [...]]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/itm-documentation/itm6x/teps/teps-62-client-java-upgrade/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TEPS: migrate-export.bat does not export MS-SQL</title>
		<link>http://www.jdsmedia.net/itm-documentation/itm6x/teps-migrate-exportbat-does-not-export-ms-sql#utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/itm-documentation/itm6x/teps-migrate-exportbat-does-not-export-ms-sql#comments</comments>
		<pubDate>Fri, 15 Aug 2008 18:29:51 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[ITM6.x]]></category>
		<category><![CDATA[TEPS]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/tivoli/itm6/teps/teps-issue-doesn%e2%80%99t-play-well-with-ms-sql/</guid>
		<description><![CDATA[Just discovered something which caused me some headache. The migrate-export.bat generates DB2 syntax statements by default, regardless if you&#8217;re using MS SQL or not for TEPS. Go ahead and try to import the &#8216;saveexport.sql&#8217; into your TEPS SQL db, it will cause some fun corruption. An APAR exists, but it still has not made it [...]]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/itm-documentation/itm6x/teps-migrate-exportbat-does-not-export-ms-sql/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

