My World of experiments with Technology

For publishing the WCF based web services on IIS 7.0, you need to have the Frontpage server extensions for IIS7.0. You can download the extension here: http://www.iis.net/community/default.aspx?tabid=34&g=6&i=1630 After the installation, visit the following site to extend the virtual server. http://test01:3610/fpadmdll.dll?page=fpadmin.htm P.S: The hostname and port may change in your case. You can also launch this adminstrator page by Start->All programs -> Administrative Tools -> Microsoft SharePoint Administrator which will open the Server Administration page. Once you are there, you can click "extend" to extend your virtual server. Please ensure that you are opening this internet browser as an Administrator. Otherwise you may receive the following error: Cannot create folder "_vti_pvt". iis7 You can open the IE as an administrator by selecting the option "Run as Administrator" on the context menu.

I have previously developed several web services in Netbeans 6.9 IDE with much ease and flexibility. But today when i launched Netbeans 6.9 today, it downloaded some updates by itself and all my existing web services were showing build errors. The following are couple of exceptions that i noted down: java.lang.ClassNotFoundException: There's no JAXB 2.2 API in the classpath C:\Projects\proj_name\nbproject\jaxws-build.xml:22: taskdef class com.sun.tools.ws.ant.WsImport cannot be found taskdef A class needed by class com.sun.tools.ws.ant.WsImport cannot be found: org/apache/tools/ant/taskdefs/MatchingTask While i kept on fixing one after another exception, here is the permanent fix that resolved all the issues: I had several Jars inside this directory: C:\Program Files\Java\jdk1.6.0_24\jre\lib\endorsed like webservices-api.jar, jaxb-api.jar, jaxws-api.jar, jaxb-xjc.jar, jaxws-tools-2.0.jar, jaxws-tools-2.1.4.jar. There was an existing issue that was raised here: http://j

While calling the Primavera API server from a remote client, i was getting this exception: com.primavera.integration.network.ServiceNotBoundException: rmi/RemoteSession at com.primavera.integration.network.RMIInstanceFactory.getRemoteInstance(RMIInstanceFactory.java:97) The default port 9099 is in listening mode on the API server. The API server is deployed on JBOSS applications server. After a careful study of the configuration and the admin guide, here is how i resolved this issue: 1. Unlike the previous versions, the RMI standard Service Port needs to be set explicitly to a valid port value if the RMI server is going to be access through a firewall. (If the server will be accessed across a firewall, you must set this to a specific port.) 2. This port must be different than RMI Registry port. You will use the Registry port in all your client side method calls. 3. Setup a inbound firewall rule for both these ports RMI Standard service port as well as RMI Registry port. 4.

If you want to add the SSL security to your web service (in Windows), please follow these steps: 1. Create a self-signed certificate on the server side using the "Keytool" utility found in your Java binary distribution. keytool -genkey -alias tomcatWSServer -keyalg RSA This will create a new file .keystore in the user's home directory. You can move it to your desired location. a. Please note that you should not enter your first name/last name, instead please enter the name of the server on which tomcat is running. The clients who will be validating the certificate will match the name of the server and the name on the certificate to verify the authenticity. b. Also they will be ensured that the request is coming from the same server as mentioned in the certificate to avoid phishing and other threats. c. Please use the same password for Certificate and the Keystore both. 2. Enable the HTTPS configuration in the tomcat's server.xml as shown below. Please note

I noticed the following exception in Tomcat logs: Commons Daemon procrun stdout initializedError occurred during initialization of VMjava/lang/NoClassDefFoundError: java/lang/Object Resolution: Go to C:\Program Files\Apache Software Foundation\Tomcat 6.0\bin and double click on tomcat6w.exe. This will open the Tomcat 6 properties. Go to Java tab and check the path for jvm.dll under Java Vitual machine textbox. This should be under the same JRE that is used for all other purposes like keystore, JAVA_HOME, etc. This fix should resolve the problem.