http://ostechnix.wordpress.com/2013/01/28/setup-ftp-server-step-by-step-in-centos-6-x-rhel-6-x-scientific-linux-6-x/
I also set the vsftpd.conf variable ftp_user=myusername, so that anon logins go to my root. And I turn off ftp when I'm not using it so that nobody anons into my instance and messes with it.
Tuesday, November 19, 2013
Monday, November 18, 2013
Creating and mounting a volume on EC2
First, using the EC2 Managment Console, create a new volume, making sure it is in the same region/geo as the instance you want to attach to. When it is created attach it to your instance using the management console.
Then use the following linux commands to format the volume and mount it:
1. Use the following command to format and create a ext3 volume.
Then use the following linux commands to format the volume and mount it:
1. Use the following command to format and create a ext3 volume.
sudo mkfs -t ext3device_name- Use the following command to create the directory.
$sudo mkdirvolume_name - Use the following command to mount the volume.
$sudo mountdevice_namevolume_name
Thursday, September 19, 2013
IBM ODM Events on SUN JDK (part 5)
Just a quick note, that if your JMS server is remote, you'll need to add a line to the connection factory configuration stating where the to find the messaging transport, otherwise it will return localhost to your client, which would make it sad. Check the ports in the admin console first...
for secure messaging - hostname.domainname:7387:BootstrapSecureMessaging
for insecure messaging :) - hostname.domainname:7267:BootstrapDefaultMessaging
for secure messaging - hostname.domainname:7387:BootstrapSecureMessaging
for insecure messaging :) - hostname.domainname:7267:BootstrapDefaultMessaging
Wednesday, September 18, 2013
Linux Skills
In the almost 40 years I've been doing this I've never had to mount a drive on a linux box... When working with EC2 it's a life skill...
As sudo you can mount a volume with a command like this:
mkdir /mnt/vol
mount -t auto /dev/xvdj /mnt/vol
This attaches the drive device to the mount volume, where it can be browse as a folder.
umount /mnt/vol unmounts it
As sudo you can mount a volume with a command like this:
mkdir /mnt/vol
mount -t auto /dev/xvdj /mnt/vol
This attaches the drive device to the mount volume, where it can be browse as a folder.
umount /mnt/vol unmounts it
Monday, September 16, 2013
Amazon EC2 and WebSphere Application Server
It's my first day using Amazon EC2 and it's incredibly easy to set up a server. But there are some things you need to understand about how it assigns IP Addresses and Machine Names before you go about installing WebSphere Application Server.
A well known, and to many of us, confusing aspect of EC2 is that every time you reboot your server the hostname and IP address will change. That's bad. Or at least it's bad for WebSphere.
WebSphere embeds its hostname in its cell configuration. If the hostname changes, the WebSphere cannot start. In other words, WebSphere needs a static hostname. So, we must find some way to work around this EC2 Feature. Here's the steps I took.
First, I signed up for domain name server external to EC2. I chose godaddy.com, but I've used others in the past. After paying $2.99 for the name ibmbpmatwork.info for a year.
Then I got an EC2 account and set up a 64 bit RHEL server with about 20 GB. Apparently that can still be a free micro server. Opened ports for WebSphere 9080/9060/9043 and 9443, and FTP (20, 21) and SSH(22) by creating an EC2 Security Group and assigning it to my image. Then I opened the same ports on RHEL using the following command for each port I wanted open: sudo lokkit -p 20:tcp
Then I set up an Elastic IP or EIP, which is a fixed externally facing IP address. An EIP *should* provide you with a static internal and external IP address that never change.
Then I went back to GoDaddy and set the IP address against the host name I just configured there.
Optional - I can set the hostname to my own naming convention by doing the following steps, otherwise I have to use the internal hostname that Amazon assigns:
Back in the RHEL image I added one line to the /etc/rc.local file that looked something like this
/bin/hostname -F /etc/hostname
And I created a /etc/hostname file with the fully qualified name in it.
updated 11/15/2013-->
Alternatively you can just edit /etc/sysconfig/network and set HOSTNAME=my.hostname.com and then restart. I was working with a client today and we could not make the rc.local approach work for some reason. But changing the /etc/sysconfig/network file worked perfectly.
<<-
I checked to make sure the image could resolve my fully qualified host name.
After that, I want to restart and make sure the hostname got set properly.
Then I installed FTP by doing a sudo yum install vsftpd
and started it by calling sudo /etc/init.d/vsftpd restart
Next, I uploaded the WAS zip files to a downloads directory and unzipped them. I also got the 32 bit Installation Manger v1.7 from the IBM site, unzipped it
Now, because I'm using WAS Express, which is 32 bit, I need to install some 32bit libraries into linux as explained here: http://www-01.ibm.com/support/docview.wss?uid=swg21459143
Next, I did a silent install using the sudo installc -acceptLicense -log log.xml command.
Then install WAS from /opt/IBM/InstallationManager/eclipse/tools, run the imcl command as sudo, pointing to the repository where I unzipped the WAS binaries. Something like this:
sudo ./imcl install com.ibm.websphere.EXPRESS.v85_8.5.0.20120501_1108 -repositories /home/ec2-user/WAS/ -acceptLicense
Then just create a default profile from the bin directory:
[ec2-user@ec2demo2 bin]$ sudo ./manageprofiles.sh -create -profileName First -adminUserName admin -adminPassword admin -tempatePath /opt/IBM/WebSphere/AppServer/profileTemplates/default -isDefault
A well known, and to many of us, confusing aspect of EC2 is that every time you reboot your server the hostname and IP address will change. That's bad. Or at least it's bad for WebSphere.
WebSphere embeds its hostname in its cell configuration. If the hostname changes, the WebSphere cannot start. In other words, WebSphere needs a static hostname. So, we must find some way to work around this EC2 Feature. Here's the steps I took.
First, I signed up for domain name server external to EC2. I chose godaddy.com, but I've used others in the past. After paying $2.99 for the name ibmbpmatwork.info for a year.
Then I got an EC2 account and set up a 64 bit RHEL server with about 20 GB. Apparently that can still be a free micro server. Opened ports for WebSphere 9080/9060/9043 and 9443, and FTP (20, 21) and SSH(22) by creating an EC2 Security Group and assigning it to my image. Then I opened the same ports on RHEL using the following command for each port I wanted open: sudo lokkit -p 20:tcp
Then I set up an Elastic IP or EIP, which is a fixed externally facing IP address. An EIP *should* provide you with a static internal and external IP address that never change.
Then I went back to GoDaddy and set the IP address against the host name I just configured there.
Optional - I can set the hostname to my own naming convention by doing the following steps, otherwise I have to use the internal hostname that Amazon assigns:
Back in the RHEL image I added one line to the /etc/rc.local file that looked something like this
/bin/hostname -F /etc/hostname
And I created a /etc/hostname file with the fully qualified name in it.
updated 11/15/2013-->
Alternatively you can just edit /etc/sysconfig/network and set HOSTNAME=my.hostname.com and then restart. I was working with a client today and we could not make the rc.local approach work for some reason. But changing the /etc/sysconfig/network file worked perfectly.
<<-
I checked to make sure the image could resolve my fully qualified host name.
After that, I want to restart and make sure the hostname got set properly.
Then I installed FTP by doing a sudo yum install vsftpd
and started it by calling sudo /etc/init.d/vsftpd restart
Next, I uploaded the WAS zip files to a downloads directory and unzipped them. I also got the 32 bit Installation Manger v1.7 from the IBM site, unzipped it
Now, because I'm using WAS Express, which is 32 bit, I need to install some 32bit libraries into linux as explained here: http://www-01.ibm.com/support/docview.wss?uid=swg21459143
Next, I did a silent install using the sudo installc -acceptLicense -log log.xml command.
Then install WAS from /opt/IBM/InstallationManager/eclipse/tools, run the imcl command as sudo, pointing to the repository where I unzipped the WAS binaries. Something like this:
sudo ./imcl install com.ibm.websphere.EXPRESS.v85_8.5.0.20120501_1108 -repositories /home/ec2-user/WAS/ -acceptLicense
Then just create a default profile from the bin directory:
[ec2-user@ec2demo2 bin]$ sudo ./manageprofiles.sh -create -profileName First -adminUserName admin -adminPassword admin -tempatePath /opt/IBM/WebSphere/AppServer/profileTemplates/default -isDefault
And then start server1 from the bin directory of the profiles/First folder and wait for that to finish.
That should do it.
That should do it.
Wednesday, September 11, 2013
IBM BPM Wiki
I wish I'd known about this earlier...
http://bpmwiki.blueworkslive.com
It contains the Neal Kolban toolkit for IBM BPM...
http://bpmwiki.blueworkslive.com/display/commwiki/The+KolbanTK+Toolkit
The demos are hidden. Search for the keyword "distribution"
http://bpmwiki.blueworkslive.com
It contains the Neal Kolban toolkit for IBM BPM...
http://bpmwiki.blueworkslive.com/display/commwiki/The+KolbanTK+Toolkit
The demos are hidden. Search for the keyword "distribution"
BPM 8.0.1 Developer's Environment SQL1092N during install
My install failed with the following error message:
SQL1092N "A166249" does not have the authority to perform the requested command or operation.
If your machine is locked down due to IT security policy, even though you have admin rights, you might not have complete rights. Here is the trick: Create a local admin account on the machine (iidadmin account). Log in with that account and run Installation Manager with the right-click option of “Run as administrator”.
SQL1092N "A166249" does not have the authority to perform the requested command or operation.
If your machine is locked down due to IT security policy, even though you have admin rights, you might not have complete rights. Here is the trick: Create a local admin account on the machine (iidadmin account). Log in with that account and run Installation Manager with the right-click option of “Run as administrator”.
There are articles in IBM support covering this as well, for example:
Monday, August 19, 2013
A Very Simple ODM Events Project (Part 4)
Today we're going to write, as simply as possible, an events project that takes a customerID and a value, runs a rule against them, and if the rule fires it will trigger an action, writing a file to a folder on the hard drive.
So go ahead and start Event Designer. I've created a new Event Project called DeveloperHat01, and then right clicked in and selected create new Event. I'm going to click next and name my event CustomerValueEvent and then click finish. I am not going to assign a connector to this event.
Next I'm going to create an event object. This will represent the incoming data elements. I will call it CustomerValueEO. Right there in the Event definition click Add. Make it a blank Event Object. Name it.
And as I drill down into it this event object, I'll add a customerID <string> and value <Integer> That takes care of defining an Event.
Next I'm going to create a Business Object that contains the same information as the Event Object. The Business Object will have verbalizations so that we can write rules against it. So right click in the project, select New... Business Object. Name it CustomerValueBO. Click Next. Select Create Business Object with the same fields as an event object. Click next, and then select the CustomerEventEO as shown below and click Finish.
Now let's create an Action so that when a rule triggers something will happen. Right click in the project and select New... Action.
Create a blank action. Click next. Name it CustomerValueAction. Click next. and select the File System connector so that it will write to the file system when our rule gets triggered. And then just as we did when creating the Event Object we'll create a new Action Object. Call it CustomerValueAO and give it two fields just like before called CustomerID and Value.
Here's where action objects are different than event objects. We have to tell Action Objects where to get their data from. So for each of the fields, go ahead and map them to the fields in the Business Object.
Now, because we've defined a file system connector for this Action, we'll need to tell it where to write to. We do that by selecting the Connector Tab, and setting the file path and filename pattern. In this case c:/temp and *.xml will work for us.
Next we're going to define a Event Rule. Right Click in the project and select New... Event Rule. Name it CustomerValueRule01, click Next. Have it trigger when the customerValueEvent is detected, click next. Have it use the System Context. The context is what holds the event correlation information. Click Next. And let's have it correlate against the CustomerID.
The content of the rule will say:
if the value of the customerValueBO is more than 10 then customerValueAction ;
So quite simply, if any events come in that have a customer value > 10 we will trigger our output Action. There is a lot more we could do with events that would make them more meaningful, but for now let's just test this one just to show how they work.
So now we want to deploy this project to the Events Server. Right Click on the project. Select Deploy... All Assets... and provide the server information. For a default ODM / Sample Server install this might be localhost, 9080, admin, admin and http protocol. Click Finish. You might have to enter another password at this point.
In a minute you'll see a dialog that says, Successful Deployment to Runtime.
Now we can open a Web Browser to our test widgets. http://localhost:9080/EventWidgets Log in as your test user, which might be admin / admin if you did the default install of SamplesServer. You should see a screen similar to this one. If you do not, then you might want to review Part 3 of this Lab. You've either logged in as a user that does not have test privileges or you do not have the one or more of the Test Widget Ear files installed or some combination of these:
Click on the Event Tester Widget. And from there click on Select Event Template. Select the CustomerValueEvent and click OK. Enter a customerID of 1 and a value of 1. Go ahead and click Send Event. Then look at the filters tab. You'll see that we received a CustomerValue Event. But if you check the actions tab, nothing will have fired. Go back to the first tab. Do this again with a customerID of 2 and a value of 20 and you should see different results in the actions tab.
And in fact if we open a file browser to the c:\temp folder we will find an xml file with a long name and the following content, which shows that we've written a WBE version 6.2 Connector Bundle, showing the customer value and customer ID.
<?xml version="1.1" encoding="UTF-8"?>
<connector xmlns="http://wbe.ibm.com/6.2/Action/CustomerValueAction" name="WBE" version="6.2">
<connector-bundle id="357B93DB17A280095B11E3C602377689" name="CustomerValueAction" stream="2" type="Action" workflow="FACE">
<CustomerValueAO>
<Value type="Integer">20</Value>
<CustomerID type="String">2</CustomerID>
</CustomerValueAO>
</connector-bundle>
<system>Base-Win2k8x64</system>
<timestamp>2013-08-20T01:46:27.368-04:00</timestamp>
<loginfo>This is an action from Decision Server</loginfo>
</connector>
In the next lab we will write an event packet directly to the JMS bus in the ODM Events Server and get a similar result.
So go ahead and start Event Designer. I've created a new Event Project called DeveloperHat01, and then right clicked in and selected create new Event. I'm going to click next and name my event CustomerValueEvent and then click finish. I am not going to assign a connector to this event.
Next I'm going to create a Business Object that contains the same information as the Event Object. The Business Object will have verbalizations so that we can write rules against it. So right click in the project, select New... Business Object. Name it CustomerValueBO. Click Next. Select Create Business Object with the same fields as an event object. Click next, and then select the CustomerEventEO as shown below and click Finish.
Now let's create an Action so that when a rule triggers something will happen. Right click in the project and select New... Action.
Create a blank action. Click next. Name it CustomerValueAction. Click next. and select the File System connector so that it will write to the file system when our rule gets triggered. And then just as we did when creating the Event Object we'll create a new Action Object. Call it CustomerValueAO and give it two fields just like before called CustomerID and Value.
Here's where action objects are different than event objects. We have to tell Action Objects where to get their data from. So for each of the fields, go ahead and map them to the fields in the Business Object.
Now, because we've defined a file system connector for this Action, we'll need to tell it where to write to. We do that by selecting the Connector Tab, and setting the file path and filename pattern. In this case c:/temp and *.xml will work for us.
Next we're going to define a Event Rule. Right Click in the project and select New... Event Rule. Name it CustomerValueRule01, click Next. Have it trigger when the customerValueEvent is detected, click next. Have it use the System Context. The context is what holds the event correlation information. Click Next. And let's have it correlate against the CustomerID.
The content of the rule will say:
if the value of the customerValueBO is more than 10 then customerValueAction ;
So quite simply, if any events come in that have a customer value > 10 we will trigger our output Action. There is a lot more we could do with events that would make them more meaningful, but for now let's just test this one just to show how they work.
So now we want to deploy this project to the Events Server. Right Click on the project. Select Deploy... All Assets... and provide the server information. For a default ODM / Sample Server install this might be localhost, 9080, admin, admin and http protocol. Click Finish. You might have to enter another password at this point.
In a minute you'll see a dialog that says, Successful Deployment to Runtime.
Now we can open a Web Browser to our test widgets. http://localhost:9080/EventWidgets Log in as your test user, which might be admin / admin if you did the default install of SamplesServer. You should see a screen similar to this one. If you do not, then you might want to review Part 3 of this Lab. You've either logged in as a user that does not have test privileges or you do not have the one or more of the Test Widget Ear files installed or some combination of these:
Click on the Event Tester Widget. And from there click on Select Event Template. Select the CustomerValueEvent and click OK. Enter a customerID of 1 and a value of 1. Go ahead and click Send Event. Then look at the filters tab. You'll see that we received a CustomerValue Event. But if you check the actions tab, nothing will have fired. Go back to the first tab. Do this again with a customerID of 2 and a value of 20 and you should see different results in the actions tab.
And in fact if we open a file browser to the c:\temp folder we will find an xml file with a long name and the following content, which shows that we've written a WBE version 6.2 Connector Bundle, showing the customer value and customer ID.
<?xml version="1.1" encoding="UTF-8"?>
<connector xmlns="http://wbe.ibm.com/6.2/Action/CustomerValueAction" name="WBE" version="6.2">
<connector-bundle id="357B93DB17A280095B11E3C602377689" name="CustomerValueAction" stream="2" type="Action" workflow="FACE">
<CustomerValueAO>
<Value type="Integer">20</Value>
<CustomerID type="String">2</CustomerID>
</CustomerValueAO>
</connector-bundle>
<system>Base-Win2k8x64</system>
<timestamp>2013-08-20T01:46:27.368-04:00</timestamp>
<loginfo>This is an action from Decision Server</loginfo>
</connector>
In the next lab we will write an event packet directly to the JMS bus in the ODM Events Server and get a similar result.
IBM ODM Events from Sun JDK (Part 3)
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.
Friday, August 16, 2013
IBM ODM Events from Sun JDK (Part 2)
Configuring a Sun JMS client to talk to WAS ...
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.
Sun works with the JKS formatted trust and store files, although you can probably get it to work with the p12 formatted files, I find that converting them over to JKS is the simplest.
Go to your <ODM INSTALL>/bin directory and start ikeyman. From there open the trust.p12 file. The default password is WebAS. And then just save it as trust.jks in the jks format with the same password. And also do the same for your key.p12 file saving it as key.jks in the jks format.
Now, in Eclipse, copy the security configuration folder that we created in Part 1 and name it SunJDKSecurity.
Edit the ssl.client.props file and change the user.root to point to your current project/SunJDKSecurity folder. To do this right click on the project security folder that you created and select properties. This will give you the full path to the folder. Highlight the path and use ctrl-c to copy. Then ctrl-s to save the file.
In addition you will have to replace some of the IBMJSSE settings with SunJSSE settings in this file. make the following edits. The big change is modifying the certifcates from .p12 to .jks format. We'll do that in the next step.
Check that you edited the sas.client.props file and set the following, which you would have done in the part 1 of this Blog)
com.ibm.CORBA.securityServerPort to your correct port, by default it is 2809.
com.ibm.CORBA.loginSource=properties
com.ibm.CORBA.loginUserid=admin and set
com.ibm.CORBA.loginPassword=admin
(Assuming admin/admin for authentication to the SamplesServer)
In project properties, (right click on project, find properties in the menu), go to the Java Builder tab. Add the j2ee.jar as an External Jars from the <ODM Install Dir>/lib folder.
Sun works with the JKS formatted trust and store files, although you can probably get it to work with the p12 formatted files, I find that converting them over to JKS is the simplest.
Go to your <ODM INSTALL>/bin directory and start ikeyman. From there open the trust.p12 file. The default password is WebAS. And then just save it as trust.jks in the jks format with the same password. And also do the same for your key.p12 file saving it as key.jks in the jks format.
Now, in Eclipse, copy the security configuration folder that we created in Part 1 and name it SunJDKSecurity.
Edit the ssl.client.props file and change the user.root to point to your current project/SunJDKSecurity folder. To do this right click on the project security folder that you created and select properties. This will give you the full path to the folder. Highlight the path and use ctrl-c to copy. Then ctrl-s to save the file.
In addition you will have to replace some of the IBMJSSE settings with SunJSSE settings in this file. make the following edits. The big change is modifying the certifcates from .p12 to .jks format. We'll do that in the next step.
| Setting | IBMJDK Value | SunJDK Value |
| com.ibm.ssl.alias | DefaultSSLSettings | DefaultSSLSettings |
| com.ibm.ssl.protocol | SSL_TLS | SSL |
| com.ibm.ssl.securityLevel | HIGH | HIGH |
| com.ibm.ssl.trustManager | IbmPKIX | PKIX |
| com.ibm.ssl.keyManager | IbmX509 | SunX509 |
| com.ibm.ssl.contextProvider | IBMJSSE2 | SunJSSE |
| com.ibm.ssl.enableSignerExchangePromp | gui | gui |
| #com.ibm.ssl.keyStoreClientAlias | default | |
| #com.ibm.ssl.customTrustManagers | ||
| #com.ibm.ssl.customKeyManager | ||
| #com.ibm.ssl.dynamicSelectionInfo | ||
| #com.ibm.ssl.enabledCipherSuites | ||
| # KeyStore information | ||
| com.ibm.ssl.keyStoreName | ClientDefaultKeyStore | ClientDefaultKeyStore |
| com.ibm.ssl.keyStore | ${user.root}/etc/key.p12 | ${user.root}/etc/key.jks |
| com.ibm.ssl.keyStorePassword | WebAS | WebAS |
| #com.ibm.ssl.keyStorePassword | {xor}CDo9Hgw | {xor}CDo9Hgw |
| com.ibm.ssl.keyStoreType | PKCS12 | JKS |
| com.ibm.ssl.keyStoreProvider | IBMJCE | SUN |
| com.ibm.ssl.keyStoreFileBased | TRUE | TRUE |
| # TrustStore information | ||
| com.ibm.ssl.trustStoreName | ClientDefaultTrustStore | ClientDefaultTrustStore |
| com.ibm.ssl.trustStore | ${user.root}/etc/trust.p12 | ${user.root}/etc/trust.jks |
| com.ibm.ssl.trustStorePassword | WebAS | WebAS |
| #com.ibm.ssl.trustStorePassword | {xor}CDo9Hgw | {xor}CDo9Hgw |
| com.ibm.ssl.trustStoreType | PKCS12 | JKS |
| com.ibm.ssl.trustStoreProvider | IBMJCE | SUN |
| com.ibm.ssl.trustStoreFileBased | TRUE | TRUE |
| com.ibm.ssl.trustStoreReadOnly | FALSE | FALSE |
Check that you edited the sas.client.props file and set the following, which you would have done in the part 1 of this Blog)
com.ibm.CORBA.securityServerPort to your correct port, by default it is 2809.
com.ibm.CORBA.loginSource=properties
com.ibm.CORBA.loginUserid=admin and set
com.ibm.CORBA.loginPassword=admin
(Assuming admin/admin for authentication to the SamplesServer)
Now change the the runtime properties that you set in the first part of this exercise so they point to the SunJDKSecurity folder. In the VM Arguments modify the following:
-Dcom.ibm.SSL.ConfigURL=file:///${project_loc}/SunJDKSecurity/properties/ssl.client.props
-Dcom.ibm.CORBA.ConfigURL=file:///${project_loc}/SunJDKSecurity/properties/sas.client.props
At this point, you should be able to run this app without errors using just the SunJDK. Next we're going to add an ODM Events Project to the workspace.
IBM ODM Events from Sun JDK (Part 1)
Configuring an IBM JMS client to talk to WAS ...
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. And this first part just shows how to get a JMS client talking to ODM in with the IBMJDK.
Let's assume that you have ODM with the Events components installed on C:\IBM\ODM85. And that you have created an ODM profile in the folder <ODM Install>/profiles/ODMSamples8500. I am using version 8.5, but this should work with previous versions of ODM / WODM with some obvious changes to pathnames, filenames, etc. Likewise, it doesn't have to be SamplesServer.
Even though I'm not going to use it yet, I'll need to install the SunJDK as an alternate JRE in Eclipse. So I downloaded the SunJDK only and installed that in C:\Java. Then in Eclipse Windows/Preferences menu, filter on Installed JRE. and from there add the new Java install dir.
Then I'll need a client JMS project in Eclipse, so change to the Java perspective and create a new Java project. Call it JMSClientExample.
Create some security configuration folders. In the Eclipse project create a new folder. Call it security. Under it create two more folders, one called properties and one called etc.
Copy the trust.p12 and key.p12 files from your <ODM Profile>/etc folder in to the new etc folder.
To do this, from the project inspector, right click on the etc folder and select Import... File System and then browse to the <ODM profile>/etc folder and select those files.
Likewise, copy the ssl.client.props and sas.client.props files from your <ODM Profile>/properties folder in to the new properties folder. To do this, right click on the properties folder and select Import... File System and then browse to the <ODM profile>/properties folder and select those files.
Edit the ssl.client.props file and change the user.root to point to your current project/security folder. To do this right click on the project security folder that you created and select properties. This will give you the full path to the folder. Highlight the path and use ctrl-c to copy. Then ctrl-s to save the file.
Edit the sas.client.props file and set the following:
com.ibm.CORBA.securityServerPort to your correct port, by default it is 2809.
com.ibm.CORBA.loginSource=properties
com.ibm.CORBA.loginUserid=admin and set
com.ibm.CORBA.loginPassword=admin
(Assuming admin/admin for authentication to the SamplesServer)
In project properties, (right click on project, find properties in the menu), go to the Java Builder tab. Add the j2ee.jar as an External Jars from the <ODM Install Dir>/lib folder.
Create a new class in the project. Call it JMSClientExample.java and add the following source code:
import java.util.Hashtable;
import java.util.Properties;
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.Destination;
import javax.jms.MessageProducer;
import javax.jms.Session;
import javax.jms.TextMessage;
import javax.naming.Context;
import javax.naming.InitialContext;
public class JMSClientExample {
/**
* @param args
*/
public static void main(String[] args) {
// TODO Auto-generated method stub
String messageID = null;
String outString = null;
String cfName = "jms/WbeConnectionFactory";
String qnameIn = "jms/actionTopic";
String qnameOut = "jms/actionTopic";
boolean verbose = false;
Session session = null;
Connection connection = null;
ConnectionFactory cf = null;
MessageProducer mp = null;
Destination destination = null;
try {
Hashtable env = new Properties();
env.put(Context.PROVIDER_URL, "corbaloc:iiop:localhost:2811"); // change your port as appropriate, default is 2809
env.put(Context.INITIAL_CONTEXT_FACTORY,
"com.ibm.websphere.naming.WsnInitialContextFactory");
Context initialContext = new InitialContext(env);
System.out.println("Getting Connection Factory");
cf= (ConnectionFactory)initialContext.lookup( cfName );
System.out.println("Getting Queue");
destination =(Destination)initialContext.lookup(qnameOut);
System.out.println("Getting Connection for Queue");
connection = cf.createConnection("admin","admin"); // use the createConnection method that takes auth params
System.out.println("staring the connection");
connection.start();
System.out.println("creating session");
session = connection.createSession(false, 1);
System.out.println("creating messageProducer");
mp = session.createProducer(destination);
System.out.println("creating TextMessage");
TextMessage outMessage = session.createTextMessage("this is test application");
System.out.println("sending Message");
mp.send(outMessage);
mp.close();
session.close();
connection.close();
}
catch (Exception je) {je.printStackTrace();}
}
}
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. And this first part just shows how to get a JMS client talking to ODM in with the IBMJDK.
Let's assume that you have ODM with the Events components installed on C:\IBM\ODM85. And that you have created an ODM profile in the folder <ODM Install>/profiles/ODMSamples8500. I am using version 8.5, but this should work with previous versions of ODM / WODM with some obvious changes to pathnames, filenames, etc. Likewise, it doesn't have to be SamplesServer.
Even though I'm not going to use it yet, I'll need to install the SunJDK as an alternate JRE in Eclipse. So I downloaded the SunJDK only and installed that in C:\Java. Then in Eclipse Windows/Preferences menu, filter on Installed JRE. and from there add the new Java install dir.
Then I'll need a client JMS project in Eclipse, so change to the Java perspective and create a new Java project. Call it JMSClientExample.
Create some security configuration folders. In the Eclipse project create a new folder. Call it security. Under it create two more folders, one called properties and one called etc.
Copy the trust.p12 and key.p12 files from your <ODM Profile>/etc folder in to the new etc folder.
To do this, from the project inspector, right click on the etc folder and select Import... File System and then browse to the <ODM profile>/etc folder and select those files.
Likewise, copy the ssl.client.props and sas.client.props files from your <ODM Profile>/properties folder in to the new properties folder. To do this, right click on the properties folder and select Import... File System and then browse to the <ODM profile>/properties folder and select those files.
Edit the ssl.client.props file and change the user.root to point to your current project/security folder. To do this right click on the project security folder that you created and select properties. This will give you the full path to the folder. Highlight the path and use ctrl-c to copy. Then ctrl-s to save the file.
Edit the sas.client.props file and set the following:
com.ibm.CORBA.securityServerPort to your correct port, by default it is 2809.
com.ibm.CORBA.loginSource=properties
com.ibm.CORBA.loginUserid=admin and set
com.ibm.CORBA.loginPassword=admin
(Assuming admin/admin for authentication to the SamplesServer)
In project properties, (right click on project, find properties in the menu), go to the Java Builder tab. Add the j2ee.jar as an External Jars from the <ODM Install Dir>/lib folder.
Create a new class in the project. Call it JMSClientExample.java and add the following source code:
import java.util.Hashtable;
import java.util.Properties;
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.Destination;
import javax.jms.MessageProducer;
import javax.jms.Session;
import javax.jms.TextMessage;
import javax.naming.Context;
import javax.naming.InitialContext;
public class JMSClientExample {
/**
* @param args
*/
public static void main(String[] args) {
// TODO Auto-generated method stub
String messageID = null;
String outString = null;
String cfName = "jms/WbeConnectionFactory";
String qnameIn = "jms/actionTopic";
String qnameOut = "jms/actionTopic";
boolean verbose = false;
Session session = null;
Connection connection = null;
ConnectionFactory cf = null;
MessageProducer mp = null;
Destination destination = null;
try {
Hashtable env = new Properties();
env.put(Context.PROVIDER_URL, "corbaloc:iiop:localhost:2811"); // change your port as appropriate, default is 2809
env.put(Context.INITIAL_CONTEXT_FACTORY,
"com.ibm.websphere.naming.WsnInitialContextFactory");
Context initialContext = new InitialContext(env);
System.out.println("Getting Connection Factory");
cf= (ConnectionFactory)initialContext.lookup( cfName );
System.out.println("Getting Queue");
destination =(Destination)initialContext.lookup(qnameOut);
System.out.println("Getting Connection for Queue");
connection = cf.createConnection("admin","admin"); // use the createConnection method that takes auth params
System.out.println("staring the connection");
connection.start();
System.out.println("creating session");
session = connection.createSession(false, 1);
System.out.println("creating messageProducer");
mp = session.createProducer(destination);
System.out.println("creating TextMessage");
TextMessage outMessage = session.createTextMessage("this is test application");
System.out.println("sending Message");
mp.send(outMessage);
mp.close();
session.close();
connection.close();
}
catch (Exception je) {je.printStackTrace();}
}
}
Now set the runtime debug properties.
Create a debug configuration for JMSClientExample. In the VM Arguments add the following:
-Dcom.ibm.CORBA.Debug=true
-Dcom.ibm.CORBA.CommTrace=true
-Dcom.ibm.CORBA.Debug.Output=c:/temp/client.log
-Dcom.ibm.ejs.ras.lite.traceSpecification=*=all
-Dcom.ibm.SSL.ConfigURL=file:///${project_loc}/security/properties/ssl.client.props
-Dcom.ibm.CORBA.ConfigURL=file:///${project_loc}/security/properties/sas.client.props
-Dcom.ibm.ejs.ras.lite.traceSpecification=SIB*=all
-Dcom.ibm.ejs.ras.lite.traceFileName=c:/temp/trace.log
Add the following to the classpath from the <ODM Install Dir>/runtimes folder.
com.ibm.ws.ejb.thinclient_8.5.0.jar,
com.ibm.ws.orb_8.5.0.jar,
com.ibm.ws.sib.client.thin.jms_8.5.0.jar.
And from the <ODM Install Dir>/runtimes/properties folder add the
orb.properties file.
orb.properties is not a jar file so you'll have to change the file selector to *.* in order to add it. These files provide the runtime elements you need to talk to the WAS JMS provider in IBM ODM.
com.ibm.ws.orb_8.5.0.jar,
com.ibm.ws.sib.client.thin.jms_8.5.0.jar.
And from the <ODM Install Dir>/runtimes/properties folder add the
orb.properties file.
orb.properties is not a jar file so you'll have to change the file selector to *.* in order to add it. These files provide the runtime elements you need to talk to the WAS JMS provider in IBM ODM.
At this point, you should be able to run this app without errors using just the IBM JDK. Next we're going to switch over to the SunJDK.
Subscribe to:
Posts (Atom)