Configuring a Test Environment
Today I have to configure IBM ODM Events so that the SunJDK can send messages to it. There's a few steps. I'll be working mainly in the Rules Designer. Review the Part 1 of this Blog Post, which just shows how to get a JMS client talking to ODM in with the IBMJDK and part 2 which shows how to get the SunJDK configured properly.
I want to take a bit of a sidetrack, because in part 1 we assumed that you had ODM installed. If you installed the SamplesServer, then you're all set, you can ignore this part of the lab. In fact, if you didn't have something set up you never could have gotten the first lab to work, so this all might be moot.
Anyway, if you are developer I recommend that you install just the ODM SamplesServer and avoid the following steps only because they are unnecessarily complicated compared to just installing SamplesServer.
I installed ODM Events in a stand-alone server, by itself, without Rule Execution Server or Decision Center and without SamplesServer. I did that by choosing a custom install from the launchpad.
There are a few things that are not entirely clear the first time through a custom install. I tend to miss some important steps that are actually in the InfoCenter, but that's just me.
I installed with DB2 instead of Derby. The custom installer assumes that you already have DB2 installed and that you've created a database. I called mine ODMEVDB. A limited license DB2 comes with the product at the time of this writing.
You'll need to install WAS ND, eXtrme Scale, and optionally JDK 7.4. Install these into a package group called C:\IBM\WAS. Then install Events and Profile Templates into a new package group called C:\IBM\ODM. You can optionally install Decision Center DC and Decision Server DS at this point too.
Once that's done, go into the profile creation tool at C:\IBM\WAS\bin\profilemanagment\pmt. and create your IBM Decision Server Events profile. You might also optionally create a deployment manager, which you will have to augment with IBM Decision Server Events. But creating a cell and a cluster is beyond the scope of this series of labs.
Start the server and go into the admin console (http://localhost:9060 by default). Go into the websphere enterprise applications and check to make sure you have both the WBETesterEAR and EventWidgetsEar applications deployed. If they are not there you'll have to find them in the product binaries and deploy them as you would any other application. The installableApps should be located in the<ODM Install>\runtime folder.
To make these test widgets work you will need to add a testuser, a group, and set an administrative role. So go into the admin console / users and groups. Add a group, call it EventOperators. Add a user, call it testuser. Add the user to the group. Then under Administrative Group Roles, add the Operator Role to the EventAdministrator role. And make sure you click OK and Save your changes at each step.
Next, go into the WebSphere Enterprise Applications and map this user to the roles WBEAdmin, WBERestApiUser and EventWidget Users which are found in the two applications, wbetesterear and eventwidgetsear. Click OK and save, and restart those two apps.
Anyway, if you are developer I recommend that you install just the ODM SamplesServer and avoid the following steps only because they are unnecessarily complicated compared to just installing SamplesServer.
I installed ODM Events in a stand-alone server, by itself, without Rule Execution Server or Decision Center and without SamplesServer. I did that by choosing a custom install from the launchpad.
There are a few things that are not entirely clear the first time through a custom install. I tend to miss some important steps that are actually in the InfoCenter, but that's just me.
I installed with DB2 instead of Derby. The custom installer assumes that you already have DB2 installed and that you've created a database. I called mine ODMEVDB. A limited license DB2 comes with the product at the time of this writing.
You'll need to install WAS ND, eXtrme Scale, and optionally JDK 7.4. Install these into a package group called C:\IBM\WAS. Then install Events and Profile Templates into a new package group called C:\IBM\ODM. You can optionally install Decision Center DC and Decision Server DS at this point too.
Once that's done, go into the profile creation tool at C:\IBM\WAS\bin\profilemanagment\pmt. and create your IBM Decision Server Events profile. You might also optionally create a deployment manager, which you will have to augment with IBM Decision Server Events. But creating a cell and a cluster is beyond the scope of this series of labs.
Start the server and go into the admin console (http://localhost:9060 by default). Go into the websphere enterprise applications and check to make sure you have both the WBETesterEAR and EventWidgetsEar applications deployed. If they are not there you'll have to find them in the product binaries and deploy them as you would any other application. The installableApps should be located in the<ODM Install>\runtime folder.
To make these test widgets work you will need to add a testuser, a group, and set an administrative role. So go into the admin console / users and groups. Add a group, call it EventOperators. Add a user, call it testuser. Add the user to the group. Then under Administrative Group Roles, add the Operator Role to the EventAdministrator role. And make sure you click OK and Save your changes at each step.
Next, go into the WebSphere Enterprise Applications and map this user to the roles WBEAdmin, WBERestApiUser and EventWidget Users which are found in the two applications, wbetesterear and eventwidgetsear. Click OK and save, and restart those two apps.
At this point if you open a browser to http://localhost:9080/EventWidgets, it will ask you to log in. Go ahead and log in as the testuser and you should see three widgets, like these. If you don't see them, or if they have little yellow "caution signs" next to them, go back and review the authenticated users steps, making sure the test user is assigned to the proper role.
In part 4 we'll develop a simple Event Application and test it using these widgets.
No comments:
Post a Comment