Changing servers for business rules deployment

In our migration to webmethods 8 we changed server names as we have 7 and 8 running concurrently in dev.

In order to deploy our business rules to the integration server, I loaded them into Blaze 6.8, but I didn't see a way to change the server.  Searching the files in the repository while blaze was closed revealed 2 places where the hostname and connection info is stored in plain text:
<Project Name>

  <instance ref='IS Host'>
   <instance ref='value'>
    <value>hostname</value>
   </instance>

<Project Name>.innovator_attbs

 managementProperty.IS\ Host=hostname

That worked, then I had to regenerate my business object model from IS.  The object hadn't changed, but would not sync up.  After regenerating it deployed fine.

Migration to Webmethods 8 - more info

Found this guide while searching about:

http://www.scribd.com/doc/35935457/8-x-Web-Methods-Upgrade-Guide

Handling CSV files

We were interfacing to external vendor who had a CSV restful interface.  I had built a system for creating and parsing the xml files.  Then my co-worker reminded me about the built in flat file handling routines.  Duh!

1. Create a flat file dictionary with all the different cvs formats you will need.
2. Then create a flat file schema for each transaction (referencing the object in the dictionary).
3. Create a document definition from the schema
4. Take the csv data and send it to pub.flatFile:convertToValues.  Send in the appropriate schema into the ffSchema entry on the service input.  (You can just copy the schema from the navigator and paste it into the value for ffSchema).
5. map ffValues to a document reference list of the document you created in step 3.

It was easy and straightforward and it handles all the parsing for you.

Migration to Webmethods 8

Based on errors we were having in 7.1.3 (we think our install was corrupt) we finally decided to migrate to 8.

Here's what we've done so far.

1. Installed and configured IS8 and MWS8.
2. Installed JDBC drivers
3. Exported all the IS Packages we wanted to keep from 7 and placed in replicate/inbound on IS 8 and installed them from there.
4. Copied properties files from 7 to 8
5. Setup all existing scheduled tasks
6. Synced all the publishable documents in the WM8 broker
7. Set the permissions for all our web service connectors to Anonymous (it seemed to revert to the default when installed from the inbound directory).
8. Created all the web service consumer aliases.

This got IS up and running and it seems fine.  We still need to regression test it, but all the packages passed basic tests.


Then I moved on to deploying our process models from WM7 into WM8.  When I opened the projects I had to change the jre from 150 to 160.  I also had to fix a couple library issues.  (We didn't want to try and deploy the process models directly into 8 as we have had numerous problems with them, so we wanted to start from scratch on them.)

I also created a new process.  This process is working fine in MWS8.  The ported processes are getting a null pointer exception on the task interface.  I'm still investigating that. 

But so far, the IS upgrade was pretty smooth.  The MWS upgrade is still taking some time.  More on that later.

Sending high priority emails

Use PSUtilities.email.smtp (instead of pub.client.smtp) and set priority = 1.

Hashtable/Hashmap

Wow, you would think this would score higher on google searches, but after several pages of results I finally found PSUtilities.hashtable.   I was going to write up something or try and find a clever way to build a document so it looked like a hashmap.  Glad I didn't waste that time but it sure wasn't easy to find!

Changing connections for an existing JDBC adapter

So you have your adapter setup with all 40 fields mapped and the 2 table join with a nice complex where clause.  Now you find out you need to use a different connection for whatever reason.  If you don't know, it looks like you have to delete and recreate your adapter.  There isn't anywhere in the adapter to change the connection.

Enter the WmART package.
For each adapter service, call pub.art.service:setAdapterServiceNodeConnection.  Pass in the serviceName (copy and paste from the navigator) and the new connection alias name.  Now the adapter will point to the new connection alias!