Testing the MSX-A Setup

The domain considerations already mentioned increase the complexity of testing the connectivity setup. Since most of these issues arise in the setup and configuration of the MSX-A component, a separate test application is shipped with the connectivity. This test application allows you to check that the setup is correct.

 

1. Locate SAPPXchText.exe.This is shipped with the Exchange transport. The components can be found at <irj>\root\portalapps\com.sap.netweaver.coll.appl.gw\WEB-INF\external\exchange.
2. Copy the executable file to the machine on which the MSX-A component has been deployed.
3. Test the CDOversion:
   • Launch the executable file on the machine on which MSX-A was deployed.
   • Choose Test → CDOVersion.
   • You should receive a success message. If you receive an error message, follow the instructions given.
4. Test data retrieval:
   • Launch the executable file on the machine on which MSX-A was deployed.
   • Choose Test → Data Retrieval.
   • Fill in the necessary fields. Mandatory fields are indicated by a red asterisk (*). Click on the question mark (?) next to each field for more information.
   • You should receive a success message. If you receive an error message, follow the instructions given.
   • Click on Save Results. Open the log file indicated by the message. The log file should have the following structure:

 

------ BEGIN 5/27/2004 6:20:29 PM----------

URL: HTTP://<IIS Server>:<Port>/<Virtual directory>/Calendar.asp

URL Parameters: Server=<IIS Server>9B78SAPCE759E22F815Alias=<mailbox-alias>9B78SAPCE759E22F815Action=READ9B78SAPCE759E22F815StartDate=2004052600009B78SAPCE759E22F815EndDate=2004052700009B78SAPCE759E22F815Subject=9B78SAPCE759E22F815recipients=9B78SAPCE759E22F815Debug=true

 

Reponse: <?xml version='1.0' encoding='UTF-8' standalone='yes'?>

<!DOCTYPE OUTPUT [<!ELEMENT OUTPUT (FAILURE|APPOINTMENTS)>

<!ELEMENT FAILURE (ERRORNUMBER, ERRORMESSAGE, CLASSNAME, METHODNAME, LINENUMBER)>

<!ELEMENT ERRORNUMBER (#PCDATA)>

<!ELEMENT ERRORMESSAGE (#PCDATA)>

<!ELEMENT CLASSNAME (#PCDATA)>

<!ELEMENT METHODNAME (#PCDATA)>

<!ELEMENT LINENUMBER (#PCDATA)>

<!ELEMENT APPOINTMENTS (APPOINTMENT*)>

<!ELEMENT APPOINTMENT (ID, SUBJECT?, LOCATION?, STARTDATE, ENDDATE, MEETINGTYPE, ALLDAY, RECURRING, BUSYSTATUS?)>

<!ELEMENT ID (#PCDATA)>

<!ELEMENT SUBJECT (#PCDATA)>

<!ELEMENT LOCATION (#PCDATA)>

<!ELEMENT STARTDATE (#PCDATA)>

<!ELEMENT ENDDATE (#PCDATA)>

<!ELEMENT MEETINGTYPE (#PCDATA)>

<!ELEMENT ALLDAY (#PCDATA)>

<!ELEMENT RECURRING (#PCDATA)>

<!ELEMENT BUSYSTATUS (#PCDATA)>]><OUTPUT><APPOINTMENTS><APPOINTMENT><ID>FF000000ED0392EFA5B91B10ACC100AA004233260200000046000000000000000000000001000000000000004A4968F56F0A984590C989C21D5F667707002FDE54BDD3ADD611B8FE0008025619F00000003CDB6E00002FDE54BDD3ADD611B8FE0008025619F0000005F6FB050000</ID><SUBJECT><![CDATA[MS Integration]]></SUBJECT><LOCATION><![CDATA[CG R05]]></LOCATION><STARTDATE>200405260730</STARTDATE><ENDDATE>200405260830</ENDDATE><MEETINGTYPE>3</MEETINGTYPE><ALLDAY>False</ALLDAY><RECURRING>False</RECURRING><BUSYSTATUS>2</BUSYSTATUS></APPOINTMENT>

</APPOINTMENTS></OUTPUT>

------ END 5/27/2004 6:20:29 PM----------

Related SAP Notes: