Comments (9)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 djc@wyle commented Permalink

In step 1 it says to start the deployment manager from ctgDmgr02, which is the non-federated deployment manager created in part1 of this 3-part document. Is this correct? I tried following the same steps outlined in your blogs and I only have startmanager in ctgDmgr01, which is the migrated deployment manager. <div>&nbsp;</div> Thanks for your assistance

2 RichardLesses commented Permalink

I just tested setting up a new unfederated node in WAS You are correct. There is no startmanager in its \bin directory. <br /> Please run startNode and let me know if that works. If so, I will correct this blog. <br /> Rich

3 djc@wyle commented Permalink

So I should run statNode from the unfederated node ctgDmgr02? I was wondering if I should run startManager from the migrated ctgDmgr01 since it has been created at this point. Also, have you created a blog for the Maximo 7.5 to Maximo 7.6 upgrade yet? These 3 articles for WebSphere have been very helpful to use in conjunction with the IBM Upgrade Guide.

4 RichardLesses commented Permalink

David, I will run through these instructions myself, as it has been almost a year since I wrote the articles. <br /> On the Maximo 7.6 upgrade, I will be taking that project up again shortly.

5 RichardLesses commented Permalink

I went through my blog posts on migrating to WAS 8.5.5 again, and found that you run startmanager from the newly migrated Deployment manager profile, not from the one you created. <div>&nbsp;</div> I updated this post with the correct information. I also added three additional tasks to make sure that all of the migration screens are covered. (No new screen shots, but they're not necessary.) <div>&nbsp;</div> Thank you very much, David.

6 djc@wyle commented Permalink

Richard, <div>&nbsp;</div> I think you need to make the same change from ctgDmgr02 to ctgDmgr01 under the "Deploying the Maximo EAR File" step 2a as well. I also had to manually modify the httpd.conf file to add two lines (I think only one may have been necessary) They were: LoadModule was_ap22_module "C:\Program Files\IBM\HTTPServer1\Plugins\bin\32bits\mod_was_ap22_http.dll" <br /> WebSpherePluginConfig "C:\Program Files\IBM\HTTPServer1\Plugins\config\webserver1\plugin-cfg.xml" <br /> If I didn't have the WebSpherePluginConfig entry then I could not get to Maximo from my web browser unless I hardcoded the port in the url. The default port (80) did not even work if it was hard coded. I was getting 404 errors. Did you encounter this? Thanks for your efforts on this.

7 RichardLesses commented Permalink

David, thank you again. I have made the changes as suggested. I also added, to the end of part 4, as a last step, a link to a blog post by Shane Howard on configuring the WebSphere Plug-in for Maximo at

8 djc@wyle commented Permalink

Richard, <div>&nbsp;</div> Thanks for the link! This is what I needed. Unless I missed something, these steps are not included in the Upgrade Guide IBM Maximo Products V7.5 to V7.6 manual (at least for Chapter 7). This should get me to where I need to be with WebSphere. Then I will need to work on the Maximo 7.6 upgrade. Are these instructions going to be added to the Upgrade Guide? Regards, Dave

9 RichardLesses commented Permalink

Dave, <br /> A fresh Maximo 7.6 installation that includes installing and configuring WAS also configures the plug-in. Installing Maximo 7.6 using existing Middleware (WAS) assumes that you have already configured the plug-in, as you have done. Put simply, either we automate the whole configuration or leave it completely up to you.