http://www.davismol.net/2014/08/31/installing-the-jdk-on-a-windows-machine-without-administrator-privileges/
Monday, April 4, 2016
Sunday, February 14, 2016
Excel: Difference of data in 2 columns
| G | A | G |
| H | D | H |
| E | E | |
| B | C | |
| X | B | X |
| Y | Y | |
| Z | Z |
=IF(ISERROR(VLOOKUP(A1,B:B,1,FALSE)),A1,"")
Monday, January 18, 2016
Java: WSDL to JAR
<?xml version="1.0" encoding="UTF-8"?>
<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/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>weatherForecast</groupId>
<artifactId>sample-ws-client</artifactId>
<version>0.0.1-SNAPSHOT</version>
<name>WeatherForecast Service</name>
<packaging>jar</packaging>
<properties>
<cxf.version>3.0.4</cxf.version>
</properties>
<build>
<!-- maven compiler plug-ins -->
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.2</version>
<configuration>
<source>1.7</source>
<target>1.7</target>
</configuration>
</plugin>
<!-- maven wsdl2java plug-ins -->
<plugin>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-codegen-plugin</artifactId>
<version>${cxf.version}</version>
<executions>
<execution>
<id>generate-sources</id>
<phase>generate-sources</phase>
<configuration>
<sourceRoot>${project.build.directory}/generated/cxf</sourceRoot>
<wsdlOptions>
<wsdlOption>
<wsdl>http://www.webservicex.net/WeatherForecast.asmx?WSDL</wsdl>
</wsdlOption>
</wsdlOptions>
</configuration>
<goals>
<goal>wsdl2java</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-frontend-jaxws</artifactId>
<version>${cxf.version}</version>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-transports-http</artifactId>
<version>${cxf.version}</version>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.12</version>
</dependency>
</dependencies>
</project>
mvn package
Thursday, October 29, 2015
SOAPUI issue when configured with certificates
Comment the following line in <soapUI installation location>/jre/lib/security/java.security File
jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024
jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024
Monday, October 26, 2015
UCM: GET_SEARCH_RESULTS using RIDC
import java.io.IOException;
import oracle.stellent.ridc.IdcClient;
import oracle.stellent.ridc.IdcClientException;
import oracle.stellent.ridc.IdcClientManager;
import oracle.stellent.ridc.IdcContext;
import oracle.stellent.ridc.model.DataBinder;
import oracle.stellent.ridc.model.DataObject;
import oracle.stellent.ridc.model.DataResultSet;
import oracle.stellent.ridc.model.serialize.HdaBinderSerializer;
import oracle.stellent.ridc.protocol.ServiceResponse;
public class TestRIDCSearch {
public static void main(String[] args) {
IdcClientManager manager = new IdcClientManager();
try {
IdcClient idcClient = manager.createClient("idc://localhost:4444");
IdcContext userContext = new IdcContext("sysadmin");
HdaBinderSerializer serializer = new HdaBinderSerializer("UTF-8", idcClient.getDataFactory());
DataBinder dataBinder = idcClient.createBinder();
dataBinder.putLocal("IdcService", "GET_SEARCH_RESULTS");
/*The easiest way to figure out the QueryText expected by the content server is to execute the query using the content server search screen
in the native UI and trace that call. Gather full verbose, system audit trace using the following trace sections:
system, requestaudit, searchquery, searchcache
This should be the following output:
>searchquery/6 03.25 14:24:41.285 IdcServer-826 preparedQueryText: ( dDocName `test` dSecurityGroup `Public` dInDate >= `3/25/15 12:00 AM` )*/
/*NOTE: UCM limits the ResultCount value according to the MaxResults configuration setting for Content Server.
* To increase the MaxResults setting, add the setting MaxResults=<integer> in config.cfg*/
dataBinder.putLocal("QueryText", "dDocName `test` dSecurityGroup `Public` dInDate >= `3/25/15 12:00 AM`");
serializer.serializeBinder(System.out, dataBinder);
ServiceResponse response = idcClient.sendRequest(userContext, dataBinder);
DataBinder responseData = response.getResponseAsBinder();
serializer.serializeBinder(System.out, responseData);
DataResultSet resultSet = responseData.getResultSet("SearchResults");
for (DataObject dataObject : resultSet.getRows()) {
System.out.println("Title is: " + dataObject.get("dDocTitle"));
}
} catch (IdcClientException ice) {
ice.printStackTrace();
} catch (IOException ioe) {
ioe.printStackTrace();
}
}
}
Installation of multiple versions of JDeveloper
Navigate to <Installation_Folder>\jdeveloper\jdev\bin\jdev.boot file.
Locate the ide.user.dir property and change it to something like this:
ide.user.dir= C:/JDev11117SOADefaultDomain
Locate the ide.user.dir property and change it to something like this:
ide.user.dir= C:/JDev11117SOADefaultDomain
Friday, October 9, 2015
Prerequisites before SOA Development
Creation of JMS Queue
Queue: Defines a point-to-point destination type, which are used for asynchronous peer communications. A message delivered to a queue is distributed to only one consumer.
Click SOAJMSModule.
In the Summary of Resources table, click New. Select the resource type: Queue and click Next.
Enter name: demoFulfillmentQueue and JNDI name: jms/demoFulfillmentQueue
Select Subdeployment SOASubDeployment. Select JMS Server SOAJMSServer
Creation of Connection Factory
Connection Factory: Defines a set of connection configuration parameters that are used to create connections for JMS clients.
Select the resource type: Connection Factory and click Next
Enter name: demoCF and JNDI name: jms/demoCF.
You should see both the queue and the connection factory listed in the Summary of Resources as shown here.
Now add the connection pool. The connection pool is configured in the JMSAdapter application and uses a Deployment Plan. First, create a directory to contain that plan.
Create a directory JMSPlan: C:\Oracle\Oracle_SOA1\soa\JMSPlan
Click Deployments. Click JMS Adapter. Click the Configuration tab and then the Outbound Connection Pools tab.
Click New. Select the factory oracle.tip.adapter.jms.IJmsConnectionFactory. Click Next. Enter eis/Queue/demo.
Click on eis/Queue/demo. Change the property ConnectionFactoryLocation to value jms/demoCF. Now update the JMSAdapter adapter.
=====================================================================
Create a data source with name as soademoDatabase, and JNDI Name as jdbc/soademoDatabase
Create a directory DBPlan: C:\Oracle\Oracle_SOA1\soa\DBPlan
Click Deployments. Click DbAdapter. Click the Configuration tab and then the Outbound Connection Pools tab.
Enter the JNDI Name as follows: eis/DB/soademoDatabase
Edit the connection pool to reference the data source. You have created a connection pool.
Queue: Defines a point-to-point destination type, which are used for asynchronous peer communications. A message delivered to a queue is distributed to only one consumer.
Click SOAJMSModule.
In the Summary of Resources table, click New. Select the resource type: Queue and click Next.
Enter name: demoFulfillmentQueue and JNDI name: jms/demoFulfillmentQueue
Select Subdeployment SOASubDeployment. Select JMS Server SOAJMSServer
Creation of Connection Factory
Connection Factory: Defines a set of connection configuration parameters that are used to create connections for JMS clients.
Select the resource type: Connection Factory and click Next
Enter name: demoCF and JNDI name: jms/demoCF.
You should see both the queue and the connection factory listed in the Summary of Resources as shown here.
Now add the connection pool. The connection pool is configured in the JMSAdapter application and uses a Deployment Plan. First, create a directory to contain that plan.
Create a directory JMSPlan: C:\Oracle\Oracle_SOA1\soa\JMSPlan
Click Deployments. Click JMS Adapter. Click the Configuration tab and then the Outbound Connection Pools tab.
Click New. Select the factory oracle.tip.adapter.jms.IJmsConnectionFactory. Click Next. Enter eis/Queue/demo.
Click on eis/Queue/demo. Change the property ConnectionFactoryLocation to value jms/demoCF. Now update the JMSAdapter adapter.
=====================================================================
Create a data source with name as soademoDatabase, and JNDI Name as jdbc/soademoDatabase
Create a directory DBPlan: C:\Oracle\Oracle_SOA1\soa\DBPlan
Click Deployments. Click DbAdapter. Click the Configuration tab and then the Outbound Connection Pools tab.
Enter the JNDI Name as follows: eis/DB/soademoDatabase
Edit the connection pool to reference the data source. You have created a connection pool.
Subscribe to:
Posts (Atom)




