I'm working with IBM MobileFirst 7.1, and trying to get integration for ISAM working. So far I've been working with the sample application provided here, but I'm having issues with it when working with 7.1 MobileFirst client-side tools.
If I download and unzip the v3.5 integration package, and unzip the ISAMforMobileFirst test project, and I build it with the v7.0 CLI, it builds successfully. However, if I build it with the v7.1 CLI, I get an error like this:
Migrating project from version 7.0.0.00.20150211-0917 to version 7.1.0.00.20150807-0630.
[Error:
BUILD FAILED
/Applications/IBM/MobileFirst-CLI-7.1/mobilefirst-cli/node_modules/generator-worklight-server/lib/build.xml:497: com.worklight.upgrader.UpgradeEngineException: FWLPL0019E: Migrating the ISAMforMobileFirst project from version 7.0.0.00.20150211-0917 to version 7.1.0.00.20150807-0630 has failed because Cannot parse /Users/ferriera/Downloads/AmWorklightAdapter-3.5/sample/ISAMforMobileFirst/server/conf/authenticationConfig.xml
at com.worklight.upgrader.WLUpgradeEngine.upgradeProject(WLUpgradeEngine.java:271)
at com.worklight.upgrader.ant.UpgraderTask.execute(UpgraderTask.java:100)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
A colleague also sees this exact error in MobileFirst Studio 7.1 (in Eclipse) so I'm guessing it's not a CLI-specific error.
I would assume that support for something has changed in authenticationConfig.xml in 7.1, and this hasn't been reflected in the migrator.
A few questions:
Is ISAM integration supported in 7.1?
Whilst I realise the sample application isn't technically supported in 7.1, if/since ISAM integration is, in theory it should be feasible to make it work. What's changed in authenticationConfig.xml syntax?
Edit: looks like the failure happens due to the following: <parameter name="embedded-pki-bridge-ca-p12-file-path" value="<file-path>"/> and more specifically: <file-path>.
Change it to the actual file path, and it will not fail importing.
Nothing in the authenticationConfig.xml file is about ISAM really; it's all declarations of realms, login modules, security tests...
There is a clear failure, and a PMR should be opened.
As for a local workaround, I've attempted to remove segments in the file that I thought might trigger it, but did not succeed to find a pattern that causes it...
Related
I have attempting to upgrade a web application that uses .NET Framework 4.5 to 4.8.
The application runs on a server that both compiles and runs the application, so I installed the .NET Framework 4.8 Developer Pack. I restarted the server and it has booted up successfully.
TeamCity successfully built and compiled the application and Octopus successfully deployed as per usual. However, when I now attempt to access the website, I get a 404 at the login page.
Looking at the folder structure, the file is definitely there. The code builds and runs successfully on my local machine, allowing me to login and perform any function on the system.
Is there something that I have missed running or doing on the server to get this to work?
Edit: Request for IIS Configuration
The configuration of this hasn't changed since I've upgrade the .NET Framework but here is what I have. If this isn't the configuration that is being asked about, please let me know.
Bindings
Everything else has been left as the default values.
I have created an ESB application which fails to execute the flow because the library js-engine-1.1-jdk14.jar is present in Mule Runtime server 3.9.0 Community Edition.
So I want to know how can I remove this jar js-engine-1.1-jdk14.jar from the mule runtime server in Anypoint Studio so that my flow can execute properly.
Error is :
com.sun.phobos.script.util.ExtendedScriptException:
org.mozilla.javascript.EcmaError: ReferenceError: "load" is not
defined. (#3) in at line number 3
You should never remove a jar from the runtime, under risk of breaking it. Same with thing with overriding or updating them. Instead, at least for Mule 3.x, you have to adapt your application to the libraries provided.
You didn't mention what was the error or problem why it fails. If the application is using a different and incompatible version than the one provided, then it needs to be modified to use the same one than the runtime.
In the EE you have the alternative method of fine grained class loading control though it is not useful for every use case.
The lib can be found inside plugins/org.mule.tooling.server.3.9.0_6.4.0.201710051922\mule\lib\opt. We can remove it from there.
While setting up the dashboard widgets on SonarQube 5.6.6 to display results from OWASP Dependency Check & ZAP and Xanitizer I encounter the following error message:
An error occurred while trying to display the widget "xanitizer". Please contact the administrator.
I have SonarQube running on a Windows 2008 Server R2 as a test instance.
What I did so far:
Installed the relevant plugins
Configured the plugin POM file with Windows paths (like: C:\Program Files (x86)\Jenkins\workspace\ZAP-Scanning\reports)
Created a reports either by a Jenkins job (for OWASP stuff) or by Xanitizer app.
Pointed SonarQube to the absolute path of Xanitizer report file in SonarQube GIU
Created each a SonarQube project manually
Linked the projects to the corresponding widget
The result is always the error message you can find above.
As a workaround I contacted Steve Springet directly. He pointed me to some GitHub pages, which did not help.
As I am not a developer: Is there any tutorial that might help?
Implementing Checkmarx plugin took some minutes to have scan results displayed.
Apparently I got stuck somewhere in the sonar.property files or the bridge between Windows and Linux syntax...
If helpful I can share the property and POM files with you.
This was a bug in the Xanitizer plugin. It has been fixed with version 1.4.0 of the plugin.
We have a MobileFirst application that worked with Worklight 6.2 server - production also. We are using a http adapter: <connectionPolicy xsi:type="http:HTTPConnectionPolicyType">
Currently we are changing the production server to 7.0.0. On Development Server we could test our application and all the functionalities were OK. We'we created the .war with the production server on build configuration and uploaded together with the android .wlapp . Now we receive 404 when the application tries to call any adapter function on production server. invokeProcedure onFailure returns UNEXPECTED_ERROR. This is with:
Server version: 7.0.0.00.20150312-0731
Project WAR version: 7.0.0.00.20150402-2001
Adapter name: XXXXX. Version: 7.0.0.00.20150402-2001
Application: XXXXX-android-0.9.7, Version: 7.0.0.00.20150402-2001
We have no security enabled in the application.
Is there something that must be enabled on Server in order to allow old type adapters call?
When we've tested with upgraded MobileFirst Development Studio 7.0.0.00.20150430 as development platform - same server version, and we got same 404 (Context not found), but there tries to connect with authorization/v1/clients/instance instead of /apps/services/api/XXXXX/android/query
Should a Server upgrade solve this problem? We've noticed that there are updates available.
The Server is on a https connection, but was same on WL 6.2.
By the description in the comments and the supplied messages.log, it is clear that you are attempting to use Application Authenticity Protection.
This feature worked in a certain way in v6.2 and it works in a different way in v6.3 and above.
From the comments it appears you are only adding the publickSigningKey - this is no longer enough.
See the updated Application Authenticity Protection tutorial for steps to follow: https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-7-0/authentication-security/application-authenticity-protection/
General steps to follow:
Setup authenticationConfig.xml with the security test
Add the security test to the environment node in application-descriptor.xml
Add the publicSigningKey to the <publicSigningKey> element
Add the application package name <packageName> element
I believe you are missing step 4.
Note that you also able to now enable the Extended Authenticity mode; follow the instructions in the tutorial.
Note about step 3: obviously the same keystore used to generate the publicSigningKey must be used when you export the signed .apk file... otherwise there will be a mismatch and the authenticity challenge will fail.
In your authenticationConfig.xml, make sure you have the securityTest available (= not commented out like in the file you've supplied in the comments below.
In your application-descriptor.xml, you are missing the securityTest attribute in the Android environment element: <android version="0.9.9"> change to <android version="0.9.9" securityTest="customTests">
I'm trying Windows Azure now.
I have been following instruction from
https://www.windowsazure.com/en-us/develop/java/java-home/download-the-windows-azure-sdk-for-java/
I'm running on eclipse helios, but when i try to install new software and enter url repository :http://dl.windowsazure.com/eclipse
Eclipse always timeout,
message on message box like bellow :
Unable to connect to repository http://dl.windowsazure.com/eclipse/content.xml
Unable to connect to repository http://dl.windowsazure.com/eclipse/content.xml
Connection timed out: connect
How to solve this, i very need it to deploy my first app on Windows Azure platform
Help me to solve this, please
Now i try to runnning azure project on Cloud Azure, but why when i try to upload cspkg file and cscfg file, the process always timeout, whereas connection is running normally when i look on ping -t
this is message when i try upload on azure hosting service :
Uploading the selected package has failed, please verify your network connection and try again.
How to solve this issue ?
it's very strange error. >-<
I think there is some problem with your network connection as I have just tested the same download location and it does work perfectly fine as below:
As you can see below I am using http://dl.windowsazure.com/eclipse URL to download the Java specific Azure components:
After that once I select "Next", the following two components are listed to be installed in my machine:
Microsoft JDBC Drive 3.0 for SQL Server (This will work with SQL Azure)
Windows Azure Plugin for Eclipse with Java
I am sure that the problem is specific to your network connection so please have it corrected.
Yes, it's foolish of me, i forget to shutting down my proxy server on My compute.After i disable it,everything gonna be alright :D
Thanks
surely I haven't meet this situation before , but just for your additional information..
Have you follow this step on installing azure #eclipse? like .net version must be >= 3.5
here are some source link for your help http://www.windowsazure4e.org/download/
I haven’t worked with Windows Azure Java SDK. But the error message is complaining the file C:\Users\workspace\AzureFirst\emulatorTools\ResetEmulator.cmd cannot be found. It would be better if you can check whether the file exists. In addition, the call stack points out you’re using Windows Azure SDK 1.4. Please try to upgrade it to 1.6 to see whether it works fine. You can find SDK 1.6 on http://www.microsoft.com/en-us/download/details.aspx?id=28045. Please install WindowsAzureEmulator and WindowsAzureSDK. The WindowsAzureLibsForNet is not needed if you don’t want to use .NET.
Best Regards,
Ming Xu.