Tag: Document type definition

7023275: Access to Web port 9443 does not work

Novell Leave a comment

This document (7023275) is provided subject to the disclaimer at the end of this document.

Environment

Sentinel 8.2 Appliance

Situation

After upgrading the appliance to 8.2 there is an issue where access to port 9443 fails.
It eventually fails with a 500 internal server error:
org.springframework.web.util.NestedServletExceptio n: Request processing failed; nested exception is org.apache.tiles.definition.DefinitionsFactoryExce ption: I/O Error reading definitions.
Caused by: org.apache.tiles.definition.DefinitionsFactoryExce ption: I/O Error reading definitions.

Resolution

The network will never be connected to the internet so an offline copy of the file is needed.
More details on how to do that:
1. Download the .dtd from the location specified in the DOCTYPE tag within tiles-template.xml (http://tiles.apache.org/dtds/tiles-config_2_1.dtd)
2. Login to the appliance and do the following:
3. mkdir /dtd
Note: feel free to use any path you wish, just be consistent in referencing it.
4. copy the downloaded .dtd file to /dtd (use SCP/ftp or whatever method you prefer to get the file onto the system)
5. cd /opt/novell/common-service/webapps
6. jar xvf root.war
7. vi WEB-INF/tiles-template.xml
Change the “http://tiles.apache.org/dtds/tiles-config_2_1.dtd” entry to: “file:///dtd/tiles-config_2_1.dtd”
Note: if you used a different path other than /dtd, then use the appropriate path after file://
8. jar cvf root.war META-INF WEB-INF favicon.ico resources
9. reboot the appliance

Cause

This is a situtation where the appliance does not have internet access (secure environment) so the appliance can not/should not access http://tiles.apache.org/dtds/tiles-config_2_1.dtd in tiles-template.xml.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

Comparison Operators in Watson Discovery queries on data from Entity.text?

IBM Customer Leave a comment
Some entity types in my custom model will extract data that could be normalized/parsed as numeric. For example:

Budget of [$100k]
[60%] of respondents

Is there a way to normalize/parse this data so that comparison operators can be used in the Discovery query?

Same question for date. If creating Date, Time or Duration entities in a custom model, is there a way to query before, after, on, etc?

Related:

SEPM 14 Unabl to download definations (Very Weird)

Symantec Community Leave a comment
I need a solution

Hello everyone, I have SEPM 14 with SQL database which is unable to download the definations. Whenever we try run an luall.exe it connects to live update downoad few KBs and then the connection fails. Attached is the screenshot.

Tried couple of fixes for it. Uninstall and reinstalled back Live Update component. Also if we try to use jdb files for update it works and updates fine. SEPM is already whitelisted on the proxy server and the firewall.

Increased the time out values

PREFERENCESINTERNET_CONNECT_TIMEOUT=144
PREFERENCESINTERNET_READ_DATA_TIMEOUT=1400

as per https://support.symantec.com/en_US/article.TECH188847.html

Also ran wireshark and find out the below many 404 erros dont know what exactly is happening

GET http://liveupdate.symantecliveupdate.com/liveupdate_3.3.100.15_english_livetri.zip HTTP/1.1

Accept: */*

Cache-Control: max-age=0

User-Agent: x0o4rajcHBQ3y2u8fYRQV+rNNGAglDTWQAAAAA

Host: liveupdate.symantecliveupdate.com

Proxy-Connection: Keep-Alive

Pragma: no-cache

 

HTTP/1.1 404 Not Found

Cache-Control: max-age=600

Content-Type: text/html

Date: Tue, 03 Oct 2017 08:55:33 GMT

Expires: Tue, 03 Oct 2017 09:05:33 GMT

Server: ATS/5.3.1

Content-Length: 345

Age: 1

Connection: keep-alive

 

<?xml version=”1.0″ encoding=”iso-8859-1″?>

<!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Transitional//EN”

“http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd“>

<html xmlns=”http://www.w3.org/1999/xhtml” xml:lang=”en” lang=”en”>

<head>

<title>404 – Not Found</title>

</head>

<body>

<h1>404 – Not Found</h1>

</body>

</html>

GET http://liveupdate.symantecliveupdate.com/minitri.flg HTTP/1.1

Accept: */*

If-Modified-Since: Mon, 24 Jun 2013 23:51:06 GMT

Cache-Control: max-age=0

User-Agent: x0o4rajcHBQ3y2u8fYRQV+rNNGAglDTWQAAAAA

Host: liveupdate.symantecliveupdate.com

Proxy-Connection: Keep-Alive

Pragma: no-cache

 

HTTP/1.1 304 Not Modified

Date: Tue, 03 Oct 2017 08:55:33 GMT

Etag: “1813808236”

Expires: Tue, 03 Oct 2017 09:25:33 GMT

Cache-Control: max-age=1800

Connection: keep-alive

Server: ATS/5.3.1

 

GET http://liveupdate.symantecliveupdate.com/automatic$20liveupdate_3.3.100.15_english_livetri.zip HTTP/1.1

Accept: */*

Cache-Control: max-age=0

User-Agent: x0o4rajcHBQ3y2u8fYRQV+rNNGAglDTWQAAAAA

Host: liveupdate.symantecliveupdate.com

Proxy-Connection: Keep-Alive

Pragma: no-cache

 

HTTP/1.1 404 Not Found

Cache-Control: max-age=600

Content-Type: text/html

Date: Tue, 03 Oct 2017 08:55:39 GMT

Expires: Tue, 03 Oct 2017 09:05:39 GMT

Server: ATS/5.3.1

Content-Length: 345

Age: 2

Connection: keep-alive

 

<?xml version=”1.0″ encoding=”iso-8859-1″?>

<!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Transitional//EN”

“http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd“>

<html xmlns=”http://www.w3.org/1999/xhtml” xml:lang=”en” lang=”en”>

<head>

<title>404 – Not Found</title>

</head>

<body>

<h1>404 – Not Found</h1>

</body>

</html>

GET http://liveupdate.symantecliveupdate.com/sepm$20content$20catalog_14.0_symalllanguages_livetri.zip HTTP/1.1

Accept: */*

If-Modified-Since: Mon, 04 Sep 2017 15:38:53 GMT

Cache-Control: max-age=0

User-Agent: x0o4rajcHBQ3y2u8fYRQV+rNNGAglDTWQAAAAA

Host: liveupdate.symantecliveupdate.com

Proxy-Connection: Keep-Alive

Pragma: no-cache

 

HTTP/1.1 304 Not Modified

Date: Tue, 03 Oct 2017 08:55:39 GMT

Etag: “3589382957”

Expires: Tue, 03 Oct 2017 09:05:39 GMT

Cache-Control: max-age=600

Connection: keep-alive

Server: ATS/5.3.1

 

GET http://liveupdate.symantecliveupdate.com/sepm$20liveupdate$20database_14.0_symalllanguages_livetri.zip HTTP/1.1

Accept: */*

Cache-Control: max-age=0

User-Agent: x0o4rajcHBQ3y2u8fYRQV+rNNGAglDTWQAAAAA

Host: liveupdate.symantecliveupdate.com

Proxy-Connection: Keep-Alive

Pragma: no-cache

 

HTTP/1.1 404 Not Found

Cache-Control: max-age=600

Content-Type: text/html

Date: Tue, 03 Oct 2017 08:55:39 GMT

Expires: Tue, 03 Oct 2017 09:05:39 GMT

Server: ATS/5.3.1

Content-Length: 345

Age: 0

Connection: keep-alive

Any help would be appreciated.

0

Related:

When there are CDATA section in my XML input, why the CDATA tag is eliminated and “

IBM Customer Leave a comment
When there are CDATA section in my XML input, why the CDATA tag is eliminated and ”

….

Output becomes:

<?xml version=”1.0″ encoding=”UTF-8″ ?>
<myType type=”CHAR” /> ….

Related:

IIB 10.0 – Using ESQL to create xmlsc document with namespace turns attributes into elements

IBM Customer Leave a comment
I am using ESQL to create a XMLNSC document that has a namespace. When I do this, attributes are turned into elements causing the xml to be invalid. Below is the code to create the document in ESQL.

BEGIN
DECLARE pendingDownstreamService REFERENCE to Environment.Variables.PENDING_DOWNSTREAM_SERVICES[1];
DECLARE wd NAMESPACE ‘urn:com.workday/bsvc’;
DECLARE employeeIdAsText CHARACTER;
DECLARE employeeIdToStartDate ROW;
DECLARE employeeCount INTEGER 1;

CALL CopyMessageHeaders();
CALL CopyEntireMessage();

SET OutputRoot.XMLNSC.wd:Get_Workers_Request.(XMLNSC.NamespaceDecl)xmlns:”wd” = ‘urn:com.workday/bsvc’;
SET OutputRoot.XMLNSC.wd:Get_Workers_Request.(XMLNSC.Attribute)wd:version = ‘v26.2’;
SET OutputRoot.XMLNSC.wd:Get_Workers_Request.wd:Response_Group.wd:Include_Employment_Information = ‘true’;

WHILE lastmove(pendingDownstreamService) DO
IF (pendingDownstreamService.EMPLOYEE_ID IS NOT NULL) THEN
SET employeeIdAsText = CAST(pendingDownstreamService.EMPLOYEE_ID AS CHARACTER);
IF (employeeIdToStartDate.{employeeIdAsText} IS NULL) THEN
SET OutputRoot.XMLNSC.wd:Get_Workers_Request.wd:Request_References.wd:Worker_Reference[employeeCount].wd:ID.(XMLNSC.Attribute)wd:type=’Employee_ID’;
SET OutputRoot.XMLNSC.wd:Get_Workers_Request.wd:Request_References.wd:Worker_Reference[employeeCount].wd:ID VALUE = pendingDownstreamService.EMPLOYEE_ID;

SET employeeIdToStartDate.{employeeIdAsText} = pendingDownstreamService.START_DATE;
SET employeeCount = employeeCount + 1;
END IF;
END IF;

MOVE pendingDownstreamService NEXTSIBLING;
END WHILE;

RETURN TRUE;
END;
![alt text][1]

Attached is the message from the flow recorder. You can see that the Get_Workers_Request element has version as a child element while the esql code adds the version as an attribute. Additionally, the wd:Get_Workers_Request.wd:Request_References.wd:Worker_Reference.wd:ID element has type as a child element while the esql adds type as an atttribute. I also don’t see the namespace declaration attribute in the Get_Workers_Request element so I am not sure if that is a problem as well. I would expect to see something like

in the flow recorder.

How can I add attributes to an XMLNSC document when using namespaces?

[1]: /answers/storage/temp/16366-get-workers.png

Related:

IIB 10 – Handling XML that is not well formed

IBM Customer Leave a comment
I have an MQInput node that reads an xml message from the queue. I am trying to handle the condition when we get a malformed xml document or an invalid xml document but it doesn’t behave as expected. There is no exception thrown and the path proceeds along the out terminal instead of the failure terminal. The ExceptionList is empty so there is no way to get any information about the parse error.

How does one handle an xml parse error when an xml message is not well formed or an xml validation error when an xml message is not valid? How can I determine the error happened and what the error is?

Related:

How to train Watson for NLU efficiently ?

IBM Customer Leave a comment
I trained Watson for some entities in Knowledge Studio but it shows the response only for one entity even though in a single text there are many entities for which I trained and it also does not show the entities for which Watson has been already trained for.
How can I get the response containing all the entities ?

Related:

Rob_Smith011111 created a topic named Can you help me solve my Xml Parsing Error so I can open my Microsoft Word 2016 file? in the Thinking XML forum forum.

IBM Leave a comment

Related:

Why are the XML special characters (e.g. ) inside of CDATA sections converted to their escaped equivalent (e.g. ) during BPM Business Object serialization?

IBM Customer Leave a comment
Why are the XML special characters (e.g. ) inside of CDATA sections converted to their escaped equivalent (e.g. `< , >`) during BPM Business Object serialization?

For example:

…..
is converted to:

<![CDATA[<?xml version=”1.0″ encoding=”UTF-8″ ?>
< myType type=”CHAR” />
….

Related: