Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Each of the configuration forms has its own unique configurations schema and xml file, so when exported it can only be imported by the same form. The default configuration is installed during the initial execution of the NoahWsiSetup exe, where the default settings files are imported. The settings files are saved in the Noah WSI db repository.

Each of the configuration forms has a delete button and an export button. The delete button will delete your current settings. You can export your configuration by the use of the Export button. If no settings are defined and stored in the Noah WSI db repository for a configuration part, e.g web service settings, the user will be prompt for an xml file to import. The user can cancel the import of the file and thereby create a new empty configuration for the viewed part.

Web service settings

Noah web service integration offers two ways of defining the web service’s communication settings, either by using of the Noah Business System Integration Tool or by editing the traditional config file shipped with the web service assembly of Noah (NoahWebIntegration.dll.config), which can be found in same directory as the other config files used by Noah.

If the communication is to be undertaken with the use of security certificates, then it recommended that the traditional config file is used. It is also strongly recommended that all editing of the config file id be done using the SvcConfigEditor.exe from Microsoft, it can be found in the windows SDK v6.0.

No matter, which configuration method is used, the following fields in the web server settings are mandatory:

BackEndWebServiceName, Name, NoahSiteIdentification and NoahWebServicePort.

If it is needed to run the webservice upon another IP address than the one, which is default for the PC server, then it is possible to specify this in the parameter NoahWebServiceId.

The communication protocol is made up of an endpoint definition, which contains one or more binding definitions.

If the communication protocol for the Noah web service endpoint binding is chosen to be either basicHttpBinding, basicHttpContextBinding, wsHttpBinding or wsHttpContextBinding, the web service settings configuration can be used for setting the communication parameters.

Note that the parameters: MaxBufferPoolSize, MaxBufferSize, MaxReceivedMessageSize, MaxStringContentLenght and MaxCharTableCount must be considered, since they control the max data size to import from and in to the backend system. The data size can vary depending on the number of actions included in the xml string. See picture below:

For a detailed description of all WCF communication parameters please consult: http://msdn.microsoft.com/en-us/library/ms731734.aspx or http://msdn.microsoft.com/en- us/library/ms733099.aspx or Windows Communication Foundation – Unleashed isbn-13 978-0- 672-32948-7.

When the Noah Web service is installed, the service endpoint bindings both for client and server is set to a basicHttpBinding. MaxBufferPoolSize, MaxBufferSize and MaxReceivedMessageSize to 65535 and MaxtableCharCount to 1000000.

  • No labels