[ https://issues.apache.org/jira/browse/OFBIZ-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shi Yusen updated OFBIZ-1724: ----------------------------- Attachment: rmiclient.zip As I'm using an ofbiz-base.jar built from OFBiz 514134 which can use trustStore and keyStore configed in jsse.properties, and I don't know how to add it to a patch, so I use zip instead of a patch file. > rmiservice and rmiclient > ------------------------ > > Key: OFBIZ-1724 > URL: https://issues.apache.org/jira/browse/OFBIZ-1724 > Project: OFBiz > Issue Type: Improvement > Affects Versions: Release Branch 4.0 > Environment: FC7 + JDK 1.6 + OFBiz 4.0 + Tomcat 5.5.26 > Reporter: Shi Yusen > Priority: Trivial > Fix For: Release Branch 4.0 > > Attachments: rmiclient.zip > > > My colleage Li Shuang removed the dependence of rmiclient code and OpenCms. > And I tested the new code with OFBiz 4.0, seems ok. Here are the steps on how > to make the rmiservice and rmiclient work: > 1. Unzip rmiservice.zip and rmiclient under specialpurpose. > 2. Edit specialpurpose/component-load.xml, add > <load-component component-location="${ofbiz.home}/specialpurpose/rmiservice"/> > 3. In specialpurpose/rmiclient/sslcert/, run createcsr.sh > 4. If you run a Linux box, you can use TinyCA2 to sign the rmiserver.csr and > rmiclient.csr. Export your CA public key(cacert.der) and the signed > rmiserver.der and rmiclient.der to specialpurpose/rmiclient/sslcert/. > 5. In specialpurpose/rmiclient/sslcert/, run importcerts.sh > 6. Run specialpurpose/rmiclient/build.xml, select target war. This will > produce an ofbizrmiclient.war under specialpurpose/rmiclient/build/. > 7. Deploy ofbizclient.war in tomcat. I use tomcat 5.5.26. I > 8. Config framework/base/config/ofbiz-containers.xml, change rmi-dispatcher > bound-host if you don't use localhost. > 9. If you run ofbiz with "ant run", edit {ofbiz_home}/build.xml, add > trustStore config: > <target name="run" depends="build"> > <java jar="ofbiz.jar" fork="true"> > <jvmarg value="${memory.max.param}"/> > <jvmarg > value="-Djavax.net.ssl.trustStore=${basedir}/framework/base/config/ofbiztrust.jks"/> > <jvmarg value="-Djavax.net.ssl.trustStorePassword=changeit"/> > </java> > </target> > 10. Rebuild and run ofbiz. > 11. If localhost is not your ofbiz server name, edit > {tomcat_home}/webapps/ofbizclient/index.jsp, change > OFBizRmiClient rc = new OFBizRmiClient("rmi://localhost:1099/RMIDispatcher"); > String ofbizUrl = "http://localhost:8080"; > accordingly. > 12. In web browser, type in your ofbizrmiclient address:. A correct result > should be similar to correct-result.png. > Trouble shootings: > 1. sun.security.validator.ValidatorException: No trusted certificate found > Edit {tomcat_home}/ofbizrmiclient/WEB-INF/classes/jsse.properties, modify the > trustStore and keyStore configuration. > 2. javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate > Check the server side trustStore configuration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.