Cyberlink Application Manager

[Kandy Swartzel]

SinceMicrosoft performed a Windows 10 upgrade to version 1803 remotely, as it it was repeatedly failing, I have lost all the HP pre-installed CyberLink software packages; Photo Director, Power Director, LabelPrint 2.5, Power2Go 10, WaveEditor2 and Power Media Player 14. In the process, of course, HP Recovery Manager also went!! Any help appreciated please. Thanks

What I don't know is if it is an update for which you need the software installed in order to update it, or a standalone update that installs an updated version of the HP recovery manager software without needing a previous version to update.

This package provides an update to the HP Recovery Manager application for supported desktop models that are running a supported operating system. HP Recovery Manager enables the reinstallation of original drivers and applications, and creates recovery media to restore the system to factory state. Recovery manager also allows you to recover your system directly from the recovery partition.

Hi there, mant thanks for your help. I found the C:\SWSetup folder that you refered to and attempted to run re-installations from there. Unsuccessful as kept getting the message "This software can only be installed on a Hewlett-Packard system", which mine is, but obviously not being seen as HP since the WIndows 10 upgrade. With your links I recovered Photo Director, Power Media Player 14 and Power2Go - albeit version 8, rather than 10. Power Director would just not install though - have seen othe posts describing same problem. The files download, but the installer just checks out without installing it. Also tried running from the download folder - but same. Many thanks for your help to date. Greg

CyberLink has an update for its long-available PhotoDirector image editor, which runs on Mac OS and Windows. This latest version is called PhotoDirector 13. New light effects and color adjustment features have been added. The company claims you can turn any photo into a "visual masterpiece with a comprehensive set of AI tools, including AI-powered Sky Replacement and Photo Animation effects."

CyberLink has been around for more than 20 years, with a variety of tools for image and video editing. They haven't made much of a mark in the pro and semi-pro venues, but I wanted to try the feature-rich software and see how it worked.

PhotoDirector 13 is offered as a subscription and as a one-time buy option. To install it, you first need the CyberLink application manager, then it will launch and install any software you are entitled to. I found the process overly cumbersome but no more so than what Adobe does with its Creative Cloud app that manages your Adobe purchases. Still, I'd be happy to enter a username and serial number and be done with it.

The app doesn't act like the other photo editors you may be used to, but it is well organized. As a useful feature, the software adds a guided mode that pretty much tells you what your options are and what to do next.

PhotoDirector 13 is what I would call "kitchen sink" software. It has more features than any photo editor I have ever seen, including popular options like bokeh and sky replacement, features first offered by Skylum in Luminar AI and now cropping up everywhere, including Adobe apps.

As a raw editor, PhotoDirector 13 has pretty much every slider a photographer would want, matching closely what Lightroom offers. I found I could get perfectly good images using this app. I also tried sky replacement on some landscape images, and I think PhotoDirector 13 is on par with what LuminarAI and Adobe provide, although, unlike LuminarAI, this app doesn't offer features like reflections in the water.

PhotoDirector 13 lets you flip the sky and further adjust image parameters. I liked its ability to separate a subject from the background. It's as well done as I've seen in other editors. And you can adjust the selection if it's not quite right.

I found the app stable and well behaved, although it re-renders quite a lot to keep all your versions. The positive is that PhotoDirector 13 has a non-destructive workflow. I tested the app on a pretty powerful iMac and found it to be pretty snappy overall.

I think the reason the app hasn't found wide acceptance is that it tries to do too much. It has all the pro features the majority of our readers want, but it also has a lot of eye candy features like animations and adding clip art to images. It reminds me of some of the mobile apps that let you add mustaches to portraits. Those things are going to appeal to a different crowd than our typical Fstoppers reader.

If I were advising CyberLink, I'd offer a pro version that includes its very capable raw editor and some of their excellent AI and portrait tools. The multiplicity of choices on the current app make for a very busy GUI, even with the guided feature. There's just a lot of stuff on screen. Also, because of all the features crammed in, it doesn't feel like an app aimed at pros, even though it has enough power and options to satisfy them.

This subscription also includes 50 GB of cloud storage and other amenities, like access to royalty-free use of Getty and Shutterstock libraries, plugins, and other image assets, which the company says are regularly updated.

If the http port of the JBoss server is changed then the port number in the attribute InvokerURLSuffix should also be modified in /server/default/deploy/http-invoker.sar/META-INF/jboss-service.xml file.

Applications Manager uses the Dynamic Monitoring Service (DMS) provided by Oracle Application Server to monitor the same. For this reason, the DMS Servlet has to be made accessible to the system where the Applications Manager is running.

To view metrics from a system other than the localhost you need to change the DMS configuration for the system that is running the Oracle Application Server that you want to monitor by modifying the file $ORACLE_HOME/Apache/Apache/conf/dms.conf on UNIX, or%ORACLE_HOME%\Apache\Apache\conf\dms.conf on Windows systems.

The following example shows a sample default configuration from dms.conf. This configuration limits AggreSpy to access metrics on the localhost (127.0.0.1). The port shown, 7200, may differ on your installation.

By changing the dms.conf configuration to specify the host that provides, or serves DMS metrics, you can allow users on systems other than the localhost to access the DMS metrics from the location :port/dms0/AggreSpy.

To monitor Tomcat 7.x and above, an application named Manager must be running in it for Applications Manager to monitor the Tomcat server. By default, this application will be running in the server. If you have customized the Manager application (Eg. \qamanager), then you can use the option "Tomcat Manager Application URI" in the client, for Applications Manager to monitor the Tomcat server.

However, remote access to Applications Manager is restricted, by default. To allow remote access, include the IP address of Applications Manager-installed host machine in context.xml file located under CATALINA_HOME/webapps/manager/META-INF/ directory (under 'allow =' ).

To monitor Tomcat 5.x and 6.x, an application named Manager must be running in it for Applications Manager to monitor the Tomcat server. By default, this application will be running in the server. If you have customized the Manager application (Eg. \qamanager), then you can use the option "Tomcat Manager Application URI" in the client, for Applications Manager to monitor the Tomcat server.

In the remote WebLogic server, navigate to /weblogic92/server/lib directory. From there, copy Weblogic.jar to \working\classes\weblogic\version9 directory in the machine where Applications Manager is running.

In the remote WebLogic server, navigate to /wlserver/server/lib directory. From there, copy Weblogic.jar, wlclient.jar, wljmsclient.jar, wlthint3client.jar to \working\classes\weblogic\version10 directory in the machine where Applications Manager is running.

In the remote WebLogic server, navigate to /wlserver/server/lib directory. From there, copy wlclient.jar and wljmxclient.jar to \working\classes\weblogic\version12 directory in the machine where Applications Manager is running.

The ports that need to be opened when the Weblogic Monitor is behind the firewall: Two-way communication between WebLogic listening port (default : 7001) and Applications Manager web server port (default : 9090).

You have to modify the Performance Monitor Interface (PMI) Specification Level from "None" to "Standard". Then deploy the perfServletApp.ear file, which uses the PMI infrastructure to retrieve the performance information from WebSphere Application Server, in the WebSphere. Restart WebSphere Application Server.

You have to modify the PMI Specification Level from "None"to "Standard" in all the WebSphere Servers in Network Deployment. Then deploy theperfServletApp.ear file, which uses the PMI infrastructure to retrieve the performance information from WebSphere Application Server, in any one of the WebSphere Servers in the Network Deployment. Restart WebSphere Application Server.

3. In Base mode, various WebSpheres will be listed down. Click on the WebSphere's name- > Under Additional Properties, click on End Points link -> click on SOAP connector address. You can get the SOAP port from there.

3. Various WebSpheres will be listed down. Click on the WebSphere's name- > Under Additional Properties, click on Web Container link -> click on HTTP Transports link. You can get the HTTP port from there.

To perform effective monitoring of DamengDB in Applications Manager, the monitor user must be granted the Data Viewer privilege. Refer here to know more about how to grant this privilege to the newly created user.

To monitor IBM Informix DB, make sure that the ifxjdbc.jar file is present in the location:\working\classes directory. The jar file can be copied from the IBM Informix installation location, \jdbc\lib\jar. Restart Applications Manager after copying the file.

3a8082e126