Guru Of Geeks

Technote (troubleshooting) Problem(Abstract) When you use a valid Mozilla Firefox version 10 or later browser, the launchpad.sh script does not launch the Firefox window that displays the main screen for the product installation process. Symptom When you run the ./launchpad.sh script from the root directory of the installation media, the following error messages are returned: cp: cannot stat `/media/186826C8347EAE50/IBM/pkg/WPS70/inst/Linux64/launchpad/lib': No such file or directory cp: cannot stat `/media/186826C8347EAE50/IBM/pkg/WPS70/inst/Linux64/launchpad/../jre': No such file or directory /usr/bin/less Cause The Firefox version validation script launchpad/browser.sh script verified that the Firefox base version is between 1 and 9: supportedFirefoxVersion() { case "$*" in  *Firefox\ [1-9].*) return 0;;  *Firefox/[1-9].*) return 0;;  *Firefox*) return 1;;  *rv:1.[7-9]*) return 0;;  *rv:[2-9].*) return 0;;  *rv:*) return 1;;  Mozilla*\ 1.[7-9]*) return 0;;  Mozilla...

Technote (troubleshooting) Problem(Abstract) The BPM launchpad does not start in a Linux or UNIX environment when using Firefox 45/Firefox 45 ESR (Extended Service Release) or above in IBM Business Process Manager. Symptom The start screen of the BPM launchpad does not open, and you may receive error messages similar to the following when you run the Launchpad.sh command: GLib-GObject -WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised GLib-GObject -WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised GLib-GObject -WARNING **: Attempt to add property GnomeProgram::display after class was initialised GLib-GObject -WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised GnomeUI -WARNING **: While connecting to session manager: None of the authentication protocols specified are supported. Or addons.xpi WARN Add-on   commonlaunchpad@ibm.com   is not correctly signed. Cause Th...

Technote (troubleshooting) Problem(Abstract) The IBM Business Process Manager product launchpad does not start. An unsupported browser error message is shown if the default browser is Mozilla Firefox Version 15 and Version 17. Symptom When you start the product launchpad, a browser window opens with the following message: "The launchpad cannot start. This error typically occurs when a supported browser cannot be found." The following screen capture shows the message: Cause Mozilla Firefox Version 15 and Version 17, by default, do not enable some of the privileges to test the browser function. This situation causes the Launchpad to fail during the browser identification process. Diagnosing the problem Use the   firefox -version   command to determine the exact version of Firefox that is installed. Resolving the problem Note : IBM Business Process Manager V8.5.5 products use an updated version of the Launchpad and do not have this issue on Mozilla Firefox V18 and later. Work ar...

Download and install below version of firefox and try the launchpad once again. https://ftp.mozilla.org/pub/ firefox/releases/17.0esr/ linux-x86_64/en-US/

Configuring Postfix as a Gmail Relay on CentOS This tutorial should work on any distro based on RedHat, but I have only tested it on CentOS 6.4. You will need to run the commands as root. I found a ton of how-tos and tutorials on how to set up Postfix as a Gmail relay, but most of them required making a client certificate or were incomplete. After fighting with getting Postfix set up on CentOS 6.1, and browsing the internet for many, many days, I finally got it working. Part of the configuration is based on the pages found here and here . Installing Postfix Installing Postfix is easy, just run this command as root: yum install postfix mailx cyrus-sasl-plain Thanks to Jonathan for pointing that out. Configuring Basically, you need to create a password file so that Postfix can authenticate to Gmail's servers. You do this by creating a file named sasl_passwd in /etc/postfix. Replace smtp_user and smtp_passwd with ...

I have written an article on how to unlock a user account when it expires: ORA-28002: the password will expire within 1 days But, every 180 days, you need to repeat the same action.  If you are NOT concerned with strict security rules for your database, you can take the following approach to set user accounts to never expire. What Profile Used by a User Account? A profile [3]  is a database object – a named set of resource limits. Using profile, you can enforce a limit on resource utilization using resource limit parameters Also you can maintain database security by using password management feature.  Here is the SQL command you can use to query which profile is used by each user account: SQL>  SELECT USERNAME, PROFILE FROM DBA_USERS; USERNAME                       PROFILE —————————— —————————— OAM_OAM                        DEFAULT OAM_IAU_APPEND                 DEFAULT OAM_IAU_VIEWER                 DEFAULT OAM_IAU                        DEFAULT ...

In simple terms, with lambda you can ignore where your code is running. You deploy a package that AWS lambda will execute somewhere for you. You pay by execution time (you won't pay if you are not running any code for idle servers). There are some restrictions in terms of languages you can use and their environments, and deployments are a bit unorthodox. There are several projects trying to use lambda as the backend for a full web applications (in conjunction with API Gateway). Elastic Beanstalk provides a more typical execution environment: you code you app as you'd usually do and AWS takes care of provisioning your web servers, app deployments, configuration management, logging and scaling among others. Basically you defer lots of ops work to them, but in the end you end up with a similar environment to the one you could do by hand with EC2, ASGs, ELBs, etc. Here as well you have some predefined environments you can use, much more varied than the o...

The application experienced an internal error loading the SSL libraries Document ID:   TEC1504286 Last Modified Date:   09/29/2016   Show Technical Document Details Problem:  When downloading a Microsoft document attachment on ServiceDesk SSL system, the following error pops up: "The application experienced an internal error loading the SSL libraries" Environment:    ServiceDesk 12.x-14.x Microsoft Windows 7 - 8 Microsoft Internet Explorer Cause:   The error is Microsoft generated Error caused by Microsoft Windows update. Resolution/Workaround: Microsoft have addressed these error. Please review one of the following documents: 1.  https://social.technet.microsoft.com/Forums/Sharepoint/en-US/78f64ac7-e68c-4171-b940-98f68e27279c/the-application-experienced-an-internal-error-loading-the-ssl-libraries-word-2013?forum=officeitpro 2.  https://blogs.technet.microsoft.com/office_integration__sharepoint/2015/04/20/office-2013-error-certificate-error-the-application-experienced-an-inte...