<?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>HollyGhozi &#187; Landmark</title>
	<atom:link href="http://hollyghozi.com/index.php/category/landmark/feed/" rel="self" type="application/rss+xml" />
	<link>http://hollyghozi.com</link>
	<description>is another Javanese Indonesian fellow blog</description>
	<lastBuildDate>Mon, 12 Dec 2011 01:52:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>LAM License Allocation</title>
		<link>http://hollyghozi.com/index.php/2011/09/lam-license-allocation/</link>
		<comments>http://hollyghozi.com/index.php/2011/09/lam-license-allocation/#comments</comments>
		<pubDate>Mon, 19 Sep 2011 11:48:34 +0000</pubDate>
		<dc:creator>hollyghozi</dc:creator>
				<category><![CDATA[Landmark]]></category>
		<category><![CDATA[LAM]]></category>
		<category><![CDATA[license]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://hollyghozi.com/?p=214</guid>
		<description><![CDATA[Sometime we need to allocate certain number of feature for different group of users. LAM, which is product of Flexera, has a capability to limit and/or allocate certain feature of license to particular group of user based on their operating system user name and/or hostname. As quick an example, these steps will guide us to [...]]]></description>
			<content:encoded><![CDATA[<p>Sometime we need to allocate certain number of feature for different group of users. LAM, which is product of <a href="http://www.flexerasoftware.com/" title="Flexera">Flexera</a>, has a capability to limit and/or allocate certain feature of license to particular group of user based on their operating system user name and/or hostname.</p>
<p>As quick an example, these steps will guide us to limit Landmark&#8217;s license feature:<br />
1. Refer the configuration file in the license.dat<br />
<!--DEVFMTCODE--><pre class="devcodeblock" title="INI"><div class="devcodeoverflow"><ol><li>DAEMON licsrv C:\landmark\LAM5000\bin\licsrv C:\Landmark\LAM5000\licsrv.opt</li></ol></div></pre><!--END_DEVFMTCODE--><br />
2. Create configuration file as follow:<br />
<!--DEVFMTCODE--><pre class="devcodeblock" title="INI"><div class="devcodeoverflow"><ol><li># usage report</li><li>#REPORTLOG +C:\Landmark\LAM5000\licsrvreport.log</li><li>DEBUGLOG +C:\Landmark\LAM5000\licsrvdebug.log</li><li>&nbsp;</li><li># Configuration</li><li>GROUPCASEINSENSITIVE ON</li><li>&nbsp;</li><li># Define grouping, based on Computer name and/or User name</li><li>HOST_GROUP grpserver dohaserver</li><li>HOST_GROUP grpclient jakartaclient</li><li>GROUP grpadmin <span style="">32547</span> <span style="">32548</span></li><li>&nbsp;</li><li># Reserve a license feature to particular group</li><li>RESERVE <span style="">1</span> EDM HOST_GROUP grpclient </li><li>RESERVE <span style="">1</span> EDM HOST_GROUP grpserver</li><li>RESERVE <span style="">1</span> OPWPACKAGE GROUP grpadmin</li><li>&nbsp;</li><li># to limit a specific user/group</li><li>MAX <span style="">1</span> EDM GROUP grpadmin</li></ol></div></pre><!--END_DEVFMTCODE--><br />
The above configuration file will create 2 group based on hostname and 1 group of username, reserve a license to particular group, and limit the number of license feature for particular group.</p>
]]></content:encoded>
			<wfw:commentRss>http://hollyghozi.com/index.php/2011/09/lam-license-allocation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Start Another Instance of OpenWells</title>
		<link>http://hollyghozi.com/index.php/2011/09/start-another-instance-of-openwells/</link>
		<comments>http://hollyghozi.com/index.php/2011/09/start-another-instance-of-openwells/#comments</comments>
		<pubDate>Sun, 18 Sep 2011 08:19:13 +0000</pubDate>
		<dc:creator>hollyghozi</dc:creator>
				<category><![CDATA[Landmark]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Drilling]]></category>
		<category><![CDATA[EDM]]></category>
		<category><![CDATA[OpenWells]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://hollyghozi.com/?p=201</guid>
		<description><![CDATA[By default, Landmark OpenWells application will not allow us to start another instance of OpenWells. If you start OpenWells, you will not be able to start another one. Clicking the &#8216;OpenWells&#8217; icon just activate the existing running OpenWells instance. To start the second instance of OpenWells, you may need to suffix additional parameter &#8220;/NEWINSTANCE&#8221; in [...]]]></description>
			<content:encoded><![CDATA[<p>By default, Landmark OpenWells application will not allow us to start another instance of OpenWells. If you start OpenWells, you will not be able to start another one. Clicking the &#8216;OpenWells&#8217; icon just activate the existing running OpenWells instance.</p>
<p>To start the second instance of OpenWells, you may need to suffix additional parameter &#8220;<strong>/NEWINSTANCE</strong>&#8221; in the command line. For example:<br />
<!--DEVFMTCODE--><pre class="devcodeblock" title="'dos'"><div class="devcodeoverflow"><ol><li>C:\Landmark\EDT_5000.1\OpenWells\Bin\RunOpenWells.bat /NEWINSTANCE</li></ol></div></pre><!--END_DEVFMTCODE--></p>
<p>The command above will start second OpenWells instance.</p>
]]></content:encoded>
			<wfw:commentRss>http://hollyghozi.com/index.php/2011/09/start-another-instance-of-openwells/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PowerHub JDBC Log</title>
		<link>http://hollyghozi.com/index.php/2009/09/powerhub-jdbc-log/</link>
		<comments>http://hollyghozi.com/index.php/2009/09/powerhub-jdbc-log/#comments</comments>
		<pubDate>Tue, 15 Sep 2009 07:13:09 +0000</pubDate>
		<dc:creator>hollyghozi</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Landmark]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[PowerHub]]></category>

		<guid isPermaLink="false">http://hollyghozi.com/?p=194</guid>
		<description><![CDATA[I&#8217;m supporting CDS in Oil Company based in the Netherland. CDS is a suite of application, one of the application is PowerHub. If I face a problem, I&#8217;ve to debug the PowerHub. One of method is to use log4jdbc. What I do is: 1. Download the log4jdbc4-1.2alpha2.jar, and put into $PE_HOME/jars 2. Download from SL4J [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m supporting <a href="http://www.halliburton.com/public/landmark/contents/Data_Sheets/web/H05239.pdf">CDS</a> in Oil Company based in the Netherland. CDS is a suite of application, one of the application is PowerHub.<br />
If I face a problem, I&#8217;ve to debug the PowerHub. One of method is to use <a href="http://code.google.com/p/log4jdbc/">log4jdbc</a>.</p>
<p>What I do is:<br />
1. Download the <a href="http://log4jdbc.googlecode.com/files/log4jdbc4-1.2alpha2.jar">log4jdbc4-1.2alpha2.jar</a>, and put into $PE_HOME/jars<br />
2. Download from <a href="http://www.slf4j.org">SL4J</a>  the compress file: <a href="http://www.slf4j.org/dist/slf4j-1.5.8.tar.gz">slf4j-1.5.8.tar.gz</a>. Extract slf4j-api-1.5.8.jar and slf4j-simple-1.5.8.jar from the compress file, and put into $PE_HOME/jars<br />
3. Modify $PE_HOME/conf/pe_dic.props, remark the old value and change the line:<br />
<!--DEVFMTCODE--><pre class="devcodeblock" title="'dos'"><div class="devcodeoverflow"><ol><li>#pe_dic.Url=jdbc:oracle:thin:@myoraclemachine:1521:PHDIC</li><li>pe_dic.Url=jdbc:log4jdbc:oracle:thin:@myoraclemachine:1521:PHDIC</li><li>#pe_dic.Driver=oracle.jdbc.driver.OracleDriver</li><li>pe_dic.Driver=net.sf.log4jdbc.DriverSpy</li></ol></div></pre><!--END_DEVFMTCODE--><br />
4. Restart the PowerHub</p>
<p>You&#8217;ll need to check your $PE_HOME/logs/pe_dic-server.log, to see the additional jdbc log messages.<br />
Below is the snippet of the log file:<br />
<!--DEVFMTCODE--><pre class="devcodeblock" title="'dos'"><div class="devcodeoverflow"><ol><li>.........</li><li>11824 [main] INFO jdbc.audit - 1. Connection.isClosed() returned false</li><li>11824 [main] INFO jdbc.audit - 1. Statement.new Statement returned </li><li>11824 [main] INFO jdbc.audit - 1. Connection.createStatement() returned net.sf.log4jdbc.StatementSpy@2e67cd84</li><li>11824 [main] INFO jdbc.sqlonly - SELECT upper(d.DATASTORE_NAME),c.DATABASE_S,c.DATABASE_NAME,c.TYPE,c.DRIVER,c.URL,c.TWO_TASK,c.SEQ_NAME,c.CLASS_NAME,c.PRIVATE </li><li>FROM SLG_DATABASE c, SLG_DATASTORE d WHERE c.DATASTORE_S=d.DATASTORE_S ORDER BY d.DATASTORE_NAME,c.DATABASE_NAME </li><li></li><li>11833 [main] INFO jdbc.sqltiming - SELECT upper(d.DATASTORE_NAME),c.DATABASE_S,c.DATABASE_NAME,c.TYPE,c.DRIVER,c.URL,c.TWO_TASK,c.SEQ_NAME,c.CLASS_NAME,c.PRIVATE </li><li>FROM SLG_DATABASE c, SLG_DATASTORE d WHERE c.DATASTORE_S=d.DATASTORE_S ORDER BY d.DATASTORE_NAME,c.DATABASE_NAME </li><li> {executed in 9 msec}</li><li>11833 [main] INFO jdbc.resultset - 1. ResultSet.new ResultSet returned </li><li>11833 [main] INFO jdbc.audit - 1. Statement.executeQuery(SELECT upper(d.DATASTORE_NAME),c.DATABASE_S,c.DATABASE_NAME,c.TYPE,c.DRIVER,c.URL,c.TWO_TASK,c.SEQ_NAME,c.CLASS_NAME,c.PRIVATE FROM SLG_DATABASE c, SLG_DATASTORE d WHERE c.DATASTORE_S=d.DATASTORE_S ORDER BY d.DATASTORE_NAME,c.DATABASE_NAME) returned net.sf.log4jdbc.ResultSetSpy@20e5ace9</li><li>11833 [main] INFO jdbc.resultset - 1. ResultSet.next() returned true</li><li>11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(1) returned AOI_SHAPEFILE</li><li>11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(2) returned 1263</li><li>11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(3) returned AOI_SHAPEFILE</li><li>11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(4) returned shapefile</li><li>11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(5) returned dummy</li><li>11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(6) returned dummy</li><li>11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(7) returned dummy</li><li>11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(8) returned seq</li><li>11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(9) returned null</li><li>11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(10) returned N</li><li>11833 [main] INFO jdbc.resultset - 1. ResultSet.next() returned true</li><li>.............</li></ol></div></pre><!--END_DEVFMTCODE--><br />
From the log file, you can see that the PowerHub tries to read the dictionary to get the databases information&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://hollyghozi.com/index.php/2009/09/powerhub-jdbc-log/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Couple of OpenWorks variables</title>
		<link>http://hollyghozi.com/index.php/2009/08/couple-of-openworks-variables/</link>
		<comments>http://hollyghozi.com/index.php/2009/08/couple-of-openworks-variables/#comments</comments>
		<pubDate>Wed, 12 Aug 2009 13:46:34 +0000</pubDate>
		<dc:creator>hollyghozi</dc:creator>
				<category><![CDATA[Landmark]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[OpenWorks]]></category>

		<guid isPermaLink="false">http://hollyghozi.com/?p=191</guid>
		<description><![CDATA[Today, I&#8217;ve learned two OpenWorks environment variables. 1. OW_DEFAULT_DISTRICT You will have to set the value of this environment variable, if you want to set the default DISTRICT. export OW_DEFAULT_DISTRICT=OWSIDEAST After you set the variable, then start your OpenWorks > Project Status, you&#8217;ll see the DISTRICT already been choosen. 2. OW_ADMIN_UTILS_PW You will need to [...]]]></description>
			<content:encoded><![CDATA[<p>Today, I&#8217;ve learned two OpenWorks environment variables.<br />
1. OW_DEFAULT_DISTRICT<br />
You will have to set the value of this environment variable, if you want to set the default DISTRICT.<br />
<!--DEVFMTCODE--><pre class="devcodeblock" title="Bash"><div class="devcodeoverflow"><ol><li><span style="color: #7a0874; font-weight: bold;">export</span> <span style="color: #007800;">OW_DEFAULT_DISTRICT</span>=OWSIDEAST</li></ol></div></pre><!--END_DEVFMTCODE--><br />
After you set the variable, then start your OpenWorks > Project Status, you&#8217;ll see the DISTRICT already been choosen.</p>
<p>2. OW_ADMIN_UTILS_PW<br />
You will need to set the value of this environment variable, if you change the password of OW_ADMIN_UTILS.<br />
<!--DEVFMTCODE--><pre class="devcodeblock" title="Bash"><div class="devcodeoverflow"><ol><li><span style="color: #7a0874; font-weight: bold;">export</span> <span style="color: #007800;">OW_ADMIN_UTILS_PW</span>=owadminutilspassword</li></ol></div></pre><!--END_DEVFMTCODE--></p>
]]></content:encoded>
			<wfw:commentRss>http://hollyghozi.com/index.php/2009/08/couple-of-openworks-variables/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cannot find modules error when try to install</title>
		<link>http://hollyghozi.com/index.php/2009/08/cannot-find-modules-error-when-try-to-install/</link>
		<comments>http://hollyghozi.com/index.php/2009/08/cannot-find-modules-error-when-try-to-install/#comments</comments>
		<pubDate>Wed, 05 Aug 2009 13:33:47 +0000</pubDate>
		<dc:creator>hollyghozi</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Landmark]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[PowerHub]]></category>

		<guid isPermaLink="false">http://hollyghozi.com/?p=189</guid>
		<description><![CDATA[We&#8217;re installing PowerHub using its installer in Linux machine. The installer is built using InstallAnyWhere, that use JRE inside the installer. The problem happen when we try to install as a user which its home directory is not mounted. We tried to set the HOME to other directory by setting up HOME environment variable. But, [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;re installing PowerHub using its installer in Linux machine. The installer is built using InstallAnyWhere, that use JRE inside the installer. </p>
<p>The problem happen when we try to install as a user which its home directory is not mounted. We tried to set the HOME to other directory by setting up HOME environment variable. But, we got:<br />
<code>No module find error</code></p>
<p>Then we try to debug the installation by:<br />
<code>sh -x setup.bin</code><br />
It come back with a lot of debug messages, and at the end we will see a line with:<br />
<code>CLASSPATH=/tmp/install.829388/jar/...<br />
exec /tmp/install.829388/jre/bin/java ....</code></p>
<p>What we did is to manipulate the user home by<br />
<code>$export CLASSPATH=/tmp/install.829388/jar/...<br />
/tmp/install.829388/jre/bin/java -Duser.home=/tmp/tmpdir ... </code><br />
This way, we will force the installer to use different HOME directory</p>
]]></content:encoded>
			<wfw:commentRss>http://hollyghozi.com/index.php/2009/08/cannot-find-modules-error-when-try-to-install/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PowerHub: Installation Error with &#8216;/tmp does not have enough disk space&#8217;</title>
		<link>http://hollyghozi.com/index.php/2009/05/powerhub-installation-error-with-tmp-does-not-have-enough-disk-space/</link>
		<comments>http://hollyghozi.com/index.php/2009/05/powerhub-installation-error-with-tmp-does-not-have-enough-disk-space/#comments</comments>
		<pubDate>Mon, 18 May 2009 12:20:14 +0000</pubDate>
		<dc:creator>hollyghozi</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Landmark]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[PowerHub]]></category>

		<guid isPermaLink="false">http://hollyghozi.com/?p=173</guid>
		<description><![CDATA[When I&#8217;m installing PowerHub, I encounter the error message: WARNING: /tmp does not have enough disk space! Attempting to use /glb/home/s_peam01 for install base and tmp dir. Extracting the JRE from the installer archive... The included VM could not be extracted. Please try to download the installer again and make sure that you download using [...]]]></description>
			<content:encoded><![CDATA[<p>When I&#8217;m installing PowerHub, I encounter the error message:<br />
<code>WARNING: /tmp does not have enough disk space!<br />
         Attempting to use /glb/home/s_peam01 for install base and tmp dir.<br />
Extracting the JRE from the installer archive...<br />
The included VM could not be extracted. Please try to download<br />
the installer again and make sure that you download using 'binary'<br />
mode.  Please do not attempt to install this currently downloaded copy.</code></p>
<p>The work around is to set IATEMPDIR environment to location that has sufficient space<br />
<code>$ export IATEMPDIR=/glb/apps/3rdparty_test/tmp</code></p>
]]></content:encoded>
			<wfw:commentRss>http://hollyghozi.com/index.php/2009/05/powerhub-installation-error-with-tmp-does-not-have-enough-disk-space/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PHJDBC: Temporary Remove the Java System Output</title>
		<link>http://hollyghozi.com/index.php/2009/05/phjdbc-temporary-remove-the-java-system-output/</link>
		<comments>http://hollyghozi.com/index.php/2009/05/phjdbc-temporary-remove-the-java-system-output/#comments</comments>
		<pubDate>Wed, 13 May 2009 07:52:19 +0000</pubDate>
		<dc:creator>hollyghozi</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Landmark]]></category>

		<guid isPermaLink="false">http://hollyghozi.com/?p=154</guid>
		<description><![CDATA[When I execute SQL query using PowerHub JDBC driver, it always gives connection status. Connecting to //powerhubmachine/pe_dic-server Connected to ////powerhubmachine/pe_dic-server (PowerHub 20.0) To remove this output, I temporarily redirect the output to &#8216;null&#8217;, as shown in snippet below: private void connect() throws IOException { try { PrintStream oriOut = System.out; System.setOut(new PrintStream(new OutputStream(){public void write [...]]]></description>
			<content:encoded><![CDATA[<p>When I execute SQL query using PowerHub JDBC driver, it always gives connection status.<br />
<code>Connecting to //powerhubmachine/pe_dic-server<br />
Connected  to ////powerhubmachine/pe_dic-server (PowerHub 20.0)</code></p>
<p>To remove this output, I temporarily redirect the output to &#8216;null&#8217;, as shown in snippet below:<br />
<code> private void connect() throws IOException<br />
   {<br />
    	try {<br />
    		PrintStream oriOut = System.out;<br />
    		System.setOut(new PrintStream(new OutputStream(){public void write (int b){}}));<br />
			 Class.forName("com.lgc.dam.phs.client.jdbc.PhsJDBCDriver");<br />
			 if (connurl!=null) {<br />
	    		 conn = DriverManager.getConnection(connurl);<br />
			 } else {<br />
	    		 conn = DriverManager.getConnection("jdbc:scwapi://"+phserver+"/"+pedic+"-"+rmiserver+";"+username+";"+password+";SYSTEM;SYSTEM");<br />
			 }<br />
			 System.setOut(oriOut);<br />
		} catch (Exception e) {<br />
			System.out.println(e.toString());<br />
		}<br />
    }<br />
</code></p>
<p>Using the &#8216;setOut&#8217; to newly create empty OutputStream, it hides the output. After finish, &#8216;setOut&#8217; to original OuputStream.</p>
]]></content:encoded>
			<wfw:commentRss>http://hollyghozi.com/index.php/2009/05/phjdbc-temporary-remove-the-java-system-output/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OpenWorks: Create default Wallet</title>
		<link>http://hollyghozi.com/index.php/2009/05/openworks-create-default-wallet/</link>
		<comments>http://hollyghozi.com/index.php/2009/05/openworks-create-default-wallet/#comments</comments>
		<pubDate>Mon, 04 May 2009 08:48:47 +0000</pubDate>
		<dc:creator>hollyghozi</dc:creator>
				<category><![CDATA[Landmark]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Oracle]]></category>
		<category><![CDATA[OpenWorks]]></category>

		<guid isPermaLink="false">http://hollyghozi.com/?p=150</guid>
		<description><![CDATA[As addition to the OpenWorks: OS Authentication in R5000. You can create default wallet without having to login into OpenWorks by running the script below. Before you run the script, you have to make sure that the following environment variable is populated correctly: OWHOME OWSYSSID ORACLE_HOME OW_HOME_DIR From your linux shell, please run the following: [...]]]></description>
			<content:encoded><![CDATA[<p>As addition to the OpenWorks: <a href="http://hollyghozi.com/?p=141">OS Authentication in R5000</a>. You can create default wallet without having to login into OpenWorks by running the script below.</p>
<p>Before you run the script, you have to make sure that the following environment variable is populated correctly:<br />
<code>OWHOME<br />
OWSYSSID<br />
ORACLE_HOME<br />
OW_HOME_DIR</code></p>
<p>From your linux shell, please run the following:<br />
<code>Bash$ ${OWHOME}/jre/bin/java \<br />
-classpath ${OWHOME}/jar/com_lgc_ow_devkit.jar \<br />
com.lgc.ow.credentials.OracleWallet \<br />
${OWSYSSID} ${ORACLE_HOME} ${OW_HOME_DIR}</code></p>
<p>If it&#8217;s not exist, it will create ${HOME}/wallet directory with user and password entry. The password created by the script has to be equal as the user. If you have different password value, you&#8217;ll need to use the default OpenWorks user dialog.</p>
]]></content:encoded>
			<wfw:commentRss>http://hollyghozi.com/index.php/2009/05/openworks-create-default-wallet/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>OpenWorks: OS Authentication in R5000</title>
		<link>http://hollyghozi.com/index.php/2009/04/openworks-os-authentication-in-r5000/</link>
		<comments>http://hollyghozi.com/index.php/2009/04/openworks-os-authentication-in-r5000/#comments</comments>
		<pubDate>Sat, 25 Apr 2009 02:29:13 +0000</pubDate>
		<dc:creator>hollyghozi</dc:creator>
				<category><![CDATA[Landmark]]></category>
		<category><![CDATA[Oracle]]></category>
		<category><![CDATA[OpenWorks]]></category>

		<guid isPermaLink="false">http://hollyghozi.com/?p=141</guid>
		<description><![CDATA[OpenWorks R2003 use traditional external user as the authentication. By simply, creating user via sqlplus: create user osuser identified externally And you can connect to OpenWorks Oracle database by: sqlplus /@openworksdb In R5000, end user is still able to logon without password but the method is slightly different. R5000 uses Oracle Secure External Password Store. [...]]]></description>
			<content:encoded><![CDATA[<p>OpenWorks R2003 use traditional external user as the authentication. By simply, creating user via sqlplus:<br />
<code>create user osuser identified externally</code><br />
And you can connect to OpenWorks Oracle database by:<br />
<code>sqlplus /@openworksdb</code></p>
<p>In R5000, end user is still able to logon without password but the method is slightly different. R5000 uses Oracle Secure External Password Store. There&#8217;s a good tutorial on this created by <a href="http://www.oracle-base.com/articles/10g/SecureExternalPasswordStore_10gR2.php">oracle-base.com</a>.</p>
<p>The wallet directory is set by ${OW_HOME_DIR} environment variable. By default the value is equal as ${HOME}. You would see wallet directory in your home directory. So, if your R5000 environment is set correctly, you will able to do:<br />
<code>sqlplus /@openworksdb</code></p>
]]></content:encoded>
			<wfw:commentRss>http://hollyghozi.com/index.php/2009/04/openworks-os-authentication-in-r5000/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>OpenWorks: Create interpretation project failed (2)</title>
		<link>http://hollyghozi.com/index.php/2009/04/openworks-create-interpretation-project-failed-2/</link>
		<comments>http://hollyghozi.com/index.php/2009/04/openworks-create-interpretation-project-failed-2/#comments</comments>
		<pubDate>Sun, 12 Apr 2009 05:02:50 +0000</pubDate>
		<dc:creator>hollyghozi</dc:creator>
				<category><![CDATA[Landmark]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[OpenWorks]]></category>

		<guid isPermaLink="false">http://hollyghozi.com/?p=138</guid>
		<description><![CDATA[In addition to my post earliear, there&#8217;s something else that we can do to minimize the error: chmod -R o+rx $ORACLE_HOME By make sure everyone has access to the Oracle&#8217;s library and executable, it&#8217;ll enable the user to create the Interpretation project.]]></description>
			<content:encoded><![CDATA[<p>In addition to <a title="OpenWorks: Create interpretation project failed" href="http://hollyghozi.com/?p=45">my post earliear</a>, there&#8217;s something else that we can do to minimize the error:<br />
<code>chmod -R o+rx $ORACLE_HOME</code><br />
By make sure everyone has access to the Oracle&#8217;s library and executable, it&#8217;ll enable the user to create the Interpretation project.</p>
]]></content:encoded>
			<wfw:commentRss>http://hollyghozi.com/index.php/2009/04/openworks-create-interpretation-project-failed-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

