PowerServer cannot be accessed after installation - powerbuilder

I've been tasked to use a new version of powerbuilder and test it's functionalities . One of it's components were powerserver that will enable all PB application to be deployed on either web and mobile.
I have installed all neccessary powerserver items on my local IIS but when i access the url http://localhost/AEM it throws an internal server error:
Handler "PageHandlerFactory-ISAPI-4.0_64bit" has a bad module "IsapiModule" in its module list
This AEM has it's own Application App Pool called AppeonAppPool. The solution i made to access the AEM is to changed the managed pipeline mode from classic to integrated. With implementing that, i can access AEM but when im trying to deploy the PB app using the PowerServer Toolkit, the IDE throws an error: Failed to connect to powerserver "Local PowerServer"
Upon installation, i have not changed anything rather used the default values.
can anyone help me or point where and what i missed?
thanks!
Im using Appeon Powerbuilder 2017 R3 universal

Related

Android app crashes when connecting to mongodb

I'm new to Android development and in my first application I'm trying to connect to mongodb. What have been done:
Installed latest Android Studio (2.2.3) on Windows 10.
Added dependency to application build.gradle:
compile 'org.mongodb:mongodb-driver:3.4.2'
Code to connect to mongodb:
MongoClientURI mongoUri = new MongoClientURI("..."); // here specified the connection string that worked fine for desktop mongodb client
MongoClient mongoClient = new MongoClient(mongoUri);
Everything compiled and deployed to a virtual device successfully. But when I try to execute this line:
new MongoClient(mongoUri);
an exception is thrown:
java.lang.NullPointerException: Attempt to invoke virtual method 'java.security.CodeSource java.security.ProtectionDomain.getCodeSource()' on a null object reference.
In debug I can see that ProtectionDomain implementation just returns null. However mongodb expects some reasonable value from that method.
According to other questions on StackOverflow it seems that people are able to connect to mongodb using such an approach. What I'm doing wrong?
The Mongo Java Driver should not be used on Android because it's not designed for Android JRE (which is not exactly Java JRE). Android JRE has some limitations, especially on cryptography and security classes, and that's why the Mongo Driver does not run on Android.
As suggested by cricket_007, to support Android apps, you should write a REST or SOAP API in Java that uses Mongo driver to get and manipulate your data, and then serve them with an HTTP Server.
From the Android app, you will call your REST API instead of Mongo driver directly.

Delphi and quickbooks examples

We have created a delphi app to connect to quickbooks 11 pro.
We are trying to use BeginSession from the TLB file and it works fine when creating a new company but after restoring a file from one of our clients, which might have been from a newer release it won't connect. But QB doesn't give any error messages, is there a way to make this happen ?
Thanks
Andy
Download the QuickBooks SDK if you haven't already done so, then try using the SDKTestPlus3 tool to see if it can access the company file. If it can't the problem is probably with the company file, if it can the problem is probably with your program.

WLclient is not getting initialised

I am trying to create a android application using native api application in worklight.I created the client it was success, but got the error message like
' WLClient.invokeProcedure() will not be executed because WLCLient is not initialized, ensure WLCLient.connect function has been called.
'
Steps used
1) First i created a natvie api appklication
2) Create and configured an Android native application
3) Initializing the WLCLient
4) Invoking a Worklight procedure
5) Receiving a procedure response
using the documantation ftp://public.dhe.ibm.com/software/mobile-solutions/worklight/docs/v505/Module_09_2_-_Android_Development_Using_Worklight_API_in_a_Native_Application.pdf
In native applications you are indeed required to implement and call the connect() method before attempting to call the invokeProcedure method in the connect's onSuccess.
Notes:
The adapter and NativeAPI must be deployed to the server to get a response back
The native application's wlcient.properties file must point to the server host address
It is also expected that you'll share at least some code snippets of what you've actually implemented and the full error stack in order to debug the error.
That said, review the Getting Started sample application created just for this. Read the tutorial and review and implementation in the native project. The studio project is required in order to deploy the adapter and app artifacts to the server.
Training module: Invoking adapter procedures from native Android applications
native project, studio project
See all Getting Started training materials for Worklight 6.2
Note that you are linking to documentation for Worklight 5.0.5; if you are using a newer version of Worklight like Worklight 6.0, 6.1 or 6.2, you cannot use that old documentation. Use the one I've pointed to.

Not able to download metadata for application in force.com IDE

I am facing a few problems when trying to integrate the force.com ide with salesforce.com.
Currently i am using eclipse(4.22 Juno) and have installed the plugin Force.com IDE(2.9) and have a developers version in salesforce.com. I was able to successfully connect to salesforce without any errors thru force.com ide, by creating a new application with the name of the application that i have created in the web version.
Right now the application is created with the sub folders classes, triggers etc... but they are empty. I also tried setting the proxy in the connections of eclipse. But even that does not seem to work.
Does anybody have any idea what could be wrong.
Thanks--
Can you post the content of your package.xml file? It's kind of project definition, it contains info which files (objects, classes, pages, reports, profiles...) you want to download & push changes to.
Check http://wiki.developerforce.com/page/An_Introduction_to_Force.com_Metadata for example - have you skipped step similar to this?

Attempting to develop an Android app with PhoneGap and Meteor - need assistance

Looking for some help building an Android app using PhoneGap with Meteor.
I've seen answers here on how one can essentially build a "thin-client" PhoneGap app that points to a meteor server and renders it and that essentially works for me.
However, I'd like to do this a little more client-side ("thick-client") and therefore would like to bring the Meteor client side code (js,css) into PhoneGap and have that code call the Meteor server remotely. I've seen some approaches to hack in a hardcoded URL in places but they aren't working for me (app.html comes up blank in the emulator - I don't think any/all of the referenced js files are loading properly).
I've also attempted to change my meteor client code to use Meteor.connect, but I don't know how to authenticate the user with the remote server. I'm using the accounts- packages and it always authenticates with my local machine server.
So my questions:
(A) Has anyone pulled something like this off? (esp. for Android using a Windows dev machine)
(B) If this is possible, what files need to be pulled from the meteor bundle into the phonegap folders and where exactly do they go? What other tweaks are necessary?
(C) If using Meteor.connect is the way to go (for remote data), how does one tell the auth packages to talk to the remote server?
Thanks mucho..
It would require some manual editing but it should be possible:
Make sure that all your images/resources are referenced such that they can be available locally (/ use relative paths)
In your project directory use meteor bundle to create a tarball of your project http://docs.meteor.com/#meteorbundle
Extract your tarball and use the index.html file in your PhoneGap or Cordova project www folder, perhaps after a network check or something as the meteor project
Copy the stuff in the static (which come from the public directory of your meteor project such as images) to your www too
Publish your bundle onto a server
Edit your index.html file so that the referenced javascript loads from your server instead
That should get all the stuff to run locally on the phone but only fetch the collections, subscriptions, meteor calls & stuff via websocket/long polling from your server

Resources