Adding a user to a group
sudo /usr/bin/dscl . -append /groups/wheel GroupMembership username
Default JAVA_HOME
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/
Thursday, February 19, 2009
Wednesday, February 11, 2009
WPS 6.1 installation fails for hostname having a dash
WebSphere Portal 6.1 install doesn't like host name with underscore (i.e. TOR_P35314X of my machine), the installation just fails and terminates. This might not be the preferred solution, but I have the following dirty trick just get-around with the issue for now - hope this help others facing the same problem.
1. Since the installation instruction claims not to use localhost or loopback address, add a dummy host name without score into Windows' host file.
127.0.0.1 torp35314x torp35314x.mcl.mrshmc.com
2. Start WPS 6.1 install, during the installation, it comes to a page with defualted node name and host name. Change the defaulted host name to the dummy name above. The install will prompt error of the inputed hostname doesn't match it's looked up name, just ignore the error and click OK/next to force the install to accept the dummy name.
3. Continue the installation.
1. Since the installation instruction claims not to use localhost or loopback address, add a dummy host name without score into Windows' host file.
127.0.0.1 torp35314x torp35314x.mcl.mrshmc.com
2. Start WPS 6.1 install, during the installation, it comes to a page with defualted node name and host name. Change the defaulted host name to the dummy name above. The install will prompt error of the inputed hostname doesn't match it's looked up name, just ignore the error and click OK/next to force the install to accept the dummy name.
3. Continue the installation.
Monday, November 17, 2008
iphone programming getting started
Started on iphone development. Came across couple useful links.
Standford CS193p iphone development course lectures.
http://www.stanford.edu/class/cs193p/cgi-bin/index.php
Standford CS193p iphone development course lectures.
http://www.stanford.edu/class/cs193p/cgi-bin/index.php
Wednesday, July 2, 2008
Maven adding source control to ClearCase
On my recent work, there's a requirement of having Maven to build an J2EE EAR file and then checkin the EAR to ClearCase. Maven SCM plugin has the ClearCase plugin, however, the scm:add command doesn't work for ClearCase. The problem got work around by executing Ant's ClearCase task in Maven.
Adding a source control to ClearCase involves three steps;
1 - Check out the containing folder of the new source file.
Acomplished by Ant task:
<cccheckout viewpath="c:/ci/view/my_view/MyFolder">
2 - Invoke the Clear Case mkelem command.
Acomplished by Ant task:
<ccmkelem viewpath="c:/ci/view/my_view/MyFolder/test4.ear" checkin="true" comment="Initial checkin">
</ccmkelem>
3 - Chech in the containing folder
Acomplished by Ant task:
<cccheckin viewpath="c:/ci/view/my_view/MyFolder" identical="true">
The complete POM:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>root.project</groupId>
<artifactId>MyProject</artifactId>
<packaging>pom</packaging>
<version>1.0-SNAPSHOT</version>
<name>MyProject</name>
<scm>
<connection>scm:clearcase:config_spec.txt</connection>
<developerConnection>scm:clearcase:config_spec.txt</developerConnection>
</scm>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.1</version>
<executions>
<execution>
<phase>package</phase>
<goals><goal>run</goal></goals>
<configuration>
<tasks>
<property name="plugin_classpath" refid="maven.plugin.classpath"/>
<echo message="plugin classpath: ${plugin_classpath}"/>
<cccheckout viewpath="c:/ci/view/my_view/MyFolder"/>
<ccmkelem viewpath="c:/ci/view/my_view/MyFolder/test4.ear"
checkin="true"
comment="Initial checkin">
</ccmkelem>
<cccheckin viewpath="c:/ci/view/my_view/MyFolder"
identical="true"/>
</tasks>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>
Adding a source control to ClearCase involves three steps;
1 - Check out the containing folder of the new source file.
Acomplished by Ant task:
<cccheckout viewpath="c:/ci/view/my_view/MyFolder">
2 - Invoke the Clear Case mkelem command.
Acomplished by Ant task:
<ccmkelem viewpath="c:/ci/view/my_view/MyFolder/test4.ear" checkin="true" comment="Initial checkin">
</ccmkelem>
3 - Chech in the containing folder
Acomplished by Ant task:
<cccheckin viewpath="c:/ci/view/my_view/MyFolder" identical="true">
The complete POM:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>root.project</groupId>
<artifactId>MyProject</artifactId>
<packaging>pom</packaging>
<version>1.0-SNAPSHOT</version>
<name>MyProject</name>
<scm>
<connection>scm:clearcase:config_spec.txt</connection>
<developerConnection>scm:clearcase:config_spec.txt</developerConnection>
</scm>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.1</version>
<executions>
<execution>
<phase>package</phase>
<goals><goal>run</goal></goals>
<configuration>
<tasks>
<property name="plugin_classpath" refid="maven.plugin.classpath"/>
<echo message="plugin classpath: ${plugin_classpath}"/>
<cccheckout viewpath="c:/ci/view/my_view/MyFolder"/>
<ccmkelem viewpath="c:/ci/view/my_view/MyFolder/test4.ear"
checkin="true"
comment="Initial checkin">
</ccmkelem>
<cccheckin viewpath="c:/ci/view/my_view/MyFolder"
identical="true"/>
</tasks>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>
Wednesday, June 25, 2008
EJB Interoperability of JBoss Portal and IBM WAS
This posting outlined how we configured the servers to have a Portlet which runs in JBoss Portal making EJB calls to WAS. This involves couple of challenges:
- Interoperability between IBM and Non IBM components on JNDI binding and EJB calls.
- Compatibility of different JDK versions among Portal and Middle tier.
- The situation of having JDK 1.5 running JBossPortal and JDK 1.4 running WAS.
1. Preparing JBoss Portal for WAS EJB interoperability
- Install IBM JDK 5, run JBossPortal using IBM JDK. IBM packaged their low level CORBA//IIOP classes in their JDK runtime, using standard Sun's JDK5 results to a lot of Class Not Found Exception.
- Copy jacorb.jar from $JBOSS_HOME\client to $JBOSS_HOME\server\default\lib
- Copy jboss-iiop-client.jar from $JBOSS_HOME\client to $JBOSS_HOME\server\default\lib
2. Packing Portlet application for WAS EJB Client
The following IBM jars are required to package into the WEB-INF\lib directory of the Portlet's WAR.
- naming.jar
- naminglcient.jar
- wsexception.jar
- iwsorb.jar
- ras.jar
- bootstrap.jar
- emf.jar
- ecutils.jar
- ffdc.jar
- idl.jar
- Interoperability between IBM and Non IBM components on JNDI binding and EJB calls.
- Compatibility of different JDK versions among Portal and Middle tier.
- The situation of having JDK 1.5 running JBossPortal and JDK 1.4 running WAS.
1. Preparing JBoss Portal for WAS EJB interoperability
- Install IBM JDK 5, run JBossPortal using IBM JDK. IBM packaged their low level CORBA//IIOP classes in their JDK runtime, using standard Sun's JDK5 results to a lot of Class Not Found Exception.
- Copy jacorb.jar from $JBOSS_HOME\client to $JBOSS_HOME\server\default\lib
- Copy jboss-iiop-client.jar from $JBOSS_HOME\client to $JBOSS_HOME\server\default\lib
2. Packing Portlet application for WAS EJB Client
The following IBM jars are required to package into the WEB-INF\lib directory of the Portlet's WAR.
- naming.jar
- naminglcient.jar
- wsexception.jar
- iwsorb.jar
- ras.jar
- bootstrap.jar
- emf.jar
- ecutils.jar
- ffdc.jar
- idl.jar
Subscribe to:
Comments (Atom)