Home > Integrating > General Information
Theoretically, the WSI interface allows complete access to your store database, which may include sensitive data. Adherence to proper security practices defined here are mandatory for proper deployment and usage.
When using WSE3 Authenticated invocation of WSI from your client program, you must use the Admin Email and HASHED Password from the master AspDotNetStorefront database! You cannot put the password in clear text in the client. It must be the hashed raw value from the storefront database! If you are using the NON WSE3 invocation, you use the clear text password for the admin user.
WSI is not really designed to import massive amounts of products, entities, or customers in a single 'pass'. While this import option can handle more at once than the standard Excel product import, we still recommend that imports be done & reviewed incrementally, and that transactions be used.
See this page for more information on Transaction nodes.
The Excel import tool is actually running through WSI. While the Excel tool will continue to function, we highlyrecommend that store owners switch to using the WSI feature instead. Though more complicated to set up, it is far more flexible, can import every field rather than the limited data set supported by the Excel import, and supports larger imports.
There is also a ResetCache processing node element in the WSI that you can include in your Xml import document that can also do this automatically. Do not execute that action too often via WSI however, or it may negatively affect your store performance by clearing the cache too frequently.
System.Web.Services.Protocols.SoapHeaderException: SOAP header Security was not understood...
This means that you have not followed all of the installation steps to properly enable your web site to use WSE3. Verify that you have added the web.config elements, that WSE3 is installed on the server, and that you have all the proper WSI class files on your web site.
Invalid security header on WSI calls
This means that you are not using time synchronization (a Windows function) on your client and web site servers. Time sync MUST be used on both machines, or SOAP calls will not work. Please see your host or IT manager for assistance with enabling time sync.