4. WorldServer Forum for version 10.x - Recent Threads

RE: From WS10 Management > Linguistic Tool Setup > Filter Configurations What we need to do is to tell WS10 the following. Treat the strings between the following tag pair:

Christine Padgett — Thu, 10 Aug 2023 05:08:07 GMT

Hy there i can see your post and i must say

It seems like you're describing a configuration process within a software or system, specifically related to linguistic tools and filter configurations. However, the information you've provided is not complete, making it difficult for me to give you precise guidance. It seems like you want to provide instructions for how to handle certain strings within tag pairs.

To provide you with accurate guidance, I'll need more specific details about the software or system you're referring to and the exact steps or actions you need to take. If you could provide more context or specific instructions you want to convey to the system, I'll be better able to assist you. My AARP Medicare Login

Thanks and regards

Christine Padgett

From WS10 Management > Linguistic Tool Setup > Filter Configurations What we need to do is to tell WS10 the following. Treat the strings between the following tag pair:

Evan Cohen — Tue, 03 Apr 2018 21:07:14 GMT

What we need to do is to tell WS10 the following.
Treat the strings between the following tag pair:
<?xm-insertion_mark_start.*?>
<?xm-insertion_mark_end ?>
to appear as a series of strings without breaking into individual segments.
So the tag pair (or as separate entries) needs to be treated like embedded tags, such <bold> <italic> <xref> etc.

From WS10 Management > Linguistic Tool Setup > Filter Configurations
I tried to modify the parsing settings but nothing worked.
It seems when FTS Server is in effect, there filter settings are not read (for Studio File Types)...
In addition, without writing any rules for <?xm-insertion_mark_.?> and <?xm-deletion_mark.?>, WS10 recognizes there tags (insertion mark as fragment, deletion mark to be suppressed)

Major issues with Astoria 6.4 (recent upgraded) (Creating new Projects) parsing XML files fail with WS 10.4.03: Has anybody else had this issue?

Evan Cohen — Wed, 30 May 2018 12:47:58 GMT

We just upgraded our CMS to Astoria 6.4, and now all new projects fail to be created, surprising older projects can be returned without issues.

"com.idiominc.webservices.client.WSRuntimeException (covers java.lang.RuntimeException: org.xml.sax.SAXException: Invalid element in com.idiominc.webservices.data.WorkflowWSProjectType - optionalAttributeDescriptors)"

RE: Major issues with Astoria 6.4 (recent upgraded) (Creating new Projects) parsing XML files fail with WS 10.4.03: Has anybody else had this issue?

Eric Bishop — Wed, 30 May 2018 15:19:12 GMT

Looking at the properties i can say that the very last item there (wspRefAtt,0=) does seem suspect to me. The error you initially provided was about optional attribute descriptors and reference material definitely could fall into that category. The reason it is suspect to me is because it is the only item where there is nothing on the right side of the equal sign. However, why that is the case is something only Astoria support could tell you. Is there a way that you can see the actual client side SOAP call that is being made to WorldServer from Astoria?

RE: Major issues with Astoria 6.4 (recent upgraded) (Creating new Projects) parsing XML files fail with WS 10.4.03: Has anybody else had this issue?

Evan Cohen — Wed, 30 May 2018 15:11:03 GMT

com.idiominc.webservices.client.WSRuntimeException (covers java.lang.RuntimeException: org.xml.sax.SAXException: Invalid element in com.idiominc.webservices.data.WorkflowWSProjectType - optionalAttributeDescriptors)

The batch job was: Start Translation on portal_8203.ditamap (pt_BR, es_ES)

Submitted by: Evan Cohen

Running on server: IBIAPPSA

The properties of this batch job were: {ABWOP:outputDirectory,0=D:\PROGRA~2\ASTORI~1\ACS\translationExport, ABWOP:exportFilter,0=8203, ABWOP:configurationGUID,0=, ABWOP:operation,0=submitStartTranslation, ABWOP:object,0=00000018WIAC07D6E10GYZ, ABWOP:bypassWS,0=false, ABWOP:destCabID,0=00000017WGA8010GYZ, ABWOP:destCabID,1=00000017WGA5010GYZ, ABWOP:wspVal,0=No, ABWOP:userName,0=ibi\ec01019, ABWOP:wspDesc,0=portal_8203.ditamap, ABWOP:thisDocumentOnly,0=false, ABWOP:wspType,0=Translation, ABWOP:translationCancelPD,0=false, ABWOP:organization,0=, ABWOP:excludeXRefs,0=true, Status=Ready, ABWOP:translationPriority,0=, ABWOP:vendor,0=, ABWOP:dueDate,0=1528208453878, ABWOP:wspRec,0=1, ABWOP:jobDesc,0=, ABWOP:wspName,0=portal_8203.ditamap, ABWOP:wspClient,0=WorldServer, ABWOP:wspPreCost,0=No, ABWOP:wspMat,0=Tech Doc, ABWOP:restartWS,0=false, ABO:ClassName=com.lspeed.webforms.BatchWebformsOperation, ABWOP:translationType,0=Full, ABWOP:includeGraphics,0=false, ABWOP:previousJobs,0=, name=Start Translation on portal_8203.ditamap (pt_BR, es_ES) , ABWOP:blockLevel,0=false, ABWOP:jobName,0=portal_8203.ditamap, ABWOP:wspRefAtt,0=}

RE: Major issues with Astoria 6.4 (recent upgraded) (Creating new Projects) parsing XML files fail with WS 10.4.03: Has anybody else had this issue?

Eric Bishop — Wed, 30 May 2018 15:08:36 GMT

I just test my links above and they seem to be one level up from where i intended. In the first link, once you are there, then click on the Configuring Options in WorldServer link. For the second link, once there, click the Additional Fields for Start Translation with WorldServer link

RE: Major issues with Astoria 6.4 (recent upgraded) (Creating new Projects) parsing XML files fail with WS 10.4.03: Has anybody else had this issue?

Eric Bishop — Wed, 30 May 2018 15:05:08 GMT

Just to be clear, this is an issue that i think that Astoria support would need to be the authoritative source for the solution for this issue. However, given the link you gave above, can you confirm that in your WorldServer instance the configurations defined at
ars.astoriasoftware.com/.../cs_AboutWorldServer.html are set up correctly? If so, is the GUI shown at ars.astoriasoftware.com/.../tk_StartingTranslationJob.html the one that you use to create a new translation? If so, could you provide a screenshot of one of the projects you are attempting to send that is giving this error before you actually submit it? If you need help attaching an image in this thread, i can help with that.

RE: Major issues with Astoria 6.4 (recent upgraded) (Creating new Projects) parsing XML files fail with WS 10.4.03: Has anybody else had this issue?

Evan Cohen — Wed, 30 May 2018 14:54:13 GMT

Actually this is well documented in the Astoria help system. ars.astoriasoftware.com/.../index.jsp

RE: Major issues with Astoria 6.4 (recent upgraded) (Creating new Projects) parsing XML files fail with WS 10.4.03: Has anybody else had this issue?

Eric Bishop — Wed, 30 May 2018 14:39:42 GMT

It looks like some invalid data is being sent when attempting to create a project using the client SDK. Do you have any insight on what is inside the calls that are sent from (i assume) Astoria and WorldServer? What do you have that connects the two systems? Is it custom development or is it something purchased?

RE: TLS 1.2 - How to set it up on WS 10.4.3

Former Member — Tue, 28 Nov 2017 17:27:03 GMT

BRILLIANT !!!!

You made my day

TLS 1.2 - How to set it up on WS 10.4.3

Former Member — Wed, 22 Nov 2017 16:11:24 GMT

Hello everyone,

One of our external app, we are connecting to, requires the connection to be TLS 1.2. I found a possible work around but have no idea on where to put it in the JAVA/Tomcat configuration.

JVM parameter of -Dhttps.protocols=TLSv1.1,TLSv1.2.

If someone already implemented such thing, I'll be glad to know how he/she did it...

RE: TLS 1.2 - How to set it up on WS 10.4.3

Eric Bishop — Tue, 28 Nov 2017 17:10:53 GMT

In that case, search your server for a file called idiom.cfg, you can put the options in that file. Be sure however to follow the following kb article:

gateway.sdl.com/CommunityKnowledge

RE: TLS 1.2 - How to set it up on WS 10.4.3

Former Member — Tue, 28 Nov 2017 17:06:00 GMT

Hello Eric,

unfortunately, I don't have IdiomRunw.exe as we are running with 10.4.3. I've tried to change the tomcat config by adding some parameters in server.xml under ...\tomcat\conf but that didn't work.

I'm running out of solution.....

RE: TLS 1.2 - How to set it up on WS 10.4.3

Former Member — Thu, 23 Nov 2017 17:01:24 GMT

Many thanks for your help Eric

RE: TLS 1.2 - How to set it up on WS 10.4.3

Eric Bishop — Wed, 22 Nov 2017 17:00:45 GMT

The best way to change them is by using the tomcat launcher config. In 10.x the executable is called idiomRunw.exe located in your ....\tomcat\bin
folder.

In 11.x i believe it is called tomcat8w.exe.

Once launched you click on the JAVA tab and you then put your parameters in the java options section.

At the following link, changing your java heap space is documented and changing the parameter you reference is goes into the same location so it my be helpful.
gateway.sdl.com/CommunityKnowledge

RE: Best FTS configuration (daemons, etc)?

Eric Bishop — Tue, 10 Oct 2017 17:37:27 GMT

Yes we keep them the same, as well as any relevant portions of the pdf one. however i have never heard of any use cases where these were applicable and do not think that the control anything.

Best FTS configuration (daemons, etc)?

Former Member — Thu, 05 Oct 2017 16:09:34 GMT

I was looking to get the best of the FTS configuration (Daemon, engine cache size, etc) but could not found any relevant info. I'm interested in getting from your configuration the values you have in the file "Sdl.WorldServer.FileTypeSupport.Server.HostProcess.exe.config".

This is what I have:

<add key="NumberOfDaemons" value="4" />
<add key="SleepTime" value="1" />
<add key="EngineCacheSize" value="0" />

Also do you use the following?

RE: Best FTS configuration (daemons, etc)?

Former Member — Tue, 10 Oct 2017 08:55:55 GMT

Thanks Eric Bishop for this very useful explanation!

Just to be sure about one thing: do you use the same values for <add key="NumberOfDaemons" value="4" />, <add key="SleepTime" value="1" /> and <add key="EngineCacheSize" value="0" /> in both Sdl.WorldServer.FileTypeSupport.Server.HostProcess.exe.config and Sdl.WorldServer.FileTypeSupport.Server.Tools.exe.config

RE: Best FTS configuration (daemons, etc)?

Eric Bishop — Mon, 09 Oct 2017 17:54:33 GMT

Actually, FTS has a threading issue and requires that you always have your daemons set at 1 and you have to increase your processes in the launcher config. I have repeatedly asked SDL to at least provide documentation as comments in the config files to this effect and long term allow the setting of the daemon to work. I have not heard any progress on that front.

As to your other settings, the engine cache size of 0 means that the engine will constantly be checking the DB for work to do and could negatively affect performance, what it does get you however, is the assurance that at any given time the FTS server is processing those jobs that have the highest priority. If you set the cache size higher, it collects a list of tasks to work on and does not check again until they are complete. In our environment we have that setting set to the same number of FTS processes we have on that node.

The sleep time is not a setting we've ever changed but with your setting, it will increase the frequency that the engine will check for new work, this may negatively impact performance but ensures that pending work in the queue does not stay pending for very long at all.

We do use the reader and write batch size, these control how much the server will queue up before making a call to the DB to either read or write. As Write's are about storing data, thus they have a lower threshold than the reader. If you wanted to follow the same pattern as you have for your other settings you'd decrease these values, however just like above, you are sacrificing performance for precision.

If i've got any of the above incorrect one of the SDL folks (Debbie Maguire (former member) Larry Bregman Misty Bragg Ray Hopley Stefan Bulzan) should be able to correct me.

RE: WorldServer 10.4.4 - Cannot parse asset data. Details: com.idiominc.ws.filters.FilterParseException

Youngrae Ko — Thu, 21 Jul 2016 15:54:27 GMT

I don't think we restarted the server, but we restarted the Idom Process Monitor and SDL File Type Support Server.

WorldServer 10.4.4 - Cannot parse asset data. Details: com.idiominc.ws.filters.FilterParseException

Youngrae Ko — Wed, 20 Jul 2016 16:07:55 GMT

After installing FTS update, we are getting the following error message in WorldServer 10.4.4

We followed the article found in FTS install change in 10.4.4(https://community.sdl.com/products-solutions/solutions/customer_experience_cloud/language/translation_management/sdl_worldserver/f/246/t/5577) and installed the vcredist_x86.exe but we still see the same error message.

Error Message:

Cannot parse asset data. Details: com.idiominc.ws.filters.FilterParseException:

Cannot validate SDL plug-in: Sdl.FileTypeSupport.Filters.MicrosoftOffice.DocxComponentBuilder, Sdl.FileTypeSupport.Filters.MicrosoftOffice.Word_2, Version=2.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888 :

RE: WorldServer 10.4.4 - Cannot parse asset data. Details: com.idiominc.ws.filters.FilterParseException

Caterina Lazzarini — Thu, 21 Jul 2016 09:31:59 GMT

According to the case you created, this issue happened after an FTS update. Have you installed the new Microsoft Word 2007-2016 Studio File Type along with the FTS update?

The error might point to it. If you have not installed it, the Hotfix associated with it is

17_WS-8848_NewWord2016Filter.zip

This Hotfix contains both the filter components and a FTS installer. You do NOT need to install FTS if you have already installed a later version. Just follow the instructions to add the Word filter correctly.

If you have any questions, please follow up with the support engineed who is working on your support case.

Caterina

RE: WorldServer 10.4.4 - Cannot parse asset data. Details: com.idiominc.ws.filters.FilterParseException

Taiki Takada — Thu, 21 Jul 2016 00:48:28 GMT

Just a quick confirm. Did you restart the server?

FTS install change in 10.4.4

Debbie Maguire (former member) — Wed, 04 Nov 2015 16:54:30 GMT

There's an additional step in the installation of FTS in 10.4.4 that's been tripping people up:

Note you see no errors during install, but the trouble starts when you try to segment assets. You see:

Cannot parse asset data. Details: com.idiominc.ws.filters.FilterParseException: Cannot validate SDL plug-in

There's a missing library:

Refer to the SDL WorldServer 10.4.4. Documentation, specifically to the FTS Server Prerequisites

WorldServer 10.4.4. FTS Server Prerequisites
This Prerequisite needs to be applied:
"Installing the latest FTS requires the vcredist_x86.exe version of the C++ 2013 redistributable package, available here:

Download Package

Install the C++ 2013 redistributable package, restart WorldServer and complete the project(s) that's in Autoerror.

FYI 10.4.4 documentation change

Debbie Maguire (former member) — Wed, 04 Nov 2015 16:33:55 GMT

Hi,

As of 10.4.4, WorldServer documentation is stored online on our LiveContent server:

WorldServer 10.4.4. Help

To see a list of how the new documentation maps to the PDF files you're all familiar with, click on "New in SDL WorldServer 10.4.4". There's a table there with that list.