nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is anybody running LiveSite on zLinux?

Frederik

I've searched for zLinux and zSeries and found no hits on the forum. (apart from 1 OpenDeploy issue).

I'm wondering if anyone is running LiveSite on zLinux, and if you're willing to post some experiences?

thanks!

Find more posts tagged with

Comments

Frederik

Haven given this some thought ...

In theory, LiveSite and dependencies is mostly Java code, and so should run, with perhaps a few exceptions / attention points.

(assuming version 7.1, but I'm curious about any experience with any version)

- IDOL in LSCS is binary (but Autonomy states in this white paper (*1) that "other POSIX compliant UNIX versions are available on request.")
- OpenDeploy receiver seems to include some native code - OD Rcvr 6.2.1 was supported on zLinux, but 7.1 not (yet?)
- LSCS installer is a bit shaky (not packaged as .ear/.war file) but that can be manually resolved I guess.

*1) http://publications.autonomy.com/pdfs/Power/Product%20Briefs/IDOL%20Server/20091001_PI_PB_IDOL7techbrief_web.pdf

1428479963920.docx

log_error_JDBC.docx

AlexC

Livesite should run in zLinux (which is IBM's Novell/SUSE based distro), however QA has not tested it. Given that Livesite is a WAR file if you get a container running on it (Tomcat, JBoss, WAS, WL, etc) then it should not be an issue. My only concern is that IBM likes to move things around and some basic utilities/directories may not be in the place the installer expects and may not even be in the path initially. You should have someone familiar with zLinux (like an admin) on-hand when doing the install.

If you are using WAS (I am assuming this since you are looking at the IBM linux distro), you should have an admin that is familiar with their configuration (WAS is far from trivial to configure and tune); WAS which uses their own version of common open source libraries which have been branched by IBM and no longer fully compatible (Xalan, Xerces, et al), so extra configuration steps are required to make sure the correct open source libraries are visible to the WAR (PARENT_LAST must be set at the very least) and IBM ones are not picked up (since they removed Serialization from their version for some odd reason and prevent the caches from working). Another issue is with logging, WAS uses their own version of log4j which again is not compatible with open source version and you have to configure logging to correctly get it to work (we have a document that explains this so it is something to be aware of).

Another issue you should be aware of with WAS is that when it starts it uses roughly 400MB of RAM without anything loaded, so you will need to size memory on the high side to account for this (there are a lot of "services" included with WAS that you may or may not need but they get loaded anyways).

Other than above issues it should work fine.

log_error_Birt_Designer_Pro.txt

Frederik

Thanks Alex, I appreciate your input.

I'm under the impression that you're focusing solely on LSDS though.

What about

- OpenDeploy (apparently 7.1 not available for zSeries, but OD Rcvr 6.2.1 was?). OD is basically a JVM, but seems to include some native code (not sure if one could hope to run without the native code and still get the majority of features in OD). OD is a mandatory element for LSDS...

- LSCS (embedded IDOL binary for zSeries) ?? LSCS is mandatory if we want Targeting etc...

I've read somewhere in a recent post on devnet that 7.2 release is forthcoming. Can you comment on that & on additional platform support (if any)?

PS: I was very interested by your comments on IBM modifications of Open Source packages etc. Even though we strictly followed the install guide when installing LSDS 7.1 on WAS 7.0 (ls_71_runtime_install_v01_en.pdf), I'm noticing several java.io.NotSerializableException messages in the logs (in code called by org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCache). I guess I may need to make a separate post about that.

Edit1:
PS2: the way the story's been told to me, our zLinux is (supposedly) a RedHat compile for zSeries. Wikipedia says IBM supports both SUSE and RedHat for zSeries

AlexC

OpenDeploy question you may want to take to their forum area, I do not know enough.

LSCS by itself is also a WAR but uses IDOL which is platform specific so that would be the determining factor.

I can't comment on the future releases, I do not have that information.

NotSerializable is the result of IBM libraries loaded before open source ones, you must have PARENT_LAST set on the classloader config for things to work.

Adam Stoller

- OpenDeploy (apparently 7.1 not available for zSeries, but OD Rcvr 6.2.1 was?). OD is basically a JVM, but seems to include some native code (not sure if one could hope to run without the native code and still get the majority of features in OD). OD is a mandatory element for LSDS...

FYI - OD's core code is, I believe, still C++ - on top of which is layer (or two, or three) of Java -- not sure if it makes a difference in your opinion, but ...

Frederik

NotSerializable is the result of IBM libraries loaded before open source ones, you must have PARENT_LAST set on the classloader config for things to work.

Thanks. I've split that off to "Running LSDS 7.1 on Websphere: using Parent Last class loader order, etc."

Frederik

FYI - OD's core code is, I believe, still C++ - on top of which is layer (or two, or three) of Java -- not sure if it makes a difference in your opinion, but ...

thx. good to know... I've moved this on OD sub-forum as AlexC suggested. http://devnet.interwoven.com/forums_vb/showthread.php?t=32798&forumid=12 to see if others share your beliefs Smiley Wink