I have deployed the war file project in context path /example
. Also i have uploaded the .wlapp and adapter in worklight console.
Where do point my application Build path to work in different server?
Should i point to /example war file path?
This is my reference on:
http://www-01.ibm.com/support/knowledgecenter/SSHSCD_6.3.0/com.ibm.worklight.deploy.doc/devref/t_transporting_the_app.html
To change the context root when building for a remote server, you need to right-click the application folder and select Run As > Build Setting and Remote Target.
In the window that will be displayed you need to set the remote server's server details. So those would be: protocol://host-or-ip:port/your-context-root.
Sounds like you should replace "your-context-root" with your own.
I have solved the problem. When war file project is installed it will became an runtime in IBM MobileFirst Platform Operations Console .
So you need to choose that runtime install .wlapp and .adapter in runtime like /example.
IBM MobileFirst Platform Operations Console
---->goofo(war file)
----->adapter
----->wlapp
---->test(war file)
----->adapter
----->wlapp
Related
I have a ASP.NET MVC project locally, but want to push to a remote server so that others can use that website. I have login access to the remote server.
Is this what i need to do?
1) add a folder to IIS in the remote server
2) copy my files to the folder on remote server. If so, which files should i copy?
If you're using Visual Studio (not code) then right click on the project and select publish, then select the options to publish to a local folder. Copy all files in your published folder to your server.
If you're using ASP.NET Core then you can also navigate to the project folder and use the following command
dotnet publish -c Release -o PUBLISH_PATH_HERE
You will need to ensure that the server has your version of .NET runtime installed.
Create a release publish profile, publish, grab the files from the directory it published to. This is the simplest way. You can automate this process if you have many releases. For example publishing directly to the server or checking code into a source control of some kind and having it publish to the server.
Initially we had the application server as a separate one. The communication to the Application Server from worklight servers using adapters. But currently we are moving the Application Server code to the Worklight's Server folder. We are able to call the java class (Simple java class not servlets) using HTTPAdapter. But it is difficult to communicate with the servlet (which is included in the server folder) using HTTPAdapter. Plese provide any solution?
If I understand correctly, you have put some servlet classes in your Worklight server folder. As they are Java classes they are now visible to your adapters. However servlets to be true servlets must be deployed to a JEE servlet engine, with appropriate configuration. You can deploy Servlets (in a WAR file of their own) as a separate JEE application on the same server as Worklight, but you cannot package them inside Worklight itself.
edited in response to your clarification:
You want to consolidate your servlet application, which is providing data accessed via the worklight adapter onto the same server instance as the worklight server. The Worklight Server is actually a JEE application deployed to one of the supported JEE servers, usually WebSphere Liberty which is supplied with Worklight, and the Worklight Server is in fact packaged as a WAR file. Your Data Provider servlet will also be packaged as a WAR file, all you need to do is deploy that WAR to the Liberty server you are currently using for worklight.
If you are doing this is development in Worklight Studio you can find the relevent folders by looking under "Worklight Development Server". You can drop the WAR into the apps folder and if necessary edit the server.xml to add any extra configuration:
WorklightServerConfig/servers/worklight/server.xml
See: http://www-01.ibm.com/support/knowledgecenter/SSCKBL_8.5.5/com.ibm.websphere.wlp.nd.doc/ae/twlp_dep_war.html
a second edit to try to explain again.
The Worklight Project represents your application, when you deploy to the Worklight Server a WAR file is created let's call this MyApp.WAR, that can be deployed to a WebSphere Application Server, inside Worklight Studio you are automatically given a WebSphere Liberty Profile. That Liberty Profile's configuration can be seen in the Project Worklight Development Server. Key Idea here you have one App Server that Liberty Profile, and you deploy the MyApp.WAR file to create what we usually call the Worklight server, it's the MyApp.WaR that is serving your Worklight console. That WAR file is derived from the contents of your project's server folder, this folder's name is a little misleading it's not the "server" itself it's your project-specific WAR information.
Now in addition you want to run a Servlet you already have packaged as a WAR file, let's call this Data.WAR. The key point is that you need to run Data.WAR on the Worklight Developmennt Server, the Liberty Profile. You are not including this DATA.WAR file into your project's server folder, that would effectively put DATA.war inside MyApp.WAR. Instead all you need to do is put Data.WAR in the Worklight Developmennt Server's apps folder and adjust the server.xml.
So: Step 1. Get Data.WAR running in the Development Server. Verify that from a browser you can call your expected servlet. Note the URL that works. Do not make any attempt to use your adapter until you have verified this.
Step 2. Adjust you adapter to call that URL.
I have deployed a war on the Weblogic server. I would like to know if that war file happens to be deleted/removed from its physical location on the server from where it was deployed, what will be the impact of this?
Regards,
Dushyant
When you are deploying the war file, there is a page of optional settings, one of which is "Source Availability".
If you choose "Use the defaults defined by the deployment's targets" or "Copy this application onto every target for me" you don't need to worry about the original war file being deleted as it has already been copied to each server. The deployment uses staged mode for all the managed servers and non-staged mode for the Admin server.
If you choose "Make the deployment accessible from the following location" and then delete that war/directory your application will no longer continue to work. This is non-staged mode.
I'm using the latest version of SpringSource Tool Suite (STS). I have set up a Java project. My code has an Ant build file that packages a WAR. I have Tomcat 6.0.24 installed locally on my Mac 10.6.3. Can someone point me to how I deploy my project onto the server from the IDE and as such, set up debugging with breakpoints?
Thanks, - Dave
Here is what you need to do:
Open up the servers view inside of STS.
Create a new Tomcat instance, and point it to your locally installed Tomcat. (Alternatively, you can use the pre-installed tcServer instance, which is essentially Tomcat with a few extra things like Spring Insight).
Right-click on your project and select Configure -> Convert to Faceted Form...
In the dialog that comes up, choose Dynamic Web Module
Now, you should be able to drag and drop your project onto the server instance.
After that, right-click on the server instance and select "Debug"
You can find more detailed instructions here:
http://www.ibm.com/developerworks/library/os-eclipse-tomcat/index.html
i have a ClickOnce application (online only) which is deployed on a network share. People can run the application by creating a shortcut to i:\ApplicationDirectory\ApplicationName.application
where i is the letter of the drive of the networkshare.
I want to start the application over HTTP. For this, I need the .Application file to be accessible through my webserver. However I am unable to select the ApplicationDirectory as a virtual directory for IIS. I tried copying the .Application file to a virtual IIS path, but this makes the deployment corrupt (i also updated application_files reference in the .Application file). Is there a(nother) way to start a ClickOnce application, deployed on a network share, over HTTP?
First find your ClickonceKey.pfx, in other words the key used to sign assemblies.
Then find mage.exe, the utility for signing manifests that's part of the .NET Framework SDK. For VS2005, it can be found at %ProgramFiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin.
Then create a batch file to execute mage.exe.
Then copy the contents of the network share deployment folder to a new virtual directory on the web server.
Finally, run the batch file.
The batch file should look something like this:
mage.exe
-update >>path to your application manifest in the virtual directory<<
-providerurl >>location of application manifest virtual directory<<
-certfile Clickoncekey.pfx -password >>your password<<