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; } } }

TS 6.7.1 SP1 - Things to watch out

System

Starting this thread to share experiences with SP1 installation

1) The metadata tagging ui screens no longer works. When trying to save the tagging info it gives a XML root element exception. "Root cause:
This record does not contain the appropriate root element"

In your metadata-rules.cfg the vpath-regex has to start with ^.*?/default/../.../WORKAREA/

2) CSSDK client programs fail with Axis fault exceptions :
Make sure you download & install the CSSDK 3.1.0 SP1. some of the important jar files that have changes are CSSD*.jar, it now also has a dependency on sharedutils100.jar
NOTE: The jar files are different from that you find on TS server installations even though they have the same names.

3) Overwrites the Interwoven\TeamSite\local\config\lib\content_center\reference\build.xml - watch out for any customizations you have done to the build file

Find more posts tagged with

Comments

nbwoven

For fixing (2) you might sometimes get away with adding the SOAP key again in cssdk.cfg .

Migrateduser

4) onSave handler shows weird behaviour: IW has release Patch 1, which fixes the onSave handler.

5) Listing taxonomies in the Metatagger UI is not longer in alpha order, instead it is listed as FIFO. IW supports answer was "feature request". It used to work before SP1 though Smiley Wink

RonaldV

1) The metadata tagging ui screens no longer works. When trying to save the tagging info it gives a XML root element exception. "Root cause:
This record does not contain the appropriate root element"

In your metadata-rules.cfg the vpath-regex has to start with ^.*?/default/../.../WORKAREA/

AGAIN???? How stupid can they be at Iwov? Don't they do ANY regression tests on production like configuration?

gzevin

AGAIN???? How stupid can they be at Iwov? Don't they do ANY regression tests on production like configuration?

what kind of regression testing are you talking about? Smiley Happy

really rarely I saw that happen ....

I just hit the above error... thanks for this thread I got it cleared.

My metadata capture record is allegedly the most complex IWOV ever seen, they used it for the new metadata capture UI. And yet I had to tweak quite a few things, including CGI callouts.

RonaldV

[left]Greg,

exactly the same happened when Iwov decided to add the servername to the vpath (v6.0) and we had to rewrite our vpath-regexes in all our code and config (f.i. templating.cfg, available-templates.cfg)

Very, very annoying.
[/left]

Migrateduser

6) Upgraded MT Studio to 4.1.2 and import XML from vocab no longer works. I have a open ticket with IW to resolve this. Will update the forum as soon as they fix it

gzevin

6) Upgraded MT Studio to 4.1.2 and import XML from vocab no longer works. I have a open ticket with IW to resolve this. Will update the forum as soon as they fix it

I've just gone live with Linux 64-bit system. Looks like TeamSite OD cannot handle multiple fanouts from backing store. Intermittently failing. Ticket is also open. At the meantime some of the deployments go to temporary location on the hard drive, and are fanned out of there.....

FurnaceFace

I've just gone live with Linux 64-bit system. Looks like TeamSite OD cannot handle multiple fanouts from backing store. Intermittently failing. Ticket is also open. At the meantime some of the deployments go to temporary location on the hard drive, and are fanned out of there.....

Quick question - have you seen any major issues with latest version of TS with Linux? We are leaning towards it as our O/S of choice mainly because Solaris has been steadily on the decline at my current client. They would like to move with Linux but I still have bad dreams about the initial Linux Teamsite release (I think it was 6.1 that had the initial linux version).

Anything out of the ordinary that I would have to watch for (aside from minor bugs here and there)?

Thanks
/FF

gzevin

Quick question - have you seen any major issues with latest version of TS with Linux? We are leaning towards it as our O/S of choice mainly because Solaris has been steadily on the decline at my current client. They would like to move with Linux but I still have bad dreams about the initial Linux Teamsite release (I think it was 6.1 that had the initial linux version).

Anything out of the ordinary that I would have to watch for (aside from minor bugs here and there)?

Thanks
/FF

I am starting to get a feeling that UVFS for 64 bit Linux is not up to scratch. Not 100% sure, but looks like it cannot cope with the processor speed.

I was looking into some major issues related to, say, tinymce, not sure it's Linux-related or not. E.g., if the containers come by default collapsed, the tinyMCE would duplicate the textarea in the DCT, preview would not work. Just a single change in templating.cfg has fixed this. I was resolving the issue with another developer over the phone, and 'f' words were just flowing. pardon me.

Having said that, I am surprised that many things did work. And the move was not too bad. I anticipated a worse scenario.

One thing - because of me assessing the risk of going with TeamSite groups straightaway as too high, my client went with the existing store. The store from Solaris works Ok in Linux. Now I am going to gradually migrate the users to another, new store, while leaving the old one for reference purposes only. At the meantime I had to modify some ldap query scripts, which handle workflows, but that was not a major task at all.

GRD

Greg, your last post was a couple of weeks ago. Any more comments on UVFS? Thanks.

-Greg

diago

we are moving from 6.5SP0 solaris to 6.7.1 SP1 linux :
BackingStore size : 100 Go
320 categories
1660 data-type
4025 tpl
223 worklows

what we need to change until now
- split template.cfg to be above 6000 lines limit
- change iwgen and iwregen binairies to script calling iwpt_compile.ipl
- add "EnableSendfile off" to apache configuration for preview

LooseCannon

We have been running Linux / 6.7.1 in a prod environment for over a month and have had nothing but issues with fan out deployments. Deployments intermittently hang as a result of lstat calls to the teamsite failing and require OD reboots through the day.

According to engineering the "fix" is to update the uvsf to 2.0.2 http://sourceforge.net/projects/uvfs .

We are making the change tonight, so we'll see....

LooseCannon

A couple other issue with TS 671 and Red Hat…

Synchronizing users managed in LDAP with TeamSite does not work. This is a pain because it forces a Master user to manually manage users in TeamSite.

When using DCT inlines the file or script that’s being referenced (including the full dir path) must be readable to the world. Not cool when the file lives in a workarea and the branch or workarea are set to private.

All sorts of VisualFormat issues, but I don’t believe these to be Linux specific.

Previews from authoring forms periodically throw PT Compile errors. The solution from IWOV was to roll iwproxy back to pre SP1, but we still see the intermittent error.

Permissions don’t display correctly from the UI when setguid is on dirs, including workareas.

No supported clt to generate output when using XSLT presentation templates.

There are more, but OD needs bounced so gotta go.

gzevin

Greg, your last post was a couple of weeks ago. Any more comments on UVFS? Thanks.

-Greg

as LooseCannon has mentioned - yes, my dx was absolutely correct. It was UVFS. It took the support a few days to ask US Engineering, who confirmed the fact. At the meaintime the support was asking to do a few stupid changes in OD, when it was clear the issue was much deeper.

We are to test the new UVFS, as our admin has reported that TeamSite did hang a few times when on 2.0.1, hence he moved us to 2.0.0. Hope 2.0.2 fixes the issue.

but it's clear again that IWOV has not even beta tested their software. Our issue always is that IWOV never tests agains huge backing stores. I was the first to find out the slowliness of CCSTD in 6, as our backing store was big and number of branches as well. I thought they did learn the lesson, but looks like they did not. My client is extremely angry now and we'll be talking with some senior people to make things change.

I am still struggling with the Visual Format issue. (i reported it in separate posting). What's more, it takes away the relative links!!!!!!!!!!!! this is BAD

LooseCannon

We have been running Linux / 6.7.1 in a prod environment for over a month and have had nothing but issues with fan out deployments. Deployments intermittently hang as a result of lstat calls to the teamsite failing and require OD reboots through the day.

According to engineering the "fix" is to update the uvsf to 2.0.2 http://sourceforge.net/projects/uvfs .

We are making the change tonight, so we'll see....

Good news - Upgrading the kernel resolved our OD issues. On to resolving the next bug...

gzevin

Good news - Upgrading the kernel resolved our OD issues. On to resolving the next bug...

thanks, good to know.

Lex

2) CSSDK client programs fail with Axis fault exceptions :
Make sure you download & install the CSSDK 3.1.0 SP1. some of the important jar files that have changes are CSSD*.jar, it now also has a dependency on sharedutils100.jar
NOTE: The jar files are different from that you find on TS server installations even though they have the same names.

I have a question tangentially related to this: my apps (.Net using SOAP) developed against prior versions of the CSSDK have suddently started failing after installation of SP1. Authentication continues to work fine, but as soon as I try to perform an action such as listing the files in a workarea or retrieving a user's branches a Java error occurs (only the first few lines here):

WARNING: com.systinet.wasp.services.com.interwoven.cssdk.sci.soap.filesys.FileServiceSOAPImpl - has thrown an application exception.
EXCEPTION: no message
java.lang.NullPointerException
at java.util.Date.getMillisOf(Date.java:938)
at java.util.Date.after(Date.java:911)
at com.interwoven.cssdk.sci.data.CSSessionCache.isExpired(CSSessionCache.java:652)
at com.interwoven.cssdk.sci.data.CSSessionCache.getSession(CSSessionCache.java:663)
at com.interwoven.cssdk.sci.filesys.FileServiceSciImpl.getDirectoryContents(FileServiceSciImpl.java:1393)
at com.interwoven.cssdk.sci.soap.filesys.FileServiceSOAPImpl.getDirectoryContents(FileServiceSOAPImpl.java:920)

I don't believe this can be corrected by installing the CSSDK 3.1 SP1 since it seems to be a server issue and not a client issue and we are not using the Java client libraries. Now, I'm certainly no Java expert, but it seems to be a problem with a Java library on the server, specifically the Date functions. Does anyone know how to fix this issue? Thanks.

scandorph

I was looking into some major issues related to, say, tinymce, not sure it's Linux-related or not. E.g., if the containers come by default collapsed, the tinyMCE would duplicate the textarea in the DCT, preview would not work. Just a single change in templating.cfg has fixed this. I was resolving the issue with another developer over the phone, and 'f' words were just flowing. pardon me.

Interesting, I don't think it should've been an OS related issue. By the way, which version of the DCT were you using? 5.0 or 6.0?

gzevin

Interesting, I don't think it should've been an OS related issue. By the way, which version of the DCT were you using? 5.0 or 6.0?

maybe not OS-related. no matter which version of DCT it was.

actually, I had a different issue recently. some 4.5 DTD-based DCRs would crash the form IF it had a replicant (old style) and a container AND a VisualFormat field. The same form would open if I changed the external editor to tinymce. The problem was solved by changing the DTD of the dCT. But still, how bizzare.....

on th other fron - our Linux-based TeamSite crashes every second day since we went live. PATHETIC. DO NOT move to Linux till a couple of versions have passed.

LooseCannon

DO NOT move to Linux till a couple of versions have passed.

I agree. Our Linux implementation went live in April and things are just now running smooth. I’m still working through bugs but at least no longer babysitting OD and TS.

gzevin

I agree. Our Linux implementation went live in April and things are just now running smooth. I’m still working through bugs but at least no longer babysitting OD and TS.

my plans to migrate all store are on hold, as the system does not tolerate 3 stores (2 stores + iwadmin) - in this case it crashes every hour or so. Now I have moved migrated branches to the 'test' box, while we are babysitting the main box.

But I am really curious to see how people will deal with visual format 'features'. If I were IWOV, I'd move back to an older Ektron version while dealing with this new functionality.

FurnaceFace

But I am really curious to see how people will deal with visual format 'features'. If I were IWOV, I'd move back to an older Ektron version while dealing with this new functionality.

I have had a number of issues with VisualFormat as well since they upgraded it. The relative link issue is due to a Windows Vista / IE7 security and it's not going back to the old way as far as I know. There is an option to turn off the relative link option within the visualformatconfig.xml but it does not seem to work (override = true of false has no effect).

Visual Format / ewebeditpro is a good tool and the developers are prompt with their replies when asking questions about it, I just wish we could have a bit more control over what we would like modified. Some clients like the WYSIWYG but not have it do anything to the html in behind the scenes. Very frustrating because the code cleaner / scrubber is ALWAYS on to some extent. We have debated several times on whether we should just remove Visual Format and use plain text boxes but we have groups of people who are technically "declined" and need it to write HTML. In the end, we are using deploy and run scripts to change all the code in the dcr to what it should be because there is no way for Visual Format to accommodate the requirements of the client. (we push the DCRs to the web server and we use a web app to consume the DCR, get the metadata from a database and build the web pages on the fly so we have the liberty of modifying the DCRs after they go out.)

Thanks to you and Loose Cannon on sharing your Linux experiences - we are still thinking of it but it's been pushed off by about 6 months or so.

/FF

gzevin

I have had a number of issues with VisualFormat as well since they upgraded it. The relative link issue is due to a Windows Vista / IE7 security and it's not going back to the old way as far as I know. There is an option to turn off the relative link option within the visualformatconfig.xml but it does not seem to work (override = true of false has no effect).

well, if IWOV does not do anything about it, they soon will see Ektron being replaced by tinyMCE everywhere (maybe this is the hidden goal anyway? Smiley Happy

). I wrote already about links too many times - but the workaround being offered is not a working solution. Maybe for some customers, but not for ones who have 'smart' users that feel that they can put any kind of links. You cannot believe HOW MANY pages I have seen changed since we moved to this new version of Ektron.....

but also, I do not buy the reasoning about why Ektron had to change THAT way.

vijay_m_charles

Hi
So, were you able to figure out a workaround for this linking issue n VFE. Im kinda stuck with it. I am wondering if i should pre process all content before deploying them. Until then, please update me if you have something in mind. Some fix that would address this issue right on VFE.
thanks
Vj