Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.
Anonymous_User Absent Member.
Absent Member.
1593 views

iFolder 2.18 on NetWare 6.5 SP7

We are currently running iFolder 2 on 2 NetWare 6.0 nodes (clustered). We purchased new servers and have installed NetWare 6.5 SP7 on them and have them setup in a 2 node cluster. I am now trying to configure iFolder to run clustered on the new hosts, but cannot get it to load in protected memory. When I do, I receive this error:

Module NLDAP.NLM cannot be loaded until DSLOADER is loaded.

I have modified the startifolder.ncf to load:

LOAD ADDRESS SPACE = IFOLDER APACHE2 -f SYS:APACHE2\IFOLDER\SERVER\HTTPD.CONF

Please advise what I am missing. The 6.5 documentation has a really odd implementation of this that basically has you load Apache from the cluster and tie all your web services to the same instance. This doesn't seem correct.




Michael Roberts, MCNE, MCSE, CCA
Director of Network Services
Consolidated Health Systems/Highlands Regional Medical Center
Labels (1)
0 Likes
6 Replies
Knowledge Partner
Knowledge Partner

Re: iFolder 2.18 on NetWare 6.5 SP7

Michael Roberts,
> The 6.5 documentation has a really odd implementation of this that
> basically has you load Apache from the cluster and tie all your web
> services to the same instance.
>

Yes, that is the way I have set it up on clusters.

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the new Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iFolder 2.18 on NetWare 6.5 SP7

So, how would iPrint/NDPS be setup in this scenario? I don't want my Print Resource tied to my iFolder resource, even though they are both web services running on Apache.

>>> Anders Gustafsson<AndersG@no-mx.forums.novell.com> 2:19 1/9/2008 >>>

Michael Roberts,
> The 6.5 documentation has a really odd implementation of this that
> basically has you load Apache from the cluster and tie all your web
> services to the same instance.
>

Yes, that is the way I have set it up on clusters.

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the new Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement
0 Likes
Knowledge Partner
Knowledge Partner

Re: iFolder 2.18 on NetWare 6.5 SP7

Michael Roberts,
> So, how would iPrint/NDPS be setup in this scenario? I don't want
> my Print Resource tied to my iFolder resource, even though they are
> both web services running on Apache.
>

I see your point.. Yes, if you want them separate, then you need
separate Apache instances. Have you tried if iFolder runs in protected
memory?

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the new Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

0 Likes
adrockk Absent Member.
Absent Member.

Re: iFolder 2.18 on NetWare 6.5 SP7

You would need to make your http.conf only listen on your cluster
resource IP, and not on your physical IP. You would need a separate
instance for each web service (netstorage, ifolder,iprint,
nps/iManager,etc...)

You would have to keep tomcat running with on each box, then load apache
with the correct includes for each service.

If you feel like writing your own httpd.conf files for each instance of
apache, I don't see why it won't work. Sounds like a .conf file
nightmare to me, especially since every service pack is gonna make you
re-do it.

I thought about trying this so I could seperate iPrint and iFolder and
iManager, but then realized it made my brain hurt, so I just keep them
all together as one "APACHE" resource, and keep tomcat running on both
nodes.




0 Likes
Knowledge Partner
Knowledge Partner

Re: iFolder 2.18 on NetWare 6.5 SP7

Adam Gabriel,
> thought about trying this so I could seperate iPrint and iFolder and
> iManager, but then realized it made my brain hurt, so I just keep them
> all together as one "APACHE" resource, and keep tomcat running on both
> nodes.
>

Yep. That was my reasoning also.

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the new Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iFolder 2.18 on NetWare 6.5 SP7

Ok, thanks for the feedback. As I am upgrading from NetWare 6 and iFolder 2.11, this is surprising, as it just worked in that setup (clustered, running in it's own memory space). None of the fine tuning and separate conf files were necessary.

Thanks for the input anyway!

>>> Anders Gustafsson<AndersG@no-mx.forums.novell.com> 6:25 1/15/2008 >>>

Adam Gabriel,
> thought about trying this so I could seperate iPrint and iFolder and
> iManager, but then realized it made my brain hurt, so I just keep them
> all together as one "APACHE" resource, and keep tomcat running on both
> nodes.
>

Yep. That was my reasoning also.

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the new Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.