Mobile First 7.1 Application center install error - ibm-mobilefirst

I am trying to install Mobile First 7.1 platform and the application server is websphere liberty 8.5.5.9. during install it throws below error in failed-install.log. (Database is DB2)
F:\Program Files\IBM\MobileFirst_Platform_Server\WorklightServer\post-install.xml:332: The following error occurred while executing this line:
F:\Program Files\IBM\MobileFirst_Platform_Server\WorklightServer\post-install.xml:2172: An error occured while reading file F:\Program Files\ibm\WebSphere\Liberty\usr\servers\server1\server.xml. Error: null.
the line numbers shows error for Application center installation..
what could be the issue?

i installed the application center manually now as mentioned in the IBM articles and that works.

Related

No supported platforms were detected to migrate issue with mfpmigrate from mobilefirst 6.3 to 8.0

I tried the migration process of mobilefirst from v6.3 to v8.0. I installed the migration tool. I tried to migrate a sample program in IBM mobilefirst v6.3 to v8.0 using the command mfpmigrate as shown below. Although the input to the command is a v6.3 program, it says that No supported platforms detected.
D:\MobileFirst>mfpmigrate client --in AdapterBasedAuth\apps\DoubleStepAuth --out
MigrationDemo
Error: An error occured during execution of command.
Error: No supported platforms were detected to migrate
Could you please help me resolve the above mentioned problems.
Thanks a lot in advance!
This is expected, as the sample application AdapterBasedAuthenticationHybridProject is not coming with any platforms. You need to first add a supported platform using MobileFirst Studio - iOS, Android etc...

IBM MobileFirst 8.0 Console - com.google.gson.stream.MalformedJsonException

In IBM MobileFirst 8.0 Console, when selecting Application push tab.
Following error is occurred sometimes and that particular tab is getting stuck though it is configured and working fine.
Error is:
com.google.gson.stream.MalformedJsonException: Use JsonReader.setLenient(true) to accept malformed JSON at line 1 column 8 path $
Please check the attached image for Error:
Error Screenshot
Now Am solving this issue by stopping mfpserver and restarting, so it is working fine as it is not stuck and error is solved.
Please check the attached image for solved console push tab stuck error:
Solved issue screenshot
How can i solve this issue without restarting mfpserver?
Not a question for Stack Overflow.
Please open a PMR (support ticket) for IBM and provide to the support team the server logs for the time when this error happens.
You can find the server log file at: [devkit installation directory]/mfp-server/usr/servers/mfp/logs -> messages.log.

Preview not working on MobileFirst Platform Foundation Server 7.0

On the MobileFirst Server Platform Foundation 7.0, the Preview is not working in the console. On the Eclipse development side, all is working well.
The error message is the following:
Here is the error in the log:
[4/10/15 12:12:55:267 CEST] 00000027 org.apache.wink.server.internal.RequestProcessor I The following error occurred during the invocation of the handlers chain: WebApplicationException (404 - Not Found) with message 'null' while processing GET request sent to http://10.3.20.64:9080/catalogmanagerfull/authorization/v1/clients/preview
The application can use the server without any issue. It's really only the Preview in the console that is not working. The Application Server is a WAS Liberty profile running on Linux.
In a MobileFirst Server V6.3, the same project has no issue.
Preview is not meant to work in a production environment, however the preview button was still there in the GM release of MFPF 7.0.
I think you might have hit APAR PI37266:
MFP OPERATIONS CONSOLE: PREVIEW OF COMMON RESOURCES BUTTON MUST BE
HIDDEN IN PRODUCTION ENVIRONMENT
So, you should update your installation to the latest available 7.0 iFix, whereh the preview button is not longer available.

How to make Titanium (SDK) work?

After an update to Titanium SDK 3.5.0 on MacBooks with Yosemite there occur several issues on all my developer machines, which prevents me from working on current projects:
The issues
"ti info" stops due to an exception in longjohn.js (see attached below)
"ti setup" stops with another exception while spawning a childProcess
Titanium Studio doesnt find my iOS SDK, although there is at least iOS SDK 8.1 installed and work perfectly in XCode (further information provided below)
After each start of Titanium Studio there occurs an error dialog stating "An internal error occured during Computing SDK Info, java.lang.NullPointerException", which seems to be related to the Issue under #3, which i mentioned above.
Because of the points mentioned above it is not possible to build any iOS Application with titanium
The installed versions:
node: 0.12.0
npm: 2.5.1
Titanium CLI: 3.4.1.201410281727
Titanium SDK version: 3.5.0.GA
java: 1.8.0_25
OSX: 10.10.2 (Yosemite)
XCode: 6.1.1
iOS SDK: 8.1
The error messages
1. "ti info": (in terminal)
Titanium Command-Line Interface, CLI version 3.4.1, Titanium SDK version 3.5.0.GA
Copyright (c) 2012-2014, Appcelerator, Inc. All Rights Reserved.
Please report bugs to http://jira.appcelerator.org/
|[ERROR] Failed to run command "info"
/usr/local/lib/node_modules/titanium/node_modules/longjohn/dist/longjohn.js:185
throw e;
^
logger.log (/usr/local/lib/node_modules/titanium/lib/logger.js:72:21),target.(anonymous function) [as error] (/usr/local/lib/node_modules/titanium/node_modules/winston/lib/winston/common.js:45:21),CLI.<anonymous> (/usr/local/lib/node_modules/titanium/lib/cli.js:955:17),/usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:119:25,Object.<anonymous> (/usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:24:16),CLI._fireHookCallback (/usr/local/lib/node_modules/titanium/lib/hook.js:269:12),/usr/local/lib/node_modules/titanium/lib/hook.js:248:10,/usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:232:13,async.eachSeries (/usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:130:20)
ha
2. "ti setup" (terminal)
> Where do you want to go? 1
|[ERROR] TypeError: Incorrect value of args option
at normalizeSpawnArguments (child_process.js:952:11)
at exports.spawn (child_process.js:984:38)
at run (/Users/<user>/Library/Application Support/Titanium/mobilesdk/osx/3.5.0.GA/node_modules/node-appc/lib/subprocess.js:47:14)
at Object.detect (/Users/<user>/Library/Application Support/Titanium/mobilesdk/osx/3.5.0.GA/node_modules/node-appc/lib/jdk.js:71:3)
at async.parallel.jdk (/Users/<user>/Library/Application Support/Titanium/mobilesdk/osx/3.5.0.GA/node_modules/titanium-sdk/lib/android.js:71:13)
at /Users/<user>/Library/Application Support/Titanium/mobilesdk/osx/3.5.0.GA/node_modules/async/lib/async.js:524:25
at /Users/<user>/Library/Application Support/Titanium/mobilesdk/osx/3.5.0.GA/node_modules/async/lib/async.js:111:13
at Array.forEach (native)
at _each (/Users/<user>/Library/Application Support/Titanium/mobilesdk/osx/3.5.0.GA/node_modules/async/lib/async.js:32:24)
at async.each (/Users/<user>/Library/Application Support/Titanium/mobilesdk/osx/3.5.0.GA/node_modules/async/lib/async.js:110:9)
3. Titanium Studio doesnt find any iOS SDK:
I already executed:
$ sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer
Then i enter "Titanium Studio -> Preferences -> Studio -> Platforms -> iOS". The setting for iOS SDK Home is empty and shows "Not specified".
But iOS SDK for 8.1 is already installed:
Some important messages from the Titanium Studio Log File:
!MESSAGE An internal error occurred during: "Computing SDK Info...".
!STACK 0
java.lang.NullPointerException
at com.appcelerator.titanium.ui.portal.processor.MobileSDKConfigurationHelper.getVersionInfo(MobileSDKConfigurationHelper.java:133)
at com.appcelerator.titanium.ui.portal.processor.MobileSDKConfigurationProcessor.computeStatus(MobileSDKConfigurationProcessor.java:74)
at com.aptana.configurations.processor.AbstractConfigurationProcessor.getStatus(AbstractConfigurationProcessor.java:154)
at com.appcelerator.titanium.ui.portal.actionController.MobileSDKActionController$1.run(MobileSDKActionController.java:127)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
!MESSAGE An internal error occurred during: "Sending Analytics Ping ...".
!STACK 0
java.lang.NullPointerException
at com.aptana.usage.internal.DefaultAnalyticsEventHandler.getAnalyticsLogger(DefaultAnalyticsEventHandler.java:207)
at com.aptana.usage.internal.DefaultAnalyticsEventHandler.sendEventSync(DefaultAnalyticsEventHandler.java:241)
at com.aptana.usage.internal.DefaultAnalyticsEventHandler$1.run(DefaultAnalyticsEventHandler.java:75)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
!ENTRY com.aptana.core 4 1 2015-02-20 11:37:18.555
!MESSAGE sudo: a password is required
!ENTRY com.appcelerator.titanium.core 4 0 2015-02-20 11:38:17.801
!MESSAGE (Build 3.4.1.201410281727) [ERROR] Unable to locate the CLI executable. Please restart Studio or use Help > Check for Titanium Updates to install Titanium CLI.
(Funny side effect: asking questions like this one in appcelerators developer forum will be rejected immediatly with the message "This data was not accepted because it was flagged as spam." (i tried it out in multiple variations))
What can i do know?
Using the older version of Node (10.33) resolved the issue for me.
I used the node package manager to install "n" which allows you to switch versions (you'll need to run it as sudo):
npm install -g n
Then switch the version, also as sudo:
n 0.10.33
Funny fact: Appcelerator Titanium isn't working with Node 0.12.
To solve all these issues with one step i only needed to switch back from Node 0.12 to Node 0.10.35.
(OS Yosemite)
If anyone else is having this issue, please check permissions to the following folder:
/Users/user.folder/Library/Application Support/Titanium/mobilesdk/osx/
Make sure to apply permissions to all subfolders / files. I had a permissions issue on my machine, after re-installing titanium 2 times, downgrading node to all kinds of different versions, and following all instructions in various stacked overflow threads.

IBM Mobilefirst CLI - Server start issue

I recently installed IBM MobileFirst CLI on my Mac, but I don't seem to be able to start the Server. See error below. I searched the internet and found that there is a bug in JDK which causes the JavaLaunchHelper error. I downloaded the beta version that supposedly fixes the issue from here - JDK Download Link
. But this doesn't help either. Any other help is appreciated.
Imayas-MBP:EmployeeDirectory imaya$ mfp start Initializing
MobileFirst Console. objc[18564]: Class JavaLaunchHelper is
implemented in both
/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/bin/java
and
/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/libinstrument.dylib.
One of the two will be used. Which one is undefined. Starting
server worklight. Server worklight start failed. Check server logs
for details.
/Users/imaya/.ibm/mobilefirst/6.3.0/server/wlp/bin/server: line 744:
18563 Abort trap: 6 "${JAVA_CMD}" "$#" > "${JAVA_CMD_LOG}"
2>&1 Error: The MobileFirst server failed to start. The port may be in
use by another instance of a running server, or the server may not
exist.
The JavaLaunchHelper error is not the problem here; Anyone using Java 7 will experience it, but things will work regardless.
The problem here is the second error:
The MobileFirst server failed to start. The port may be in use by
another instance of a running server, or the server may not exist.
Verify you do not have an already running server, that was started either by the CLI or by MFP Studio in an Eclipse installation.
In the command line, run mfp stop
In Eclipse, well, quit it
Make sure the Java process is not running
Then, start over. Using the CLI, create a new project and application and try to start the server. For example:
cd /Users/idanadar/Desktop
mfp create testProject
cd testProject
mfp add hybrid testApp
mfp start
mfp build
mfp deploy
mfp console
On OSX, you can locate and kill a process holding open a port using the following:
Run (assumes port 10080):
$ lsof -i :10080
Then if a process is shown, run the following using the shown Process ID:
$ kill -9 {PID}