Management System

Most parameters are stored as keys in the section <appSettings>. They are briefly described below. You will find more information at the respective places in the Axinom Developer Guide.

Additionally you have to add the following section:

<location path="publish/preliminary">
   <system.web>
      <authorization>
          <allow users="*"/> 
      </authorization> 
   </system.web>
</location>

If you use Windows-Authentication, change IIS settings to allow everybody to access the folder publish/preliminary.

Configuring Web-Services

AxCMS.net consumes some Web-wervices.  All of them are to be configured the same way. Most of the services are hosted in the AxCMSPublishService-application. The others are MailService, SupportService and WssService. You can also access additional services from your Extras-application and reuse the same configuration pattern.

Here is a description of a service configuration, using WebQueryService as an example. Just replace the name and other information to configure other service.

First, add section-description under configSections: 

<section name="WebQueryService" type="Axinom.AECMS.Gateway.GatewayConfiguration, AxCMS.BL" />

The section itself looks like this:

<WebQueryService type="WebService">
<Url>http://localhost/AxCMSPublishService_Sample/WebQueryService.asmx</Url>
    <Timeout>30</Timeout>  
    <UseWSE>true</UseWSE>
    <Username>wseUsername</Username>
    <Password>wsePassword</Password>
    <Proxy>address_of_your_proxy</Proxy>
    <ProxyUsername>proxyUsername</ProxyUsername>
    <ProxyPassword>proxyPassword</ProxyPassword>
</WebQueryService>

Url - points to the asmx-file of the web-serivce
Timeout - web-service timeout in seconds
UseWSE - true/false - if WSE should be used to access the service. If set to true, Username and Password have to be specified as well - credentials for WSE. Web-service must also support WSE and WSE3 must be installed on both - client and server. Read more under Securing AxCMS.
Proxy - address of your web-proxy, if one is used. Optional. If the proxy requires username and password, they can be specified under ProxyUsername and ProxyPassword.

There are the following CMS clients in the MS application:

• WebQueryService (WebQueryService.asmx) allows to execute any queries on the live system from anywhere. You can use ExecuteDataTable and ExecuteNonQuery methods.
  The service of this proxy is hosted in the AxCMSPublishService application.
• PublishWebService (PublishWebService.asmx) is responsible for publishing of objects of all kinds.
  This client will be configured as part of a PublishAgent.
  The service of this proxy is hosted in the AxCMSPublishService application.
• ReIndexWebService (IndexWebService.asmx) is responsible for indexing on the LS.
  This client will be configured as part of a PublishAgent. The service of this proxy is hosted in the AxCMSPublishService application.
• IpRuleService (IpRuleWebService.asmx) is provided to be able to manage IP authentication data stored in the LS
  from the management system. It was developed before the generic WebQueryService and
  could be recycled if the management logic will be reimplemented using WebQueryService.
  The service of this proxy is hosted in the AxCMSPublishService application.
• UserService (UserWebService.asmx) is responsible for classification and right management of live users. The service of this proxy is hosted in the AxCMSPublishService application.
• MailService (MailCenterWebService.asmx) provides means to send and manage bulk emails using the AxCMS.net MailCenter application.
  The service of this proxy is NOT normally hosted in the AxCMSPublishService application,
  but somewhere else as a standalone web application.
• SupportService (http://support.axinom.de/WebSuiteService.asmx) is responsible for a context sensitive help of CMS user interface. You are not
  supposed to call this service from the customer specific code.
  The service of this proxy is hosted by the Axinom GmbH.
• WssService (http://wss.yoursharepoint.com/wss/_vti_bin/AxinomWSS.asmx) is used to integrate AxCMS.net with Microsoft Sharepoint.
  The IWssService interface is subject to changes in the future, don't use it unless you absolutely have to. The service if this proxy is hosted together with the sharepoint web application.

Support Service

The SupportService of Axinom delivers dynamic help for any CMS page and informs you about news in the AxCMS.net. To get this service working, your CMS application must have direct internet access. If this is not the case you can disable the service (see the key "SupportService" above). If the service is not available, the local help is displayed, which may no longer be complete and possibly also not up to date anymore.

IPRuleSerivce

AxCMS.net offers functionality for setting up IP-address based authentication to live system's users. One should configure IP-rules for that. GUI in MS communicates with the Live System through IpRuleWebService. More details under IP-address Based Live Authentication.

UserService

AxCMS.net users can manage live users (members). As user information is placed in the Live-System, communication has to be done via a web service.

Publishing

How the Management System publishes its content to the Live System is configured using PublishAgents.

It is possible to define multiple agents in the same time

and publish simultenously to multiple Live Systems. Publishing configuration looks like this:

<Publisher>
    <PublishAgent mode="off" type="InProcess" />
    <PublishAgent mode="on" type="WebService">
        <PublishWebService type="WebService">
            <Url>http://localhost/AxCMSPublishService_Sample/PublishWebService.asmx</Url>
        </PublishWebService>
        <ReIndexWebService type="WebService">
            <Url>http://localhost/AxCMSPublishService_Sample/IndexWebService.asmx</Url>
        </ReIndexWebService>
    </PublishAgent>
</Publisher>

Mode (on/off) lets temporary turn off one or many publish agents. Only the agents with mode=on are taken into account during publishing.

Type of a publish agent can be InProcess or WebService. InProcess is to be used, if the Live System runs on the same server like Management System.

WebService - if Live System is installed remotely and Web-Services are used to access it.

If you use InProcess-publish-agent, you don't need any additional configuration for the agent itself, but you have to define

PublishService-section in the same web.config, because the PublishService is hosted in this case in the ManagementSystem and not in the AxCMSPublishService-application.

See also Configuring Publish Service.

If you use WebService, you have to specify 2 standard Web-Service sections in your publish agent: for PublishWebService and ReIndexWebService.