August 19th, 2008 dan Posted in WebSphere Application Server, WebSphere Process Server No Comments »
The WebSphere Community Blog pointed out that there is a new WebSphere Application Server 7.0 Feature Pack available for download. This one will enable the Tuscany implementation of SCA inside the WebSphere Container.
It should be noted that this version of SCA is not the same one included in WebSphere Process Server. I would just assume that you can’t call a WPS 6.1 SCA Export from a WAS 7.0 SCA Import.
August 14th, 2008 syndication Posted in DeveloperWorks, WebSphere Process Server No Comments »
Draft Redbook, last updated: Thu, 14 Aug 2008 - Transition concepts and planning - Transition support and guidance - Transition examples This IBM® Redbook publication provides a guide on how to transition from your WebSphere® MQ Workflow 3.6 environment to WebSphere Process Server V6.1.
August 13th, 2008 syndication Posted in DeveloperWorks, WebSphere Integration Developer, WebSphere Process Server No Comments »
This article shows you how to build versions of business processes and human tasks that are based on best practices in IBM WebSphere Integration Developer V6.1 and WebSphere Process Server V6.1.Versioning of a Business Process is the most important feature of the BPEL Container, and likely the feature you know the least about. The choices you make in how to invoke parent-child processes define the way they behave when the BPEL templates are updated. If you wire them together in the assembly editor, then the two specific versions of the template are bound together forever. Parent process A v1.0 will always use Child Process B v1.0. If child B 2.0 is deployed, A will continue to use 1.0. Not exactly the behavior you would expect. This article defines the way that the BPEL engine resolves versions and it should be required reading.
August 13th, 2008 dan Posted in Oracle BPEL, WebSphere Process Server No Comments »
Right out of the gate in my experience with Oracle BPEL, I have to integrate with a non-SOAP HTTP service. Luckily, Lucas Jellema over on the AMIS Technology blog has a very well written article that goes end to end on exactly what you need to do in order to get Oracle and HTTP (REST) Get to play nicely with each other.
I’d also like to add that Oracle themselves include an example as well in the documentation in section “702.Bindings”.
If I was in WebSphere Integration Developer v6.0.2.x, I’d have to write the custom invocation logic myself.
In WebSphere Integration Developer v6.1.x I can use the HTTP Import Binding.
August 7th, 2008 syndication Posted in DeveloperWorks, WebSphere Process Server No Comments »
This article introduces you to techniques and patterns that you can use to develop personalized user interfaces for business processes. Although this article focuses on IBM WebSphere Process Server as the process engine, you can use most approaches and tools to create client applications for other process engines, for example, IBM Lotus Workflow and SAP Business Workflow.
August 7th, 2008 syndication Posted in WebSphere Integration Developer, WebSphere Process Server No Comments »
This article shows you how to design, develop, configure, deploy, and test an end-to-end purchase order scenario using WebSphere Process Server, WebSphere Adapters, and SAP. You also learn how to create applications that Web enable SAP services and help in the analysis, design, and implementation of similar integration applications.A nice scenario developed by IBM to show off how to use the WebSphere Adapter for SAP, WebSphere Process Server and WebSphere Integration Developer.
July 29th, 2008 dan Posted in WebSphere Integration Developer, WebSphere News, WebSphere Process Server No Comments »
Geez, I don’t know how I missed this one. ILOG is a business rules engine that can already integrate with WebSphere Process Server so this acquisition makes sense. It’s better than the one bundled with the product and used by more companies.
Anyway, I’ll defer to the bloggers of the world who have more industry insight than I to explain this acquisitions relevance:
July 29th, 2008 dan Posted in WebSphere Application Server, WebSphere Business Services Fabric, WebSphere Enterprise Service Bus, WebSphere Integration Developer, WebSphere Message Broker, WebSphere Process Server, WebSphere Service Registry and Repository 1 Comment »
Planning that new WebSphere Process Server v6.0 GA production deployment? I suggest you check out the End Of Service Dates published by IBM for your versions to ensure that you aren’t painting yourself into a corner before you even start. Beware clicking that last link, it’s a poorly created web page with every single IBM product and revision; the worlds longest HTML ever.
End of Marketing: IBM stops actively selling it to customers
End of Support: IBM stops answering the phone when you call to complain about it. Of course, you can always enter into an extended contract to continue support of mission critical installations.
Quick links:
WebSphere Integration Developer
I tried to get other quick links but it was too frustrating with all the product versions inlined together.
July 28th, 2008 syndication Posted in DeveloperWorks, WebSphere Enterprise Service Bus, WebSphere Process Server No Comments »
IBM WebSphere Process Server is a powerful runtime engine that can be used as the heart of a Service Oriented Architecture. It is built on WebSphere Application Server, and includes WebSphere ESB, enabling you to run integration modules created with WebSphere Application Developer, mediation modules, and J2EE applications. This article examines the features new to WebSphere Process Server V6.1.2. Basic knowledge of WebSphere Process Server is required for this article.Goes a step beyond the lis of features that I posted earlier with some user interface screenshots.
July 24th, 2008 dan Posted in WebSphere Application Server, WebSphere Process Server No Comments »
I have an SIBus destination called: ‘MY/QUEUE’.
I create a JMS QueueConnectionFactory and JMS Queue definition to this destination. jms/LoggingPoisonQueueCF and jms/LoggingPoisonQueue. When I attempt to put a message on the destination (using Spring JMS) I get the following exception:
org.springframework.jms.InvalidDestinationException: CWSIA0046E: The parameter queue://MY/QUEUE?busName=SIBJMSBus is from a foreign implementation that is not supported.; nestedexception is javax.jms.InvalidDestinationException: CWSIA0046E: The parameter queue://MY/QUEUE?busName=SIBJMSBus is from a foreign implementation that is not supported.; nested exception is javax.jms.JMSException: CWSIA0385E: It is not permitted for a destination URI to specify a queue manager, as found in URI : queue://MY/QUEUE?busName=SIBJMSBus at org.springframework.jms.support.JmsUtils. convertJmsAccessException(JmsUtils.java:261)
Digging deeper into the stack trace, the offending piece of code is found:
Caused by: javax.jms.JMSException: CWSIA0385E:
It is not permitted for a destination URI to specify a
queue manager, as found in URI :queue://My/Queue?busName=SCA.APPLICATION.widCell.Bus at com.ibm.ws.sib.api.jms.impl.URIDestinationCreator. processURI(URIDestinationCreator.java:476) at com.ibm.ws.sib.api.jms.impl.URIDestinationCreator. createDestinationFromString(URIDestinationCreator.java:285) at com.ibm.ws.sib.api.jms.impl.JmsFactoryFactoryImpl. createQueue(JmsFactoryFactoryImpl.java:523) at com.ibm.ws.sib.api.jms.impl.JmsDestinationImpl. checkNativeInstance(JmsDestinationImpl.java:707)
This URIDestinationCreator is interpreting the string as the format
queue://<queue manager>/<queue_name>?<busName>
I poked around in vain in the infocenter and I think I found the article that describes the issue. Basically what happens with a destination URI that is ambiguous like this one (Am I referring to a queue names ‘Queue’ on QueueManager ‘My’ , or am I referring to a queue called ‘My/Queue’) is that WebSphere will just toss an exception.
When I tried to see if slashes were used anywhere in WebSphere Process Server, I was surprised to find that they were in the SYSTEM bus. I also noticed that JMS isn’t used by much except the BPEL engine. When the BPEL engine uses it, they use ‘.’ to separate components. I assume it’s because they also ran into this exception.
The workaround is to just not use forward slashes. The secondary workaround is to create aliases for your SIBus destinations sans slash.
July 22nd, 2008 dan Posted in Oracle BPEL, WebSphere Process Server No Comments »
I spent a few days battling the oracle DBMS_CRYPTO package. This package allows the encryption of data types, including clobs and blobs (in oracle 10g). The battles included:
dbms_crypto.encrypt(
dst IN OUT NOCOPY BLOB,
src IN CLOB CHARACTER SET ANY_CS,
typ IN PLS_INTEGER, key IN RAW,
iv IN RAW DEFAULT NULL);To which I wrote:
outputBlob := dbms_crypto.encrypt
(outputBlob, myClob, myRawKey, myCryptoFormat, null)To which oracle told me:
Error(13,15): PLS-00306: wrong number
or types of arguments in call to 'ENCRYPT'".Now what is mischievous about this error is that it’s not actually the arguments of the function that are wrong, it’s the fact that I’m trying to set the output of the call back into outputBlob.
dbms_crypto.encrypt(outputBlob, myClob,
myRawKey, myCryptoType, null)Is the proper call. I wish that the compiler was better as telling me that. I’m assuming that because a parameter is an IN OUT I shouldn’t be trying to set the output value the way I was.
ORA-01405: fetched column value is NULLWhich basically said that the output BLOB needs to be initialized. I initialized the value to EMPTY_BLOB.
ORA-22275:invalid LOB locator specified"Apparently EMPTY_BLOB is no good. I google’d around for a while and found:
DBMS_LOB.CREATETEMPORARY(encrypt,true);And finally it worked and returned me an encrypted BLOB! Props to the power of the internet for providing the chain of solutions that got my stored procedure up and running.
July 21st, 2008 dan Posted in WebSphere Integration Developer, WebSphere Process Server No Comments »
I did not realize that the default log size of the test server installation of WebSphere Process Server inside of WebSphere Integration Developer was so small. It’s a single one megabyte file. This means that I don’t have all the spring exceptions that I thought I did.
I suggest anyone who wants to be able to have a log file thats worth anything go and increase these defaults. I use five 20MB files.
You can change it from the admin console via Logging and Tracing > server1 > JVM Logs.
July 17th, 2008 syndication Posted in Syndication, WebSphere Enterprise Service Bus, WebSphere Process Server No Comments »
Redpaper, published: Thu, 17 Jul 2008 This IBM® Redpaper publication explains how to configure IBM WebSphere® Process Server V6.1 to work with an Oracle® database.There's always a thin amount of documentation on integrating IBM products with non-DB2 databases. Here is a redpaper on using Oracle for WebSphere Process Server.
July 11th, 2008 syndication Posted in DeveloperWorks, Syndication, WebSphere Process Server No Comments »
Draft Redbook, last updated: Fri, 11 Jul 2008 - Migration of WebSphere InterChange Server and WBI Adapters - Architectural usage patterns and migration planning - Migration tools, technical examples and scenarios IBM® WebSphere® Process Server is the next generation business process integration server that has evolved from proven business integration concepts, application server technologies, and the latest open standards.WICS was the precursor product to WebSphere Process Server. I know there are still a lot of WICS users out there looking to migrate.
July 7th, 2008 dan Posted in WebSphere Enterprise Service Bus, WebSphere Integration Developer, WebSphere Process Server 2 Comments »
The ability to roll back a update is a nifty idea. The theory is that you installed something that broke your platform. You can now just ‘undo’ the install.
In practice, it’s a feature that next to nobody uses. It requires a deep-faith in the programmers of the rollback logic to return the system to it’s initial state. If they missed a single file or java class, it could land up affecting the entire system. The user is then left with a question “Is the environment broken or is there a bug in the platform?”. In order to resolve this question, they will uninstall and re-install the product.
Therefore, if you know that you will never bother to rollback, why are you dedicating disk space for the installation manager to rollback? Yup, that’s the default setting. Every old version of every plugin in every product you’ve ever installed is still there needlessly. For people like me who work in virtual machines, disk space is precious.
You can turn this open off by clicking File -> Preferences.
You can turn off the check box to preclude future saving. You can also click the Delete saved Files button to remove any current old versions.
Before I clicked the button, it told me I had 1.6G of files saved.