IIB V10 SOAP Request node throws UnsupportedEncodingException: ibm-5348

Looking for help interpreting the Exception message.
I read a file with the FileInput node and consume a SOAP web service with a SOAP Request node.

The data coming out of the “Failure” terminal of the SOAP Request is,
![alt text][1]

The Exception is,
Frame : 0 javax.xml.stream.XMLStreamException: java.io.UnsupportedEncodingException: ibm-5348

Any help pointing me in the right direction is appreciated.

[1]: /answers/storage/temp/25740-soap.png

Related:

SEPM trigger remote scan with API

I need a solution

I am creating python code to trigger a remote scan on a computer using this API.

       https://apidocs.symantec.com/home/saep#_run_a_scan…

I am wondering if there is any way to do this without Advanced Threat Protection.  Something like setting the date on the computer as having an out of date scan so it triggers SEPM to start another scan on its own.

Also, the documentaion references the eoc.wsdl

       “The evidence of compromise command in XML. See eoc.xsd in the Remote Management and Monitoring documentation for the proper     format.”

I am having trouble finding this wsdl file.  Can anyone help me find it?  I have searched extensivly for Remote Management and Monitoring documentation but have not found the eoc.xsd.

0

1536249554

Related:

Re: Recovery Point for VM Failover through REST

Hi All,

Need a suggestion on Failing over VM through the REST API in RP4VM.Any leeds on it will be very helpful.

I came across the following :

1.The CLI might not be having all the functionalities

2.The API functionalities I came across in the Programming guide either does not cover all operations or might not be stated in the document.

3.We have the Swagger link , where we can test the Requests made : https://<ip>/deployer/swagger/#

4.There are two versions of the API i think : FAPI and deployer (however the FAPI contains methods like failover as i was searching online) and deployer contains more or less the same methods as in swagger. The Fapi documentation is old and for 4.0 , while deployer i could get for 5.1.

Question : How can we failover using the REST API ,present verion we are using is 5.1 , if you can mention the method and the wsdl/wadl , it would be great help.

Related:

Re: SRDF conversion from FC to IP

Create a separate RDFG for your RE ports and then perform a movepair operation to get your devices from the RF RDFG across to the RE RDFG. You will need to suspend RDF first, but it’s not a re-synch of the data:

symrdf -sid 001 addgrp -label RE_RF -rdfg 109 -dir 9g:0,7e:0 -remote_rdfg 109 -remote_dir 9g:0,7e:0 -remote_sid 002

Execute a Dynamic RDF Addgrp operation for group

‘RE_RF’ on Symm: 0001 (y/[n]) ? y

The RDF directors specified to support the dynamic RDF group are not the same type

Related:

SRDF conversion from FC to IP

Create a separate RDFG for your RE ports and then perform a movepair operation to get your devices from the RF RDFG across to the RE RDFG. You will need to suspend RDF first, but it’s not a re-synch of the data:

symrdf -sid 001 addgrp -label RE_RF -rdfg 109 -dir 9g:0,7e:0 -remote_rdfg 109 -remote_dir 9g:0,7e:0 -remote_sid 002

Execute a Dynamic RDF Addgrp operation for group

‘RE_RF’ on Symm: 0001 (y/[n]) ? y

The RDF directors specified to support the dynamic RDF group are not the same type

Related:

Re: Create comment in a discussion topic

I’m using the standard create XML which comes with the XML api kit but the create xml doesnot seem to work is there anything missing..

<?xml version=”1.0″ encoding=”UTF-8″ ?>

<SOAP-ENV:Envelope xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/” SOAP-ENV:encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/”>

<SOAP-ENV:Body>

<er:ExecuteXMLCommand xmlns:er=”http://www.eroom.com/eRoomXML/2003/700″ xmlns:xsi=”http://www.eroom.com/eRoomXML/2003/700/XMLSchema-instance”>

<er:eRoomXML>

<er:command er:select=”Rooms/Room[URLName=’OCIOManagement’]/HomePage/Items/Item[Name=’Discussion Forum’]/Items/Item[Name=’Classification of dti users’]”>

<er:create>

<er:Item xsi:type=”erItemTypeComment”>

<er:Name>A comment on Topic2</er:Name>

</er:Item>

</er:create>

</er:command>

</er:eRoomXML>

</er:ExecuteXMLCommand>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

Related:

Re: When can a SnapVX establish -both_sides option be used on an SRDF/A device group?

When can a SnapVX establish -both_sides command be used on an SRDF/A device group?

When attempting said establish command, we get a invalid RDF state error, see below in red:

When querying the device group, it shows the RDF state as being consistent, see below in red:

symsnapvx -g “SDG02Srdf_Drclive” -name “VXW_BACPRE-Archive-Pre” -noprompt establish -both_sides

Establish operation execution is in progress for the device group SDG02Srdf_Drclive. Please wait…

The device is not in a valid RDF state for this operation

symrdf -g “SDG02Srdf_Drclive” query

Device Group (DG) Name : SDG02Srdf_Drclive

DG’s Type : RDF1

DG’s Symmetrix ID : 000197700110 (Microcode Version: 5977)

Remote Symmetrix ID : 000197700111 (Microcode Version: 5977)

RDF (RA) Group Number : 242 (F1)

Source (R1) View Target (R2) View MODE

——————————— ———————— —- ————

ST LI ST

Standard A N A

Logical Sym T R1 Inv R2 Inv K Sym T R1 Inv R2 Inv RDF Pair

Device Dev E Tracks Tracks S Dev E Tracks Tracks MACE STATE

——————————— — ———————— —- ————

DEV001 007A8 RW 0 0 RW 005C8 WD 0 0 A.X. Consistent

DEV002 007A9 RW 0 0 RW 005C9 WD 0 0 A.X. Consistent

DEV003 007AA RW 0 0 RW 005CA WD 0 0 A.X. Consistent

DEV004 007AB RW 0 0 RW 005CB WD 0 0 A.X. Consistent

DEV005 007AC RW 0 0 RW 005CC WD 0 0 A.X. Consistent

DEV006 007F3 RW 0 0 RW 00613 WD 0 0 A.X. Consistent

Total ——- ——- ——- ——-

Track(s) 0 0 0 0

MB(s) 0.0 0.0 0.0 0.0

Legend for MODE:

(M)ode of Operation : A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy

: M = Mixed, T = Active

(A)daptive Copy : D = Disk Mode, W = WP Mode, . = ACp off

(C)onsistency State : X = Enabled, . = Disabled, M = Mixed, – = N/A

Consistency (E)xempt: X = Enabled, . = Disabled, M = Mixed, – = N/A

symdg show “SDG02Srdf_Drclive”

Group Name: SDG02Srdf_Drclive

Group Type : RDF1 (RDFA)

Device Group in GNS : No

Valid : Yes

Symmetrix ID : 000197700110

Group Creation Time : Tue Apr 3 14:32:58 2018

Vendor ID : EMC Corp

Application ID : SYMCLI

Number of STD Devices in Group : 6

Number of Locally-associated BCV’s : 0

Number of Locally-associated VDEV’s : 0

Number of Locally-associated TGT’s : 0

Number of Remotely-associated VDEV’s(STD RDF): 0

Number of Remotely-associated BCV’s (STD RDF): 0

Number of Remotely-associated TGT’s(TGT RDF) : 0

Number of Remotely-associated BCV’s (BCV RDF): 0

Number of Remotely-assoc’d RBCV’s (RBCV RDF) : 0

Number of Remotely-assoc’d BCV’s (Hop-2 BCV) : 0

Number of Remotely-assoc’d VDEV’s(Hop-2 VDEV): 0

Number of Remotely-assoc’d TGT’s (Hop-2 TGT) : 0

Number of Composite Groups : 0

Composite Group Names : N/A

Standard (STD) Devices (6):

{

———————————————————————————–

Sym Device Cap

LdevName PdevName Dev Config Att. Sts (MB)

———————————————————————————–

DEV001 /dev/sdgy 007A8 RDF1+TDEV RW 9218

DEV002 /dev/sdgz 007A9 RDF1+TDEV RW 9218

DEV003 /dev/sdha 007AA RDF1+TDEV RW 9218

DEV004 /dev/sdhb 007AB RDF1+TDEV RW 9218

DEV005 /dev/sdhc 007AC RDF1+TDEV RW 9218

DEV006 /dev/sdjv 007F3 RDF1+TDEV RW 9218

}

Device Group RDF Information

{

RDF Type : R1

RDF (RA) Group Number : 242 (F1)

Remote Symmetrix ID : 000197700111

Number of Storage Groups : 0

Storage Group Names : N/A

R2 Device Is Larger Than The R1 Device : False

Paired with a Diskless Device : False

Paired with a Concurrent Device : False

Paired with a Cascaded Device : False

Thick Thin Relationship : False

RDF Pair Configuration : Normal

RDF STAR Mode : False

RDF SQAR Mode : False

RDF Mode : Asynchronous

RDF Adaptive Copy : Disabled

RDF Adaptive Copy Write Pending State : N/A

RDF Adaptive Copy Skew (Tracks) : 16383

RDF Device Domino : Disabled

RDF Link Configuration : Fibre

RDF Link Domino : Disabled

Prevent Automatic RDF Link Recovery : Enabled

Prevent RAs Online Upon Power ON : Enabled

Device RDF Status : Ready (RW)

Device RA Status : Ready (RW)

Device Link Status : Ready (RW)

Time of Last Device Link Status Change : N/A

Device Suspend State : N/A

Device Consistency State : Enabled

Device Consistency Exempt State : Disabled

RDF R2 Not Ready If Invalid : Disabled

Write Pacing Information

{

Pacing Capable : Yes

Configured Group-level Exempt State: Disabled

Effective Group-level Exempt State : Disabled

Group-level Pacing State : Disabled

Device-level Pacing State : N/A

}

Device RDF State : Ready (RW)

Remote Device RDF State : Write Disabled (WD)

RDF Pair State ( R1 <===> R2 ) : Consistent

Number of R1 Invalid Tracks : 0

Number of R2 Invalid Tracks : 0

RDFA Information:

{

Session Number : 241

Cycle Number : 11582

Number of Devices in the Session : 6

Session Status : Active

Consistency Exempt Devices : No

Session Consistency State : Enabled

Minimum Cycle Time : 00:00:15

Average Cycle Time : 00:00:15

Average Transmit Cycle Time : 00:00:15

Transmit Queue Depth on R1 Side : 1

Tracks not Committed to the R2 Side: 0

Time that R2 is behind R1 : 00:00:16

R2 Image Capture Time : Thu May 3 17:43:46 2018

R2 Data is Consistent : True

R1 Side Percent Cache In Use : 0

R2 Side Percent Cache In Use : 0

Transmit Idle Time : 00:00:00

R1 Side DSE Used Tracks : 0

R2 Side DSE Used Tracks : 0

R1 Side Shared Tracks : 0

}

}

Related:

Question Mark(?) is not Supported in NetScaler CLI

When running a command with question mark in the NetScaler CLI the question mark is removed.

Example command:

add lb monitor http-cmmvk-80 HTTP-ECV -send “GET /ConnectMVKWS_CancelBooking/mvkservice_CancelBooking?wsdl” -LRTM ENABLED -destPort 8080

If you copy and paste the above command in to a CLI session you will get the following result:

CLI1


If you run the same command via MAS or another automation tool the URL is set but it removes the “?” in the path.

However in MAS the report shows the right command with “?” but it is in fact set without it.

MAS Config Job report example:

MAS Report

NS GUI example after running the above job:

NSGUI
Notice that the “?” is missing from the config.

Adding the “?” via the GUI and the result from ns.log:

Mar 13 11:29:09 192.168.0.14 03/13/2018:10:29:09 GMT ns 0-PPE-0 : default GUI CMD_EXECUTED 739029 0 : User nsroot – Remote_ip 10.8.0.6 – Command “set lb monitor http-cmmvk-80 HTTP-ECV -send “GET /ConnectMVKWS_CancelBooking/mvkservice_CancelBooking?wsdl” -LRTM ENABLED -interval 5 SEC -resptimeout 2 SEC -resptimeoutThresh 0 -retries 3 -failureRetries 0 -alertRetries 0 -successRetries 1 -downTime 30 SEC -destPort 8080 -state ENABLED -reverse NO -transparent NO -ipTunnel NO -tos NO -secure NO -storefrontcheckbackendservices NO” – Status “Success”

The same issue can be seen in other CLI commands like this for AppFW:

bind appfw profile Test2 -denyURL “^[^?]*/winnt/”

The commands with ? are stored in ns.conf as expected.

Related:

When can a SnapVX establish -both_sides option be used on an SRDF/A device group?

When can a SnapVX establish -both_sides command be used on an SRDF/A device group?

When attempting said establish command, we get a invalid RDF state error, see below in red:

When querying the device group, it shows the RDF state as being consistent, see below in red:

symsnapvx -g “SDG02Srdf_Drclive” -name “VXW_BACPRE-Archive-Pre” -noprompt establish -both_sides

Establish operation execution is in progress for the device group SDG02Srdf_Drclive. Please wait…

The device is not in a valid RDF state for this operation

symrdf -g “SDG02Srdf_Drclive” query

Device Group (DG) Name : SDG02Srdf_Drclive

DG’s Type : RDF1

DG’s Symmetrix ID : 000197700110 (Microcode Version: 5977)

Remote Symmetrix ID : 000197700111 (Microcode Version: 5977)

RDF (RA) Group Number : 242 (F1)

Source (R1) View Target (R2) View MODE

——————————— ———————— —- ————

ST LI ST

Standard A N A

Logical Sym T R1 Inv R2 Inv K Sym T R1 Inv R2 Inv RDF Pair

Device Dev E Tracks Tracks S Dev E Tracks Tracks MACE STATE

——————————— — ———————— —- ————

DEV001 007A8 RW 0 0 RW 005C8 WD 0 0 A.X. Consistent

DEV002 007A9 RW 0 0 RW 005C9 WD 0 0 A.X. Consistent

DEV003 007AA RW 0 0 RW 005CA WD 0 0 A.X. Consistent

DEV004 007AB RW 0 0 RW 005CB WD 0 0 A.X. Consistent

DEV005 007AC RW 0 0 RW 005CC WD 0 0 A.X. Consistent

DEV006 007F3 RW 0 0 RW 00613 WD 0 0 A.X. Consistent

Total ——- ——- ——- ——-

Track(s) 0 0 0 0

MB(s) 0.0 0.0 0.0 0.0

Legend for MODE:

(M)ode of Operation : A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy

: M = Mixed, T = Active

(A)daptive Copy : D = Disk Mode, W = WP Mode, . = ACp off

(C)onsistency State : X = Enabled, . = Disabled, M = Mixed, – = N/A

Consistency (E)xempt: X = Enabled, . = Disabled, M = Mixed, – = N/A

symdg show “SDG02Srdf_Drclive”

Group Name: SDG02Srdf_Drclive

Group Type : RDF1 (RDFA)

Device Group in GNS : No

Valid : Yes

Symmetrix ID : 000197700110

Group Creation Time : Tue Apr 3 14:32:58 2018

Vendor ID : EMC Corp

Application ID : SYMCLI

Number of STD Devices in Group : 6

Number of Locally-associated BCV’s : 0

Number of Locally-associated VDEV’s : 0

Number of Locally-associated TGT’s : 0

Number of Remotely-associated VDEV’s(STD RDF): 0

Number of Remotely-associated BCV’s (STD RDF): 0

Number of Remotely-associated TGT’s(TGT RDF) : 0

Number of Remotely-associated BCV’s (BCV RDF): 0

Number of Remotely-assoc’d RBCV’s (RBCV RDF) : 0

Number of Remotely-assoc’d BCV’s (Hop-2 BCV) : 0

Number of Remotely-assoc’d VDEV’s(Hop-2 VDEV): 0

Number of Remotely-assoc’d TGT’s (Hop-2 TGT) : 0

Number of Composite Groups : 0

Composite Group Names : N/A

Standard (STD) Devices (6):

{

———————————————————————————–

Sym Device Cap

LdevName PdevName Dev Config Att. Sts (MB)

———————————————————————————–

DEV001 /dev/sdgy 007A8 RDF1+TDEV RW 9218

DEV002 /dev/sdgz 007A9 RDF1+TDEV RW 9218

DEV003 /dev/sdha 007AA RDF1+TDEV RW 9218

DEV004 /dev/sdhb 007AB RDF1+TDEV RW 9218

DEV005 /dev/sdhc 007AC RDF1+TDEV RW 9218

DEV006 /dev/sdjv 007F3 RDF1+TDEV RW 9218

}

Device Group RDF Information

{

RDF Type : R1

RDF (RA) Group Number : 242 (F1)

Remote Symmetrix ID : 000197700111

Number of Storage Groups : 0

Storage Group Names : N/A

R2 Device Is Larger Than The R1 Device : False

Paired with a Diskless Device : False

Paired with a Concurrent Device : False

Paired with a Cascaded Device : False

Thick Thin Relationship : False

RDF Pair Configuration : Normal

RDF STAR Mode : False

RDF SQAR Mode : False

RDF Mode : Asynchronous

RDF Adaptive Copy : Disabled

RDF Adaptive Copy Write Pending State : N/A

RDF Adaptive Copy Skew (Tracks) : 16383

RDF Device Domino : Disabled

RDF Link Configuration : Fibre

RDF Link Domino : Disabled

Prevent Automatic RDF Link Recovery : Enabled

Prevent RAs Online Upon Power ON : Enabled

Device RDF Status : Ready (RW)

Device RA Status : Ready (RW)

Device Link Status : Ready (RW)

Time of Last Device Link Status Change : N/A

Device Suspend State : N/A

Device Consistency State : Enabled

Device Consistency Exempt State : Disabled

RDF R2 Not Ready If Invalid : Disabled

Write Pacing Information

{

Pacing Capable : Yes

Configured Group-level Exempt State: Disabled

Effective Group-level Exempt State : Disabled

Group-level Pacing State : Disabled

Device-level Pacing State : N/A

}

Device RDF State : Ready (RW)

Remote Device RDF State : Write Disabled (WD)

RDF Pair State ( R1 <===> R2 ) : Consistent

Number of R1 Invalid Tracks : 0

Number of R2 Invalid Tracks : 0

RDFA Information:

{

Session Number : 241

Cycle Number : 11582

Number of Devices in the Session : 6

Session Status : Active

Consistency Exempt Devices : No

Session Consistency State : Enabled

Minimum Cycle Time : 00:00:15

Average Cycle Time : 00:00:15

Average Transmit Cycle Time : 00:00:15

Transmit Queue Depth on R1 Side : 1

Tracks not Committed to the R2 Side: 0

Time that R2 is behind R1 : 00:00:16

R2 Image Capture Time : Thu May 3 17:43:46 2018

R2 Data is Consistent : True

R1 Side Percent Cache In Use : 0

R2 Side Percent Cache In Use : 0

Transmit Idle Time : 00:00:00

R1 Side DSE Used Tracks : 0

R2 Side DSE Used Tracks : 0

R1 Side Shared Tracks : 0

}

}

Related:

Modification of Application Schema in Infoarchive

Article Number: 501357 Article Version: 3 Article Type: How To



InfoArchive 4.3,InfoArchive 4.2,InfoArchive 4.1,InfoArchive 4.0

In order to add support for new version of xsd schema for an existing holding, so that the field is searched, follow steps:

1. Add new “120-pdi-schema.xml” object.

2. Add new “pdiConfig” for a “170-holding.xml”

3. Add new “190-aic.xml” and “220-query.xml”.

4. Modify “pdi.xml” with indexes definition, so that new ingested sips are processed in accordance to the new pdi.xml and indexes are created for this new SIP for new schema.

For example please see modified Invoices sample application, that shows how to support two schema within the single holding.

For assistance on custom Application Schema modification please engage Professional Services.

Related: