Novell Cool Solutions

Consultants Corner: Quick Tip: How to Install WebAccess 2014 on Windows 2012 IIS (or Windows 2008)

Gregg Hinchman

By:

June 9, 2014 11:10 am

Reads:1,595

Comments:0

Score:5

Print/PDF

Recently I had the pleasure of installing GroupWise 2014 on Windows 2012 server. Generally, 75% of my installs/upgrades are to Linux and I get very little time to play with new Windows operating systems. And Windows 2012 is definitely a different look and feel.

In the process of installing the GroupWise 2014 WebAccess portion, I hit a snag. WebAccess 2014 did not work. Not being as well versed in IIS as I am with Apache2, I struggled to figure out what we missed. I figured we had missed some part of IIS for sure, but what part. After a time, and some research I found it was the ISAPI Extensions and Filters. Now, if you are a Windows jockey, you likely know this, but I had long forgotten they were needed for GroupWise WebAccess. So, to help those that may not be as Windows savvy as others, I bring you this quick tip.

The first step is to install IIS on the Windows 2012(r2) server.
The second step in installing GroupWise 2014 WebAccess on Windows 2012 (r2) IIS is to install the ISAPI Extensions and Filters.

On the IIS server where you will install GroupWise 2014 WebAccess:

  1. Go to Server Manager
  2. Select Local Server (on the left side)
  3. Select Manage (upper right side)
  4. Select Add Roles and Features
Figure 1: Server Manager, Local Server, Manage, Add Roles and Features (Windows 2012)

Figure 1: Server Manager, Local Server, Manage, Add Roles and Features (Windows 2012)

In the pop up window:

  1. Select Server Roles
  2. Select WebServer (IIS)
  3. Select WebServer
  4. Use the slider bar
  5. Check and Expand the Application Development option
  6. Check the ISAPI Extensions and ISAPI Filters
  7. Select Next
  8. Select Next
  9. Select Install
  10. Select Close
Figure 2: Add Roles and Features, Web Server IIS, Web Server

Figure 2: Add Roles and Features, Web Server IIS, Web Server

Figure 3: Slider bar, Application Development, ISAPI Extensions and ISAPI Filters

Figure 3: Slider bar, Application Development, ISAPI Extensions and ISAPI Filters

Figure 4: Next, Next, Install

Figure 4: Next, Next, Install

Figure 5: Installing ISAPI Extensions and Filters, Close

Figure 5: Installing ISAPI Extensions and Filters, Close

The third step is to install the GroupWise 2014 WebAccess code. This includes an installation of Tomcat6 as well. Here is a list of prerequisites for Windows 2008/2012/2012r2.

  1. Microsoft Internet Information Server (IIS) 7 or later
  2. Tomcat 6 (automatically installed with GroupWise 2014 WebAccess)
  3. IBM Java 6 Runtime Environment (JRE) (automatically installed with GroupWise 2014 WebAccess)
  4. Jakarta Connector 1.2 (automatically installed with GroupWise 2014 WebAccess)
  5. ISAPI support (see above)

At this point, just run through the GroupWise 2014 WebAccess installation. When finished, make sure you have stop/start IIS (WorldWideWeb service), Tomcat 6. And a note, during the install of the GroupWise 2014 WebAccess, I prefer to have stopped IIS services first. While I know you may not have to do that, I have in the past found it works. The information provided here is presented in Novell Documentation but not to the detail presented here. Hopefully, this quick tip will save you some time.

For more information about ISAPI Filters see:
GroupWise 2014 Documentation
TID: 7006147

Got comments or article ideas? Need help GroupWise? Drop me a line at: Gregg@HinchmanConsulting.com. “The Force is strong in this one.”

 

1 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 5 (1 votes, average: 5.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Tags: ,
Categories: GroupWise, Technical

0

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS