I am newbie in DOTs programming. I Installed a Domino server 9.0 social edition as enterprise server.
I think DOTS framework is inbuilt with this server. and just after installation and configuration i am able to exchange emails. No problem with it but when i execute the command "load dots" i got the following exception:
> load dots
> Exception in thread "main" java.lang.NoClassDefFoundError: com.ibm.dots.launcher.OSGiProfile
Caused by: java.lang.ClassNotFoundException: com.ibm.dots.launcher.OSGiProfile
at java.net.URLClassLoader.findClass(URLClassLoader.java:434)
at java.lang.ClassLoader.loadClass(ClassLoader.java:672)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:358)
at java.lang.ClassLoader.loadClass(ClassLoader.java:638)
[08E4:0002-0B80] 07/14/2014 12:58:53 PM Unable to access OSGiProfile class, make sure the launcher.jar is in osgi-dots directory
[08E4:0002-0B80] 07/14/2014 12:58:53 PM Domino OSGi Tasklet Container terminated
But when i create a directory in domino/ directory named "osgi-dots" and copy the contents of osgi and launcher.jar and dotssec.jar files.
i got the following exception:
> load dots
> java.lang.NullPointerException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.ibm.dots.launcher.OSGiProfile.frameworkStarted(OSGiProfile.java:974)
at com.ibm.dots.launcher.OSGILauncher.startOSGI(OSGILauncher.java:280)
at com.ibm.dots.launcher.OSGILauncher.launchOSGIFramework(OSGILauncher.java:145)
[1E74:0002-1AAC] 07/14/2014 03:49:59 PM Domino OSGi Tasklet Container started ( profile DOTS )
Please tell me what is this problem i am facing and what these outcomes says.
By default DOTS is not fully installed on the server. You need to install the OpenSocial component add-on.
Part numbers for that are here.
http://www-01.ibm.com/support/docview.wss?uid=swg24033984
Be sure to download the matching OpenSocial component for the Domino Server you are running. For example the V9.0 release listed here will not install on a Server installation of V9.0.1.
In case page vanishes.
OpenSocial component V9.0 installers
CIF0JEN
IBM Domino Social Edition OpenSocial component V9.0 32 bit for Windows English
CIF0QEN
IBM Domino Social Edition OpenSocial component V9.0 32 bit for AIX English
CIF0MEN
IBM Domino Social Edition OpenSocial component V9.0 32 bit for Linux for xSeries English
CIF0KEN
IBM Domino Social Edition OpenSocial component V9.0 64 bit for Windows English
CIF0LEN
IBM Domino Social Edition OpenSocial component V9.0 64 bit for AIX English
CIF0REN
IBM Domino Social Edition OpenSocial component V9.0 64 bit for IBMi English
CIHU1EN
IBM Domino Social Edition OpenSocial component V9.0 64 bit for Linux for xSeries English
CIF0NEN
IBM Domino Social Edition OpenSocial component V9.0 64 bit for Linux for zSeries English
Related
Hi I recently updated MobileFirst Version from 7 to 8 and the application working perfectly on MobileFirst Development Kit Server (with Android, iOS, Browser Environment).
But after I have deploy to on premise MobileFirst Server version 8. What happened is the only environment or platform that visible on server is iOS as you can see in screenshot below.I have successful deploy all 3 platform but the other two platform not visible
We couldn't find any information on IBM knowledge Center website
Thank you.
This happens if, during installation of IBM MobileFirst Platform Server 8.0 ( using Installation Manager), you select the option "Install IBM MobileFirst Platform Foundation for iOS" in the General settings panel. If this option is chosen, iOS will be the only platform visible in the MobileFirst Operations Console.
Once the choice has been made during installation, you cannot reset it later. You will have to uninstall and re-install , and choose not to select "for iOS" option. Keep the default option (No) as-is in the Install IBM MobileFirst Platform Foundation for iOS section of the General settings panel.
Details on each step during installation, can be found in this link.
After applying latest iFix( 8.0.0.0-MFPF-IF201708031112) to the IBM MobileFirst Server 8.0.0 and cordova-mfp-plugin( v8.0.2017072706), MFPF Runtime still shows the older version no (8.0.2017070506). Due to the mismatch of the server runtime version and mfp plugin version we were not able to connect to the server and obtain accessToken in our mobile application.
Below is the version info log captured from server messages.log file.
[8/9/17 10:26:02:750 EDT] 00000025 com.ibm.mfp.server.core.internal.logging.ServerInfoLog I
MFP version: 8.0.0.00-20170803-1112
MFPF runtime version: 8.0.2017070506
Running on server: Liberty, version:8.5.5.8. Running on premise
Running OS: Windows Server 2012 R2, version: 6.3
Java: IBM Corporation, version: 1.7.0
DB name: DB2/NT64, DB version: SQL10058
Application Log:
08-08 20:48:40.935 19080-19112/com.xxxxx E/null: >> Failed to connect to MobileFirst Server{"status":400,"statusText":"Bad Request","responseText":"{\"server_version\":\"8.0.2017070506\", **"errorCode\":\"PROTOCOL_MISMATCH_ERROR\",\"errorMsg\":**"There is a mismatch between the SDK versions used for this application. If you upgraded the SDK, please create a new application version.\"}","errorMsg":"There is a mismatch between the SDK versions used for this application. If you upgraded the SDK, please create a new application version.","errorCode":"PROTOCOL_MISMATCH_ERROR"}
08-08 20:48:40.950 19080-19112/com.xxxxx E/null: Fatal error - Client was unable to connect to MFP Server
The most likely cause of the issue is this -
you had application registrations when your server was at an iFix level prior to February 2017. There were Dynamic app authenticity feature related changes in the February build (details here), which does not apply directly to earlier application registrations. Owing to which due to this it is ending up with "Protocol Mistmatch Error".
In order to resolve the issue, increment your application registration version in MFP Operations Console & in your client application. Rebuild the client application and it should connect to the server successfully.
Whenever I am trying to deploy application its showing following message? How can I resolve it?
FWLSE3030E: The runtime "HelloWorld" does not exist in the Worklight
administration database. The database may be corrupted.
I am using Eclipse Luna Java EE 64 bits , IBM MoblieFirst Studio 6.3, JRE 1.8 and JDK 8.
IBM MobileFirst Platform does not support Java 8.
Downgrade to either Java 6 or Java 7.
It should then work.
The following is my setup:
WebSphere Application Server v8.0 express Edition
IBM DB2 10.1 Server Edition
IBM Worklight Server Consumer Edition v6.0
Worklight Studio v6.0 Consumer edition Eclipse plug-in
JDK 1.7
To perform installation task i followed the IBM Worklight v6.0.0 infocenter "Installing & Configuring" section.
After Deploying app on the Application Server when i am accessing app using
localhost:9080/Hello/console it shows the error of "Worklight Project not initialized".
Thanks,
It would help if you edit your question and detail how did you install (deploy) Worklight on your copy of WAS. This will help in finding out any possible errors in your steps.
Please make sure that you follow the instructions as given in the IBM Worklight Information Center: Installing Worklight Server
In addition I've found this technote regarding WAS Liberty, which talks about the same error message: http://www-01.ibm.com/support/docview.wss?uid=swg1PM88638
I'm having problems migrating a PowerBuilder application from XP to Windows 7.
We've built the application in PowerBuilder on Windows XP, and when we attempt to install components in to component services on Windows 7 machines, we get compatibility errors. Everything works great on Windows XP. But I think because the DLL's on 7 are so different, it's having problems.
If the program was built using a PowerBuilder IDE in a Windows 7 environment, would that possibly fix the problem?
The application is divided into
- a server component running on Server 2003
- a client component which installs sucessfully on Win7
- proxy components that are generated into an MSI when the server components are installed.
The problem is only the proxy. The MSI doesn't want to work on Windows 7.
Without the proxy installed on the client desktops, the client can't communicate with the server.
When I run the MSI in compatibility mode on Windows 7, I get some details of the error. Here they are
Program Compatibility Issues found Incompatible Application Fix
application CCS_Proxy_XP_Exports
Issues found Incompatible Application CCS_Proxy_XP_Exports is
incompatible.
Fix application CCS_Proxy_XP_Exports Provides steps to fix the
incompatible application. CompatMode CompatMode UserVerifySolution
User Verification of Solution Verify_NO
Detection details Collection information Computer Name: ##########
Windows Version: 6.1 Architecture: amd64 Time: Wednesday, November
14, 2012 11:56:36 AM
Publisher details Program Compatibility Make older programs run in
this version of Windows. Package Version: 1.5 Publisher: Microsoft
Windows
Program Compatibility Make older programs run in this version of
Windows. Package Version: 1.0 Publisher: Microsoft Corporation
If I view more details on the event log, I get the following
“Product: Client Communications (Application Proxy) -- Error 1928.
Error registering COM+ Application. Contact your support personnel
for more information.”
General idea
Actually dll on the win7 platform are not different from previous ones. There can be differences related to the multiple and different C runtimes that live now in the WinSxS dll-hell directories but this should not impact powerbuilder (as I can say from my 11.5 classic release experience).
I suspect that you might have some problems related to the UAC and or ACL management. I recently upgraded some legacy PB applications by adding compatibility to the Vista / Win7 specifications.
In short : the application must run without needing administrative privileges, and must not try to modify data in privileged places like c:\ or c:\windows.
Thus everything must no more be installed in program files directory. The application binaries can be deployed in program files but if the application need to create / modify some files they must be deployed in a ProgramData subdirectory for user-shared datad and / or in the local user data files for the private data. The application has to be modified to create or find the files in the correct directories. If you do not comply to the standard, the file virtualization mechanism can hide a lack of rights and can simulate the files in a VirtualStore directory in the user local data but is just a workaround and it provides some other problems.
Com+ error
Given you error messages, if the proxy is also a PB application, given the fact that PB only produce 32bits binaries and that your system is a 64bits one, maybe that the tips to register a 32b COM+ onto a Win2008 could help you?
Thought, your proxy exe/dll file does not have manifest or manifest does not contains compatibility section. Try to add compatibility info to manifest.