Skip to main content
Version: 4.2.5

Managing iCore Invoke

To manage iCore Invoke web service hosted in IIS, you need to be logged in with an account with administrative rights. Also, PowerShell 3.0 (or later) must be enabled in the OS settings.

For general considerations regarding hosting of iCore web applications in IIS, see iCore web applications hosted in IIS.

note

For each iCore Invoke operation, a new log file is created under %PROGRAMDATA%\iCore Solutions\iCPS

caution

If you are running Windows 2008 R2 SP1, you must start the scripts from a PowerShell console or PowerShell ISE. A bug in Microsoft PowerShell installation prevents users from starting a PowerShell script using File Explorer if the scripts has arguments.

To run a script from within the PowerShell console, type: & "<path to .ps1-script>".

If you are running iCore on a x64 OS, you must start the x64 PowerShell console.

Installing iCore Invoke web service IIS hosting​

Before you install a new instance of iCore Invoke web service, you need the following:

  • The name of the site where the web service is to be installed.
  • The name of the IIS application pool where the web service is to be executed.
  • A suitable name for the new web service instance.
note

It is possible to install multiple instances of an iCore Invoke web service hosted in IIS and it is possible to share application pools between web service instances.

To install a new instance of iCore Invoke web service​

  1. Open the file explorer and go to directory “[iCore root]\bin\Web service templates”.
  2. Locate the file “CreateiCoreInvokeApplication.ps1”, open the file context menu and select Run with PowerShell. The PowerShell console is started.
    note

    Make sure to use the Windows Powershell console and not another host (for example PowerShell ISE) as it may not support all functionality.

  3. Supply the requested information:
    • Site name
    • Web service name
    • IIS application pool name
      • If the application pool should be created for you, values are:
        Y or Yes ; create application pool if it does not exist.
        N or No ; application pool is expected to already exist, if not the installation will fail.
  4. Confirm creation of web service.
  5. When complete, press <ENTER> to close PowerShell host.

Removing iCore Invoke web service​

Before you can remove an instance of iCore Invoke web service, you need the following:

  • The name of the site where the web service is hosted.
  • The name of the web service instance to remove.
  • The name of the IIS application pool where the web service is executed.
    • Decide if the application pool used by web service instance should be removed or not (if application pool used by another application it is not removed)
caution

Removing a web service instance will also remove the web.config file. If information in this file needs to be saved, make sure you have made a backup copy of the file in another location.

To remove an instance of iCore Invoke​

  1. Open the file explorer and go to directory “[iCore root]\bin\Web service templates”.
  2. Locate the file “RemoveiCoreInvokeApplication.ps1”, open the file context menu and select Run with PowerShell. The PowerShell console is started.
  3. Supply the requested information:
    • Site name
    • Web service name
    • Remove or keep IIS application pool
      Y or Yes ; remove application pool, if application pool is used by another application it will not be removed
      N or No ; keep application pool
  4. Confirm removal of web service.
  5. When complete, press <ENTER> to close PowerShell host.

Updating all instances of iCore Invoke (on all sites)​

When installing a new version of iCPS, the iCore Invoke web service needs to be updated. The update procedure takes care of all instances of iCore Invoke on all sites, so the update only needs to be done once on each host machine.

note

When updating from versions earlier than iCIS v4.1, the SystemContextEndpointBehavior section of the web.config file must be updated. For more information, see Configuration.

note

 In future releases of iCPS, the iCPS installer will handle update of iCore Invoke web services.

To update all instances on a machine hosting iCore Invoke web service​

  1. Open the file explorer and go to directory “[iCore root]\bin\Web service templates”.
  2. Locate the file “UpdateAlliCoreInvokeApplications.ps1”, open the file context menu and select Run with PowerShell. The PowerShell console is started.
  3. All found instances of iCoreInvoke web services are listed.
  4. Verify that no instances are missing. Also make sure that the list does not include any "non-iCore Invoke" web applications.
  5. Confirm to update the listed web services.
  6. When complete, press <ENTER> to close PowerShell host.

Accessing the iCore Invoke web service description​

The WSDL of iCore Invoke is accessible at the following address:

http://<host address>/<Virtual directory>/iCoreInvokeServiceImpl.svc?wsdl
Last updated on