Liferay Connected Services Client

The Liferay Connected Services app connects your Liferay instance to Liferay Connected Services (LCS). LCS is an online service that offers fix pack management, server metrics, Liferay subscription management, and more. LCS provides single-click download and install of fix packs, even across a cluster. The server metrics service provides information on how your Liferay instance is running. This includes data on pages, portlets, memory usage, JVM performance, and more. Note that the fix pack and subscription management features require an active Liferay subscription.

In order to offer the best service possible, we store the following information about your servers on the LCS servers: patches installed on each server, portal.properties (except sensitive data), JVM metrics, portal and portlet metrics, cache and server metrics. Sensitive data is defined as any key-value pair containing usernames or passwords.

This app will appear in your Control Panel once installed.

Liferay Connected Services Client (any version) requires the installation of Liferay Portal 6.2 EE SP15+, and Liferay Connected Services Client 6.0.0 requires the installation of Liferay DXP 7.0 de-83+. In OpenShift and dockerized environments, the minimum Java requirement for LCS Client 5.0.0 or higher is JDK 1.8.0_191

Latest Changes
  • CLDSVCS-2465 As LCS Developer I need JSONErrorCode changed into RESTError
  • CLDSVCS-2471 Update lcs-api to ignore transportMetadata property
  • CLDSVCS-2477 As LCS Developer I need to export NoSQL service beans as OSGi components
  • CLDSVCS-2481 Unable to verify message from LCS when using IBM JDK
  • CLDSVCS-2482 On the first startup of LCS client, there is a JSON web service communication error in the logs
  • CLDSVCS-2483 Fix packs not available on fresh DXP bundle
  • CLDSVCS-2499 As LCS Developer I need new REST methods in LCS API
  • CLDSVCS-2519 As an LCS developer, I would like to define new constants for JVM, system and hardware settings
  • CLDSVCS-2537 As an LCS administrator, I would like to set email addresses for recipients of quarterly uptime reports
  • CLDSVCS-2585 As an LCS developer, I would like to fix backend module dependencies
  • CLDSVCS-2591 As LCS Developer I need LCS API module refers same petra json ws client module version as osb-lcs modules
  • CLDSVCS-2595 As a System Admin, I want to see better descriptions of registration exceptions
  • CLDSVCS-2609 DXP fix pack download may fail
  • CLDSVCS-2696 As an LCS Developer, I would like to lower more noisy LCS Client logs from debug to trace level
  • CLDSVCS-2718 As a System Admin, I want a descriptive error message in LCS Client log when LCS does not find a valid subs...
  • CLDSVCS-2740 As LCS Developer I need LCS API to support new fields in LCSClusterNode entity
  • CLDSVCS-2753 As LCS Developer I need LCS API to depend to petra ws client 2.0.0
  • CLDSVCS-2755 As LCS Developer I need LCS API to depend to petra ws client 3.0.0
  • CLDSVCS-2841 Server with Websphere 8.5.5.9 and DXP 7.0 is unable to register
  • CLDSVCS-2843 As LCS Developer I need LCS REST API extracted from LCS API
  • CLDSVCS-2885 As LCS Developer I need to remove code that refer to old enrollment process
  • CLDSVCS-2909 Integrate/Merge the new AnalyticsMessageEvent proposal
  • CLDSVCS-2939 Update AnalyicsEventsMessage format to new requirements
  • CLDSVCS-2947 Extract lcs-messaging to a lcs-messaging-api project
  • CLDSVCS-2980 AnalyicsEventsMessage add event timestamp
  • CLDSVCS-3047 As LCS Developer I need LCS Client is aware of CommandMessage attributes
  • CLDSVCS-3126 Messaging OSGi library fails to deserialize payload due to class loading issues
  • CLDSVCS-3177 Rename ScheduledTaskMessage to PortalModelMessage class
  • CLDSVCS-3298 As a LCS developer, I want to update DownloadPatchesCommandMessage
  • CLDSVCS-3331 Rename buildNumber to portalBuildNumber field in HandshakeMessage
  • CLDSVCS-3346 LCS Client deployed on AIX is unable to connect
  • CLDSVCS-3619 MessageBusMessage's put method should have Object type for value argument
  • CLDSVCS-3707 AS LCS Developer I need HandshakeMesage to support lcsClusterEntryTokenId attribute
  • CLDSVCS-3710 As LCS Developer I need LCS API to provide Subscription Service labels
  • CLDSVCS-3734 HanshakeResponseMessage needs way to send back new key
  • CLDSVCS-3770 As LCS Developer I need well designed Messages in lcs-messaging module
  • CLDSVCS-3781 Standardize naming pattern of patches with LRDCOM
  • CLDSVCS-3848 As a part of PM review, wordsmith LCS Client logs and assign appropriate severity levels
  • CLDSVCS-3953 LCS Client as OSGi module
  • CLDSVCS-3955 As DXP owner I need LCS Client dependencies applicable to all DXP portals
  • CLDSVCS-3956 LCS Client components should comunicate via event manager
  • CLDSVCS-3965 As LCS Developer I need LCS Client tests to pass to avoid CI complains
  • CLDSVCS-3966 As LCS Developer I need all LCS components are activated on portal sdeploy lifecycle event
  • CLDSVCS-3967 As portal instance administrator I need ability to override LCS Client settings i OSGi container via OS env...
  • CLDSVCS-3975 LCS Client has to set minimum allowed version of dependency
  • CLDSVCS-3976 LCS Client has to use build number provided by configuration
  • CLDSVCS-3978 Activate all Tasks as OSGI components
  • CLDSVCS-3980 As LCS User I need LCS Client has necessary petra and lcs-messaging dependencies
  • CLDSVCS-3982 LCS Client should implement OSGi message bus components to integrate with LicensManager legacy messages
  • CLDSVCS-3983 javax.management.AttributeNotFoundException: Cannot find attribute [currentThreadCount] on resource - affec...
  • CLDSVCS-3984 LCS Client Web module needs access to LCSConfiguration
  • CLDSVCS-3985 LCS Client does not deactivate properly if tomcat is shutdown
  • CLDSVCS-3986 LCS Client does not work properly in clustered environment
  • CLDSVCS-3987 LCSPortalClinet doesn't work properly after lcs-client-impl is restarted through gogo shell
  • CLDSVCS-3992 Version mismatch for com.fasterxml.jackson.databind in build.gradle
  • CLDSVCS-3993 LCS Portlet is unavailable on 7.2
  • CLDSVCS-3995 Remove unused(old) lcs-client related libraries
  • CLDSVCS-3997 Add language files for portlet title
  • CLDSVCS-4009 lcs.client.impl service parameter is null on "unsupported" app server startup
  • CLDSVCS-4017 Add default language files for LCS configuration pids
  • LPS-65012 Move all private packages inside an "internal" package
  • LPS-65446 Move lcs-portlet into "modules"
  • LPS-65810 As a developer, I would like to remove wildcards in Export-Package and explicitly declare the exported pack...
  • LPS-66547 HotDeployException error registering servlet context listeners for spi-provider-web
  • LPS-66853 SourceFormatter Improvements
  • LPS-67352 As a developer, I would like the source formatter to integrate checkstyle
  • LPS-69271 Adding @Override annotations not working properly for modules files when running ant format-javadoc
  • LPS-69453 As a developer, I would like an empty "deployDependencies" Gradle task to enable if required
  • LPS-73855 JavadocFormatter cannot handle java 8 notation or enum constants
  • LPS-74544 SourceFormatter improvements
  • LPS-75049 Drop support for "provided" configuration in gradle-plugins-defaults and move to "compileOnly"
  • LPS-77699 Update Translations
  • LPS-80064 Use GetterUtil.getX instead of the parseX method on primitive types when appropriate
  • LPS-84119 SourceFormatter improvements
  • LPS-91420 Integrate portal-tools-java-parser with SourcFormatter
  • LPS-94629 Expose JSONWebServiceClientFactory in petra-json-web-service-client to be able to direclty create new JSONW...
  • LPS-94968 LCS dependency error com.liferay.portal.kernel.theme
  • LPS-94973 LCS dependency error com.liferay.lcs.client.impl
  • LPS-94975 LCS throws errors about a missing connection token on startup
  • LPS-95024 lpkg tests failing at move-artifact lcs.security.jar
  • LPS-96210 LCS missing from product menu on 7.2
Show More

I clienti che hanno visto questo hanno inoltre acquistato