Soon after posting 'Part 3 – Enable Transport System on Netweaver 7.01 Trial' I went on to configure my Workflow Engine and realised that it had a very similar problem as the transport system had - For some reason this version of Netweaver is set up with the host name specified as PWDF3101 by default - This causes all sorts of complications, one of which I dealt with in the previous part of this series, and another here. The problem that this incorrect system configuration causes, is that when we run the automatic workflow customisation, it is unable to create an RFC destination for the workflow system. After a lot of digging, I found that to fix the problem you have to do the following:

Run transaction RZ04 - Double click on the "DUMMY Self-Configured Operation Mode" line. Click once on the line (probably the only one) that contains the incorrect host name. Now click on the "Delete Instance" icon. Confirm when asked if you want to delete all the instance data. Now go to the "Settings->Based on Current Status->New Instances->Generate" menu item. Click the save button, and you are done.

Ok now you have gotten the hard work done - on to the easy part!

It's actually very simple - Everything you need to do has been nicely packaged into transaction SWU3. If you go there, you will see a whole lot of red crosses indicating that the configuration has not been done. In the transaction, you will see 5 top level nodes:

• Maintain Runtime Environment
• Maintain Definition Environment
• Maintain Additional Settings and Services
• Classify Tasks as General
• Guided Procedures

All you have to do is highlight each node, and then click on the "Perform Automatic Workflow Customizing" button or press F9. As you go through this, you will notice that most of the red crosses turn into green checks. If any of them do not change from the red cross, you can simply highlight the individual offender to see the corresponding documentation on the right side of the screen. There are a few items that need to be manually process like "Maintain Prefix Numbers" and some others. Then there are some of the entries that you don't need to get to a green check because, for instance, you won't have a J2EE server for "Maintain Guided Procedures Gateway".

Just go through all the entries to make sure that they are configured, or confirm that you don't need to configure them. As mentioned earlier, the documentation for each entry is listed on the right side of the screen and it is extremely helpful in guiding you through problems.

Once you are done you can click on the "Start Verification Workflow (F5)" button. If the system asks you to activate event linkage, say yes. If need be, enter transport details. It will then tell you "Verification workflow started":

1. Go to the Business Workplace.

You will find a user decision work item in your workflow inbox.

2. Execute this work item and select a decision.

You receive two mails. These are the notifications of completion for this user decision and the subsequent background step.

You should now have successfully tested the workflow environment - If all went well then you have set everything up correctly, and you can begin to develop and test your own custom or SAP delivered workflows.

Series

Part 1 gives general tips for running SAP Netweaver Trial

Part 2 tells you how to access your Netweaver trial at home from anywhere

Part 3 talks about how to enable the transport system in Netweaver 7.01

Part 4 shows how to set up the workflow engine