Troubleshooting eText Integration Issues



[pic]

October 7, 2011

Troubleshooting eText Integration Issues

Erik Unhjem

eText Systems Product Manager

Content Management Services / Pearson Education

Erik.Unhjem@

Office: 201-236-7214

Cell: 845-551-8508

Follow these steps if an eText has been recently published to the live Viewer and an error message is received while trying the access the eText from another platform:

1. Verify that the eText has been published. Links to the final product will not work unless the eText is published to the live (published) Viewer with the appropriate integration scenarios enabled. Ask Website Release (WebsiteRelease@) to double-check the SMS/RUMBA page in the eText Authoring tool to make sure that the correct Site IDs have been obtained for each of the desired integration scenarios and that the eText has been published with the correct SMS Module IDs or RUMBA Resource IDs (as appropriate) for all of the required integration scenarios.

2. For HE/PLS/International eTexts, go to and log in to see the SMS summary of the account being used. Check to see if a subscription to the other platform and the appropriate eText are BOTH contained in the summary, and search for the SMS Module ID(s) used to publish the eText. Access to newly published eTexts through “bookbag” type accounts is added manually and may lag publishing of the eText by days or even weeks. The overwhelming majority of eText access issues can be attributed to incorrect or incomplete SMS configuration.

3. For School eTexts, verify that configuration of the RUMBA Resource ID is correct. Contact Sara.Baldwin@ for more information.

4. LTI links and links from PSN+, eCollege and MathXL are programmatic and generated by those platforms. Triple-check the eText parameters entered into those platforms, looking for any errant characters or spaces in the links. Try to capture and then examine the links as they transform in the browser URL window.

5. Review the links to your eText to insure that links point to the live Viewer — ie the URL begins with "view." -- not "auth." (A URL beginning with "auth." is pointing to the Authoring server.) Make sure there are no errant characters or spaces in the links.

6. Check to make sure that the link indicates the appropriate Integration Scenario. The ‘linktoeText’ part of the URL indicates the Integration Scenario. For example, this link is for Scenario 5:

7. Check to make sure that the Platform ID in your link matches the Platform ID provided by your eText Production Project Manager. The Platform ID is bolded in this sample link:

8. Check to make sure that the Book ID in your link matches the Book ID provided by your eText Production Project Manager or production vendor. The Book ID is bolded in this sample link:

9. If using Integration Scenario 2, make sure that a courseid is included in the link (coursename is optional). For example:

If using Integration Scenario 3, make sure that a courseid and token is included in the link. For example: &courseid=xyz&token=abcd

If using Integration Scenarios 4 or 6, make sure that there are startpage, endpage and hid parameters and values, and that the start page actually precedes the end page in the eText. For example:

If all of the above steps are followed and no errors are found, post a query to the Pearson Knowledge Base at .

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download