To help your implementation of the Web Services Kit meet your organization's unique requirements, each implementation is managed as a project consisting of the following four phases:
The team will verify that each phase's activities have been performed
properly and determine when the project is ready to move to the next phase.
This project team will not:
The project team's goal is simply to make certain :
To these ends, your LexisNexis account representative and technical support contact will be available throughout the process to answer your questions as your applications mature.
Before a project team is formed, you will work with your LexisNexis Account Representative to clarify your organization's needs and to propose recommended solutions. During these interactions, you review design options, such as the data hosting feature described below. You may even determine that a different LexisNexis Research Service solution would work better for you.
If, however, you determine that the LexisNexis Web Services Kit is the appropriate solution, you will be asked to sign a trial agreement.
This will allow you to investigate the WSK's further without making a long-term commitment.
Discovery Phase Activities
After a trial agreement has been signed, a project team for your implementation is formed. You will then be given an ID and password that lets your developers access the secured areas of this site so they can review this API's capabilities in more detail. They will also be provided with WSDL files, an endpoint URL, and limited access to the Web Services Kit's Customer Certification server.
The primary objective of this phase is for LexisNexis to understand your needs and migration plans. A LexisNexis representative will work with you to clarify this information and document it in a Scope document for this project. When this document is ready, the project team will review it to determine if your intended implementation is feasible. If it is, the project moves to the next phase.
Note: To reduce the chance of unnecessary complications due to switching development areas (and WSDL files) during development, your team will be given new endpoint URLs as needed along with any necessary IDs and passwords. This allows you to manually adjust the WSDL file to point to the appropriate Web Services Kit API's Customer Certification, Customer Pre-Production, or Production server.
During this phase, LexisNexis support personnel will quickly respond to your emails and
- if necessary - contact you by phone to answer your questions. Eventually, test runs
will be set up to check your applications and their impact on the LexisNexis system under load conditions.
Compliance Phase Activities
When you feel that you are ready for the initial rollout of your application, you give the LexisNexis project team access to your Web Services Kit applications so they can:
In most cases, since the development team and Web Services Kit project team have been working together, the compliance phase goes very smoothly.
Rollout Phase Activities
Once the compliance reviews have successfully completed, your team will be provided with the Production server endpoint URL and IDs and passwords for your users. You will probably want to train your applications users and to keep development resources available for the first few weeks after rollout. But the value and usefulness of a carefully-designed solution is usually apparent the first day.
The Web Services Kit throttling mechanism looks for ...
Under normal conditions, your implementation should never be impacted by this throttling mechanism. Most threshold levels are determined for each implementation based on the estimated average work flow plus a generous addition to cover potential peak periods. As activity nears a threshold level, customer support is alerted so that they can investigate.
Issues causing unexpected peaks in usage can include:
If the unexpected activity increase is simply due to an increase in normal usage, the threshold levels for the various activities can be adjusted or even suspended, on a per installation or per user basis, for a period of time.
If service needs to be suspended, the timeframe of that suspension can vary. For example if the number of concurrent requests limit is reached, additional requests will be denied until the other requests finish processing and the number falls below the threshold level. However if the total number of requests for service within an hour is reached, service would be suspended for the remainder of that monitoring period.
If you have additional questions about this throttling mechanism, please contact Web Services Kit Technical Support at LexisNexis.
About the Data Hosting Feature
Your organization may have the requirement to host certain LexisNexis documents or document collections on your local server. These may be documents that your people access frequently or that you want to integrate in some way into your local systems. They may include:
In such cases, you may be able to arrange with LexisNexis to use the WSK to download the documents you want to host locally. The ability to host documents is dependent on the content set you require, the information vendors involved and the time period for which you wish to retain the documents on your servers. You will not be able to host documents indefinitely, however you may be able to arrange for a rolling archive, e.g. 90 days, after which you discard the oldest documents from your servers.
Data hosting arrangements require a separate agreement with LexisNexis in order to protect the rights of our information vendors. LexisNexis will consider each request on an individual basis and, if approved, will draw up the necessary agreement.
LexisNexis is required to pay our information vendors royalties on resources that our customers access. As a result when you host a document on your site you are required to track the number of times that document is accessed internally by your users. You must then use the ReportDocumentUse operation to periodically report the usage back to LexisNexis. More detail on ReportDocumentUse can be found in the Developer's Guide section of this site.
Note: Since most sources are covered by an organization's subscription agreement, these access counts should not impact the invoice your organization receives. However, some sources that are considered premium may be outside the boundaries of the subscription. In these cases, those counts would be used to calculate additional charges just as though those documents were accessed directly from the LexisNexis Research Services.