A Citrix XenApp/XenDesktop service failed to connect to Citrix Configuration Logging Service

Health Check has detected that a XenApp/XenDesktop service failed to connect to Configuration Logging Service. As a result, communication between these services cannot occur. The services might not be listening or they might be corrupted.

ADIdentity Service

Analytics Service

AppLibrary Service

Broker Service

Configuration Service

Delegated Admin Service

Environment Test Service

Host Availability Service

Machine Creation Service

Monitor Service

StoreFront Service

Trust Service

Orchestration Service

For more information about these services, refer to CTX139415 – XenDesktop 7.x Services Overview


Citrix XenApp/XenDesktop Site is unreachable by a FMA Service

Health Check has detected that the XenApp/XenDesktop site is unreachable by one of the following services:

ADIdentity Service

Analytics Service

AppLibrary Service

Broker Service

Configuration Service

Delegated Admin Service

Environment Test Service

Host Availability Service

Machine Creation Service

Monitor Service

StoreFront Service

Trust Service

Orchestration Service

The database is compatible and the service group for the Controller Service is available for registration. The Controller Service can communicate with the database, but no endpoints are registered in the Central Configuration Service. This can occur when the Site setup or upgrade did not complete, resulting in a partially configured Site.

For more information about these services, refer to CTX139415 – XenDesktop 7.x Services Overview


Why Integration Matters for Creating Productivity Hubs with Exceptional Worker Experiences

EMC logo

The trends in productivity tools,
improved connectivity, changing work culture and worker expectations have led many organizations to rethink their technology investments. Most enterprises, even those in highly regulated industries (financial and life sciences sectors), have reduced their data center footprint. They’ve moved workloads to the cloud, virtualized desktops, adopted SaaS-based solutions, increased BYOD support and provided flexibility for their workforce to work from anywhere. So, what’s missing? A connected worker experience across enterprise applications – one that’s worker obsessed and totally focused on workforce productivity and sentiment.

Bring Enterprise Applications Together Into a Cohesive Worker Experience

Enterprise applications aren’t going away, they’re at the heart of the business and will remain so. That doesn’t mean they should operate in silos. Organizations have a variety of business applications and IT solutions that all too often fall short on worker experience.  Examples of these apps and solutions include:

Typical enterprise apps used by business workers:

  • Payroll apps such as ADP or Paychex
  • HR services powered by Workday, Kronos or Oracle ERP Cloud
  • CRM by Salesforce or Microsoft Dynamics
  • Travel & Expense via SAP Concur
  • ITSM is delivered through ServiceNow or BMC Remedy
  • Collaboration/productivity apps by Microsoft O365, Slack or Google G-Suite

Enterprise platforms used by IT departments:

  • Amazon Web Services or Microsoft Azure hosting servers and custom apps
  • VMware or Hyper-V for virtualization and cloud infrastructure
  • VMware AirWatch or Citrix XenMobile for device management and mobile apps
  • Pivotal Cloud Foundry, Docker, Kubernetes, and others for modernizing legacy apps using microservices architectures

Once enterprise workloads have been containerized, deployed in the cloud and workers are able to use any device and work from anywhere, is this the end game? Of course not, the journey never ends. Adopting purpose-built SaaS solutions have led to newer challenges around business process automation, workflow and integration. It’s resulted in multiple interfaces, security requirements and disconnected worker experiences.

Many corporate intranets and portals either provide a collection of links to other applications or embed content from external sources – neither of which provide an engaging worker experience. Why is that so? The problem is that links take the workers to other locations rather than allowing them to have a cohesive experience within a single portal. Given that content often lives in multiple repositories managed by different vendors, searching or even browsing seamlessly to access the right information is a challenge. It becomes a spaghetti space that is frustrating and time consuming for the workforce. The solution is a unified Digital Workplace that collates information from multiple enterprise applications and provides the ability to perform actions without having to switch context.  This is the difference between a productive, engaging experience and one that simply frustrates the workforce.

Adopting purpose-built SaaS solutions have resulted in multiple interfaces, security requirements and disconnected worker experiences.

iPaaS Becomes the Enabler for Delivering More Productive Worker Experiences

Traditional EAI platforms such as WebSphere, Tibco, BizTalk etc., focused on integration and process automation at the data level and the emphasis wasn’t on the worker experience. The emphasis was on batch processing, message queuing and transforming data between sending and receiving parties or systems. However, these integrations were often complex and expensive deployments requiring specialized skillsets and infrastructure. Depending on the systems, often additional adapters and/or scripting were required for full-scale integration.

The changing landscape of integration in the cloud-first world is no longer about batch processing, ETL jobs, EDI or XML formats. Modern enterprise systems support REST APIs and JSON for data interchange. Major vendors have realized the change – IBM Integration Bus, Microsoft Integration Services and Azure Logic Apps aim to address the integration needs in the cloud. However, the complexities of deployment and challenges around worker experience still exists.

While holistic transaction-focused middleware might still make sense for certain scenarios, the new breed of integration-platform-as-a-service (iPaaS) solutions offer lightweight, plug and play, low code/no code integration that is quick to deploy and easy to manage. Many provide graphical interfaces for orchestrating process automation that empowers knowledge workers with business acumen to create and manage workflows and automation. Dell Boomi has been the leader in the iPaaS space and other players such as Informatica, MuleSoft, SnapLogic etc., offer varying degrees of flexibility and niche feature sets. There’s a lot of consolidation happening in this area with major cloud solution providers such as Salesforce acquiring MuleSoft and Google taking over Apigee to bolster their iPaaS offering.

iPaaS solutions effectively tackle the cloud-to-cloud and on-premises integrations and enable drag-n-drop process automation. However, there is still a void in terms of a seamless, integrated worker experience. A combination of dashboard/portal framework, search engine and cloud-based collaboration tools – working in conjunction with an iPaaS solution forms the foundation to a comprehensive digital workplace and addresses the worker experience issue.

Digital Workplace Platforms Bring Together Enterprise Applications and Solutions for a Cohesive Personalized Experience

Platforms such as ServiceNow provide a flexible layout, navigation scheme, built-in search engine and widgets-based rendering of external content. SharePoint and Office 365 provide all the above stated capabilities, along with additional collaboration, document management, social features, AI/ML based suggestions and native integration with the Office Suite. These platforms, combined with personas and robust worker profiles as key enablers, can be leveraged to integrate with other enterprise systems either via point-to-point integration or through an iPaaS platform to deliver an integrated digital workplace solution.

Productivity Hubs in the Real-world

Slack is another notable example that has combined the collaboration and communication needs into a single chat-based interface. Slack has pioneered the use of bot frameworks to enable integration and submitting actions to other applications without having to leave the Slack channels. For example, it allows workers to schedule a WebEx meeting, book flights or submit expenses in Concur, track projects issues in Jira etc., all within the Slack interface. There’s a bot for everything and the catalog keeps growing.

For organizations already invested in Microsoft technologies, Microsoft Teams offer similar advantages as Slack by providing a consistent worker experience by natively integrating with Exchange, SharePoint Online, OneDrive, Yammer, Office etc. Workers can leverage persistent chat to connect with colleagues, schedule meetings, share screens and collaborate on documents – all within a modern interface. With PowerApps and Flow integration and new features such as support for application pages, rendering SharePoint web parts etc., Teams is truly becoming the productivity hub of choice. Bots and apps frameworks also enable integration with virtual assistants such as Alexa or Cortana for voice-based command execution and will likely support IoT integrations soon.

While bots are great for point-to-point integrations and for performing micro actions within Slack or Teams, advanced workflow automation involving transactions on multiple enterprise applications and decision tree algorithms, can be implemented by leveraging an iPaaS solution such as Dell Boomi. To the right is a conceptual architecture for a digital workplace implementation leveraging industry leading enterprise solutions.

Help the Workforce Realize Their Full Potential

Dell EMC Consulting is a thought leader in Digital Workplace.  We’ve helped organizations transform their worker experiences with modern intranets and collaboration tools by integrating with enterprise applications to deliver consumer grade, personalized hubs and experiences.

We start by engaging with workers and IT stakeholders to:

  • Understand needs and current pain points
  • Identify key personas, journeys and required capabilities
  • Assess the current IT landscape and existing investments
  • Conduct workshops with sponsors and stakeholders to establish a vision
  • Present the technical approach and roadmap to realize the vision
  • Prioritize use cases and formalize program workstreams
  • Design and implement projects to modernize applications and integrate enterprise systems
  • Collaborate with corporate communications on adoption and change management for driving adoption of modern digital workplaces

Looking to modernize your workers’ experiences? Comment below to start the conversation, or contact Dell EMC Sales to learn how our Consulting Services can help.

The post Why Integration Matters for Creating Productivity Hubs with Exceptional Worker Experiences appeared first on InFocus Blog | Dell EMC Services.

Update your feed preferences





submit to reddit


Help Mid Market Customers Drive the Technology Changes Needed to be Successful

Dell EMC is your strategic technology partner that Mid Market customers can depend on for efficient solutions to meet their business goals.

Who are Mid Market Customers?

IT is small – often small department and their level of experience varies widely. IT or Business decision makers are typically in hybrid roles, wearing multiple hats and stretched thin.

Technology is critical to their businessesMid Market customers need ‘commercial’ systems and some level of infrastructure. They are dealing with complex IT needs (mobility; cloud; security; operations), looking to keep up with and take advantage of change with solutions that scale to their needs.

Need assurance and support – because of their size, each IT decision is a big one and can have a significant impact on their business. With limited budgets and resources, they need confidence and trust in their vendor and solutions.

Efficiency is the end goal for ITMid Market customers may have different goals; grow big, increase their margin, compete, however they are all looking to technology to provide efficiency toward that goal—automate, speed-up and make things easy to accomplish.

What do Mid Market customers need?

Easy to install and maintain – Mid Market customers don’t need a lot of layers, complexity or staff. They would rather invest in future-oriented solutions that allow them to take on more, while staying lean.

Flexible + scalable – Mid Market customers prefer solutions that are flexible and scalable, should things change and they can adjust as needed. Technology is a big investment for them—they don’t want to over or under buy.

Comprehensive – Comprehensive products and comprehensive support. Mid Market customers prefer vendors who can offer a range of solutions across IT, not just one-offs. Vendors who can help upfront with expertise and throughout the process with deployment, support and lifecycle services.

Dell EMC has the latest innovative solutions from end users to infrastructure, plus the strategic guidance and expert execution, that make it easy for mid-size organizations to adopt transformative technologies to grow, compete or perform their best.

Product Portfolio –the broadest range with the latest solutions from end users to infrastructure, to help adopt transformative technology that Mid Market customers need to improve speed and agility.

Security Portfolio a full range of innovative data security and data protection solutions that scale to the needs of any business, working together to protect data, prevent threats and assure business continuity.

Services Portfolio best-in-class services to extend their IT teams. Get systems up and running faster and resolve issues more quickly, whether refreshing PCs or modernizing infrastructure.

What’s the benefit to your business?

Mid Market customers have limited bandwidth to manage multiple vendors and solutions. Partnering with Dell EMC enables you to:

  • Offer businesses the solutions they need to achieve their goals and build long-term loyal relationships
  • Achieve higher sales and margins by selling a broad range of products and solutions
  • Boost profitability by offering a wide range of services

Find campaign assets to support you in planning and creating your own marketing activity, targeting these growing businesses on theDigital Marketing Platform.


The benefits of agile integration, Part 1: The fate of the ESB

While many large enterprises successfully use the enterprise service bus
(ESB) pattern, the term is often disparaged in the cloud-native space, and
especially in relation to microservices architecture. It is seen as
heavyweight and lacking in agility. What has happened to make the ESB pattern
appear so outdated, and what should we use in its place? What would
lightweight integration look like?


The benefits of agile integration, Part 2: Moving to a lightweight, agile integration architecture

Microservices principles are revolutionizing the way applications are
built by enabling a more decoupled and decentralized approach to
implementation, which leads to greater agility, scalability, and resilience.
These applications still need to be connected to one another and to existing
systems of record. It clearly makes sense to use microservice techniques in
the integration space, too. Lightweight integration provides the benefits of
cloud-ready containerization to integration architecture, and provides the
opportunity to escape from the heavily centralized ESB pattern to more
empowered and autonomous application teams.


Multi-Cloud: What’s Your ROI?

EMC logo

Organizations are looking to move to a multi-cloud environment to realize the benefits of self service, scalability, accountability, standardization and automation. However, many are finding it difficult to get started. They are struggling with how to get corporate commitment, how to justify funding for the transformation, and where to start.

Projecting the ROI of the transformation gives you the information you need to build the business case to justify the transformation, and to help secure stakeholder and corporate buy-in.

How to determine multi-cloud ROI

Key to determining the ROI is understanding and comparing the total cost of ownership (TCO) of the current environment, the projected TCO of the target state, as well as what the transitions costs will be.

Establish Current and Target State Costs

Measure your current state TCO, and project your target state TCO. Both current and target state costs of all of the in-scope:

  • Hardware and software that is used to provision the applications.
  • The embedded network that the services use. Almost everything today has a network component such as in the fabric that connects us to storage, the LAN components in every server, the connections to the WAN and Internet that connects the services to users and other related systems.
  • The current costs of maintain the applications in the current and projected environments. You will find this varies due to the level of automation and application modernization.
  • The FTEs needed to support the infrastructure will also vary due to automation and modernization.
  • Facilities costs which include the more variable power and cooling as opposed to the fixed, less variable real estate costs. Power and cooling will decrease especially when migrating to converged more efficient, right sized environments.
  • External, outsourced workloads are the services we might employ for operations, service management, help desk, remote hands, etc. These will be impacted also by automation and modernization.  However, they might increase if the strategy is to reduce less reliance on internal resources.
  • Overhead includes whatever management, corporate and executive costs are attributed to the in-scope P&L.

Project Transition Costs

The transition costs pretty much parallel the same TCO of the current and future states.

They include:

  • Swing hardware refers to the additional or overlapping hardware that will be needed during the transformation / migration.
  • Additional Software, as with the H/W, identifies the costs associated with running parallel licenses.
  • There may be additional network connections needed that will need to be accounted for in determining transition costs.
  • Staff time refers to the internal or external costs for executing the transition. This is an interesting factor in terms of the time impact for executing the transition.  We have found that relying totally on internal resources, who also have their “Day Job”, will result in longer transition deliveries.  Often, employing outside resources will result in faster execution and at less cost.
  • As with many transformations, additional education and training is needed. This comes at a cost both in terms of costs and staff time.
  • There may be additional support needed in the form of transition services which will facilitate and guarantee success.

Run the Numbers

Input the current state, target state and transition costs into a cost-benefit analysis. Calculate current and target state IT run rates, and develop an investment profile based on the transformation roadmap. From this, the net IT costs, net savings, and ROI can be calculated.

The analysis should also take into account the time value of money by calculating the net present value (NPV) of the investments and savings. This will show the potential investment returns in current dollars. All of the analysis should be multi-year, typically covering a five year investment period.

By doing a payback or breakeven analysis you can determine how much time, usually expressed in years, it will take to recover the total cost of the investment (including both capital and services costs) and therefore, when the real savings from the transformation takes effect.

Want to learn more?

Join us at at Dell Technologies World on Wednesday May 2nd at 1:30pm in the session “Multi-Cloud: What’s Your ROI?” where we will walk through the detailed ROI analyses of two organizations with varying transformation scope and objectives, as well as an example transformation roadmap that shows key activities that impact ROI.

The post Multi-Cloud: What’s Your ROI? appeared first on InFocus Blog | Dell EMC Services.

Update your feed preferences





submit to reddit


7021552: Upgrading Host Integrator from 6.x to 7.x on Windows

64-Bit vs. 32-Bit

Beginning with version 7.5, your Windows system must be 64-bit. If you still need support for 32-bit Windows, please install version 7.1 SP2 (7.1.2026) in your environment. For more information about supported platforms, see also Technical Note 10030.

Upgrading Your Server(s)

When upgrading from a prior version (6.0, 6.5, or 6.6) on Windows, you can migrate the existing configuration to the new installation. The process is as follows:

  1. Prior to upgrading, note whether you have security enabled for Servers or Domains in your existing installation. (Because these settings are not automatically migrated, you will manually restore any non-default settings in step 14.c.)
    1. Open the Administrative WebStation interface: Click Start > Programs > Attachmate Verastream > Host Integrator > Administrative WebStation.
    2. If security is enabled, log in as a user in the Administrator profile; otherwise use blank credentials.
    3. Make a note of any non-default configuration for the following items.
      Location in Left Navigation Tree
      Default Value
      Security > Domains
      Security is unchecked
      Security > Servers
      Security is unchecked

If you have trouble accessing Administrative WebStation, you can instead check whether your existing clients specify a user name and password in the connect method calls. If connections are successfully established without credentials, Server or Domain security is not enabled.

  1. If you are using SSL encryption for host connections and the host requires a client certificate, make a copy of your C:Program FilesVHIsecurehostcertificate.pem file. You will manually restore it in step 13 below.
  2. After downloading the version 7.x product from http://download.attachmate.com/upgrades, run the downloaded .exe file as an administrative user. You may be presented with a Security Warning dialog confirming the file is published by Attachmate.
  3. Select a folder to unpack installation files. Click the ellipsis button (“…”) to browse to a different folder location. If you unpack to the Desktop, a subfolder is recommended.
  4. After the unzip process is complete, setup.exe automatically starts. Accept the license agreement to proceed.
  5. When the existing installation is detected, you are prompted with the following dialog message:
Setup has detected an existing Verastream Host Integrator installation. You can migrate settings files to your new installation. Do you wish to migrate the settings?

Click Yes. Files are copied to a separate temporary folder (%TMP%vhi6xbackup), and this folder location is temporarily stored in the system registry (HKEY_LOCAL_MACHINESoftwareVHILegacyBackupVHI6xInstallDir).

  1. After data has been successfully backed up, the following dialog message displays:
To complete the migration, please uninstall the existing copy of Verastream Host Integrator. When you have uninstalled, you may run this setup again, at which time you will be allowed to restore your saved settings. Setup will now exit.

Click OK to proceed.

  1. If you have been running a .NET web application or web service that uses the VHI connector, the appconncom.dll and xerces-c_1_4.dll files may remain loaded and locked by IIS. To unlock these files, terminate the aspnet_web process in Windows Task Manager, stop the IIS service, or restart the system.
  2. Uninstall the existing version: In Control Panel, click “Programs and Features,” “Uninstall a program,” or “Add or Remove Programs” (depending on your Windows version and view).

The uninstall process removes the old program files, but retains many data files for migration (such as deployed models and Web Builder projects).

Note: If you are upgrading multiple systems in your installation environment, it is strongly recommended that you repeat the above steps 1 through 9 on all systems before proceeding. For more information on setting up a version 7.x multi-server installation for load distribution and failover, see also Technical Notes 10108 and 10103.

  1. Run setup.exe again (in the folder location from step 4 above).

Important: Make a note of the administrative password you set during the installation process. Blank administrative credentials are no longer supported. (You will need to enter the administrative credentials later when running Administrative Console in step 14.b., or when installing an additional server for load distribution and failover.)

For additional information on installing Host Integrator, see the Installation Guide for your product version, available from http://support.attachmate.com/manuals/vhi.html.

  1. After Setup installs the new files and performs configuration, you are prompted whether to restore settings.
Setup has detected stored settings that were saved from a previous installation. Would you like to restore these settings?

Click Yes.

  1. Setup temporarily stops the session server service to restore its configuration. The following data is migrated:
    • Session server configuration (session pools, model variable lists, etc.)
    • Deployed models
    • Session server log data
    • Authentication and authorization configuration (profile OS groups and LDAP settings)
    • Load balancing domains
    • Web Builder projects

If migration and conversion is successful, the following message displays:

The migration of the stored settings was completed successfully.

Also, the VHI6xInstallDir value (from step 6) is removed from the registry, so future upgrades will migrate 7.x data (not re-migrate 6.x data).

If any steps of the migration process fail, see the migrateto7.log file in the folder specified by the value of your TMP environment variable.

  1. If you backed up a certificate.pem file in step 2, copy your certificate.pem file into the securehost subdirectory.

Note: Beginning in version 7.1, the securehost subfolder is automatically created by the installer. However, in version 7.0, you must manually create a subfolder named securehost within the folder specified by the VHI_ROOT system environment variable (typically C:Program FilesAttachmateVerastreamHostIntegrator).

  1. Verify successful migration and restore previous settings.
    1. Run Administrative Console from the installed shortcut (Attachmate Verastream > Host Integrator > Administrative Console).
    2. Connect to the management server and log in with user name “admin” and the administrative password set during installation (step 10 above).
    3. If Session Server Explorer is not currently displayed, click Perspective > Host Integrator > Session Servers.
    4. Restore any custom security settings that were noted in step 1 above: Under Servers, right click your server name and click Properties > General > Security.

Beginning in version 7.0, security is configured on a per-server basis only and also applies to connections using a load distribution domain.

Host Application Models

This section addresses the use of existing models that were created in previous versions (5.5 through 6.6).

Keep Unchanged vs. Convert

You can choose from two upgrade approaches for your models:

  • You can leave the existing model(s) unchanged. Compatibility settings are automatically enabled (where applicable) to maintain the same behavior as in earlier versions.

In the server upgrade process, models deployed to the session server are automatically moved from the previous installation location (typically C:Program FilesVHIdeploy) to C:Program FilesAttachmateVerastreamHostIntegratordeploy. Also, the source models created with Design Tool are moved from the previous installation location (typically C:Program FilesVHImodels) to <Documents>AttachmateVerastreamHostIntegratormodels for version 7.1.x (or C:Program FilesAttachmateVerastreamHostIntegratormodels for version 7.0).


  • You can manually convert models to the new version and re-deploy. Use this approach if you need to make changes to a model, or you want to take advantage of the latest product functionality (such as performance improvements).
    1. Open the model in Design Tool. You may see the following dialog:
Figure 1. Prior Version Model: 'This model was created with a prior version of Verastream Host Integrator....'Figure 1. Prior Version Model: ‘This model was created with a prior version of Verastream Host Integrator….’
    1. Verify the model continues to behave as you expect. For example, in certain cases it may be necessary to delete a pattern and re-add it. You should also verify that other aspects of the model, such as operations, recordsets, and procedures, behave correctly.
    2. Save the model. Note: Once you convert a model file to a newer version, it can no longer be loaded by an earlier version of Session Server or Design Tool.
    3. To take full advantage of the latest product functionality, disable compatibility settings in the model and re-test as appropriate. For more information on compatibility settings, see the “Compatibility Settings for Host Integrator Upgrades” topic in the VHI User Guide. For example, in VHI 7.6, see http://docs2.attachmate.com/verastream/vhi/7.6/en/topic/com.attachmate.vhi.help/html/reference/compatibility_switches.xhtml.

Java Event Handlers

If your pre-7.0 model uses Java event handler scripting code to customize session server behavior, you may need to make changes as follows:

Web Builder Projects

Generally, projects created in earlier versions can be deployed, undeployed, and deleted in version 7.x, but you may not be able to modify them. You should be aware of the following issues.

VHI Web Server Changed

After upgrading to version 7.5, any existing pre-7.5 Java projects must be re-built and re-deployed. See also Technical Note 10138.

Project Type Changes

Some project types that were in previous versions of Web Builder are no longer available for creating new projects:

Web Builder continues to provide support for generating Java and .NET web applications, Java Beans, and .NET Class Libraries.

Project Files Moved

In the installer upgrade process, Web Builder projects are moved from the previous installation location (typically C:Program FilesVHIprojects) to C:Program FilesAttachmateVerastreamHostIntegratorprojects. Beginning in version 7.1, when you first run Web Builder, projects are migrated to <Documents>AttachmateVerastreamHostIntegratorprojects.

Client Applications

It is recommended that you install the new connector API files on systems running client applications. While you may be able to continue using the old connector, an “Undefined error message” indicates that a connector upgrade is required. The error message may also include an error number that can provide further information. See the list of error numbers at http://docs2.attachmate.com/verastream/vhi/7.1sp2/en/topic/com.attachmate.vhi.help/html/reference/h_rte.html.

Note: If you have statically linked to any of the connector files in your applications, you must re-link to the connector files after upgrading in order to take advantage of new methods and features.

Beginning in version 6.5, the COM connector file name has changed from appconn.dll to appconncom.dll.

Beginning in version 6.6, the .NET Connector no longer supports .NET 1.1 client applications.

BizTalk and J2EE Changes

If you are currently using these technologies, you will need to make changes in conjunction with your Host Integrator 7.x upgrade:

  • BizTalk: The Verastream Interface for Microsoft BizTalk Server is no longer supported or included with Verastream Host Integrator. To integrate host data into a BizTalk orchestration project, web services are the recommended approach.
  • J2EE: Java EE Connector Architecture (JCA) Resource Adapter (RA), also known as the J2EE Connector, is no longer supported. To integrate host data into your application server (such as BEA/Oracle WebLogic, IBM WebSphere, or Sun GlassFish Enterprise Server), web services are the recommended standard. Also, the Java connector and JDBC are still supported.

For more information about using Host Integrator web services, see Technical Note 10092.

SNMP Changes

This section applies if you are using an SNMP network management station to monitor Verastream Host Integrator Session Server.

After upgrading to version 7.x, update your management station with the new Management Information Base (MIB) file installed at hostintegrator/lib/java/vhi.mib. The MIB uses the Attachmate organization ID (1371) instead of WRQ (820).