Xcp 2.1 Preview mode error - documentum

When I am trying to run the preview mode in Xcp 2.1 . I am getting the below error.
http://localhost:8888/Concordant_Insurance/reloadcontext?webby
HTTP ERROR 404 Problem accessing /Concordant_Insurance/reloadcontext.
Reason:
Not Found
-------------------------------------------------------------------------------- Powered by Jetty://
Also , when I checked the xCP designer logs i am seeing the below.
2015-09-21T11:02:01.894 INFO [Tmain] [com.documentum.fc.client.impl.connection.docbase.DocbaseConnection:377] Object protocol version 2
2015-09-21T11:02:02.519 INFO [Tmain] [com.documentum.fc.client.security.internal.AuthenticationMgr:448] new identity bundle <dfc_m0m14WKi50bKqjX3rBVf33lcIuca 1442813522 SYNPSZD4515.syntelorg.com aKqqpudgiie/TVVX5nqwOeOWKMSSD3W19n1LkWPftu/4ahAW5E+iLN7LsrTgjpcgLuVaNMex7jb64Cgupy+KitzI/liMqlEWY8iQqa2kDsFO3x7uzjqAnF+FYqIvinHg0sjw7Z1mTqdAzUJiFmNzRcYzyeaRHPE/cFyB0WzW4VY=>
2015-09-21T11:03:45.821 INFO [Tmain] [com.documentum.deployment.service.DeploymentManager:113] Catalog path is set to: [/C:/Users/NT5023515/Desktop/Documentum self Doc/xCPDesigner/plugins/com.emc.ide.external.dfc_2.0.0.201502150958//deploymentCatalog/]
2015-09-21T11:05:02.910 INFO [Tmain] [com.documentum.fc.client.impl.connection.docbase.DocbaseConnection:377] Object protocol version 2

You have to remove the target folder located inside your Application workspace

Related

ASP.NET Core 3.0 project fails to run under IIS Express: HTTP Error 500.30 - ANCM In-Process Start Failure // ERROR: Unknown command '%LAUNCHER_ARGS%'

I migrated a project from asp.net core 2.2 to 3.0 following the migration guide.
After a couple issues were resolved, starting it with dotnet run worked fine.
However when I try to run/debug with IIS Express, I get the following error:
HTTP Error 500.30 - ANCM In-Process Start Failure
Common solutions to this issue:
The application failed to start
The application started but then stopped
The application started but threw an exception during startup
Troubleshooting steps:
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect
For more information visit: https://go.microsoft.com/fwlink/?LinkID=2028265
The output window for "ASP.NET Core Web Server" in Visual Studio shows the follwing error:
ERROR: Unknown command '%LAUNCHER_ARGS%'
As does an error entry in the windows event viewer
<EventData>
<Data>Application '/LM/W3SVC/2/ROOT' with physical root 'C:\Path\To\Project\' has exited from Program.Main with exit code = '1'. First 30KB characters of captured stdout and stderr logs: ERROR: Unknown command '%LAUNCHER_ARGS%'</Data>
<Data>Process Id: 7092.</Data>
<Data>File Version: 13.0.19258.0. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: aee5e4080331553ea9dfb7fb388b6d72f715bf6a</Data>
</EventData>
Immediately followed by:
<EventData>
<Data>Application '/LM/W3SVC/2/ROOT' with physical root 'C:\Path\To\Project\' failed to load coreclr. Exception message: CLR worker thread exited prematurely</Data>
<Data>Process Id: 7092.</Data>
<Data>File Version: 13.0.19258.0. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: aee5e4080331553ea9dfb7fb388b6d72f715bf6a</Data>
</EventData>
My initial thought was that there was an issue with my system setup, but a fresh ASP.NET Core 3.0 project runs without issues in IIS Express. I compared the two applicationhost.config files of the projects and they're identical (except differences like the project name). I also can't find any meaningful differences in the other project files (Project.csproj, appsettings.json, launchSettings.json). I also tried deleting the .vs folder and .user files .
The error messages suggests that it's not a problem with my code. As does the fact that there's no exception the attached debugger breaks at and that everything seems to work fine using dotnet run. Yet a fresh project created via template runs without those issues.
I was able to identify the issue. One mistake I made was to attribute the ERROR: Unknown command message to ASP.NET, when it was actually our application that complained.
The %LAUNCHER_ARGS% parameter is still passed to the application, but it's no longer set in an in-process hosting context.
More details here: https://github.com/aspnet/AspNetCore/issues/14735

"Adapter deployment failed: Could not resolve placeholder" error in IBM MobileFirst 6.3

I'm unable to read a property's value from worklight.properties file.
I added property as publicProtocol=http in wroklight.properties file and used the property in my adapter.xml as <protocol>${publicProtocol}</protocol> but I'm getting the following error:
Adapter deployment failed: Could not resolve placeholder
'publicProtocol'
This works fine for me using IBM MobileFirst Platform Studio 6.3.0.00-20150214-1702
Created a new project with a HTTP adapter.
Added to server\conf\worklight.properties the following: myCustomProperty=http
The server was automatically restarted
Changed adapters\myAdapter\myAdapter.xml as follows and re-deployed the adapter:
- <protocol>http</protocol>
+ <protocol>${myCustomProperty}</protocol>
To verify that it worked I simply:
Right-click the myAdapter folder and selected Run As > Invoke MobileFirst Procedure and click on OK to invoke the default procedure.
A browser window opened with a successful invocation.

Can't deploy adapter/application in IBM MobileFirst Platform Foundation 7.0

In a production installation over 'WAS_LIBERTY_CORE_V8.5.5.4' with 'DB2':
I have now a simple configuration in server.xml.
The mobilefirst console shows the runtimes but I can't deploy adapters or applications. This is the content of messages.log. This 2 lines appears every attempt to upload an adapter/application:
[19/04/15 19:19:37:667 CEST] 0000008e org.apache.wink.server.internal.registry.ResourceRegistry I The system cannot find any method in the com.ibm.worklight.admin.services.RuntimeService class that supports POST. Verify that a method exists.
[19/04/15 19:19:37:683 CEST] 0000008e org.apache.wink.server.internal.RequestProcessor I The following error occurred during the invocation of the handlers chain: WebApplicationException (405) with message 'null' while processing POST request sent to http://MACHINENAME:9080/wladmin/management-apis/1.0/runtimes/test/
More info:
wlp.install.dir = C:/IBM/WebSphere/Liberty/
java.home = C:\Program Files\Java\jdk1.7.0_79\jre
java.version = 1.7.0_79
java.runtime = Java(TM) SE Runtime Environment (1.7.0_79-b15)
os = Windows Server 2008 R2 (6.1; amd64) (en_US)​
DB: DB2 in localhost
Complete server.xml file: https://drive.google.com/file/d/0BxAEyIioPI2YT2NPZXdCcktoT1U/view?usp=sharing
Complete console.log file: https://drive.google.com/file/d/0BxAEyIioPI2YUDhLZDQ0Qmgydk0/view?usp=sharing
Complete messages.log file: https://drive.google.com/file/d/0BxAEyIioPI2YdUREcjcyd3JYNGs/view?usp=sharing
I'm tried with other Java version like 'SDK_JAVA_TE_V7.0_WASLC_V8.5.5', with other runtimes, reinstalling all...
Per the comments, the error appears to happen only in IE 9.
As a work around, use a different browser such as Safari, Chrome, Firefox, Opera, etc... in order to deploy artifacts.
The issue with IE 9 will be investigated.

Error in transporting an application from development worklight to Worklight Server Consumer Edition

I am using IBM Worklight environment. I have created a small application "SampleHybridProject" using Worklight Developer studio and tested it successfully.
Now when I am trying to deploy it on the Worklight Server Consumer Edition, and hitting the following URL: http://mymachine.com:9080/SampleHybridProject/console
I am getting this error in my browser:
Error 404: com.ibm.ws.webcontainer.servlet.exception.NoTargetForURIException: No target servlet configured for uri: /SampleHybridProject/console
I am using Worklight Edition 5.0.6. The Worklight Server is default "WAS with Liberty profile".
Here are the properties that I changed in worklight.properties file.
publicWorkLightHostname=localhost
publicWorkLightProtocol=http
publicWorkLightPort=9080
publicWorkLightContext=/SampleHybridProject
wl.db.type=MYSQL
wl.db.url=jdbc:mysql://mysqlinstalledonmypc:3306/WRKLGHT
wl.db.username=root
wl.db.password=admin
Here are the changes that I made in application-descriptor.xml:
<worklightServerRootURL>http://${local.IPAddress}:9080/SampleHybridProject</worklightServerRootURL>
Can you tell me what I am doing wrong or what I need to do?
I have found the problem and solved it. The problem is I was having this error in console.log file:
Error creating bean with name 'txManager' defined in URL [jar:file:/C:/ProgramData/IBM/Worklight/WAS85liberty-server/wlp/usr/shared/resou‌​rces/lib/worklight-jee-library.jar!/conf/core.xml]: Invocation of init method failed; nested exception is java.lang.LinkageError: loader constraint violation: loader (instance of com/ibm/ws/classloading/internal/UnifiedClassLoader) previously initiated loading for a different type with name "javax/sql/DataSource"
This was because I had a jar in the server/lib folder of my project which was causing this problem. I removed the jar from server/lib folder and redeployed the .war file. Now the console is getting loaded.
Are you getting any deployment errors in your liberty logs? A 404 on the context root generally means either the WAR was not found, or the context root defaults to something other than 'SampleHybridProject'. If the WAR appears to be loading correctly, it will output where it is listening on similar to:
[AUDIT ] CWWKT0016I: Web application available (default_host): http://[hostname]:port/SampleHybridProject/*
If it says the context root is anything other than SampleHybridProject, you can set it in the tag in liberty's server.xml:
<application id="SampleHybridProject" name="SampleHybridProject"
location="SampleHybridProject.war" type="war"
context-root="SampleHybridProject">
...
</application>

cannot find EJB reference while deploying ADF Fusion Webapp into oracle weblogic server

I created a Fusion Webapplication project with Oracle jdeveloper 11g (11.1.5 but the same problem occours with the 11.2.1 version). Then I created a jsf page and I deployed the project to an external weblogic server (WL 10.3) with the ADF runtime support and evrithing where working.
Then I created the POJOs object (to the model project, because I have 2 proj: Model and ViewController for the web pages and backing beans) from the DB tables and a session bean who provides queries methods. After that (and so far everything it's ok) I added an ADF Data Control bound to the session bean and then I bound (via editor) one of these methods into the jsf page using an ADF table.
If I run the project using the run button everything work, but if I deploy it into both the external deployment WL server and in the internal one I get the following error
[05:30:04 PM] [Deployer:149193]Operation 'deploy' on application 'Prova_application1' has failed on 'AdminServer'
[05:30:04 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application Prova_application1 on AdminServer.: Could not setup environment.
[05:30:04 PM] Weblogic Server Exception: weblogic.application.ModuleException: Could not setup environment
[05:30:04 PM] Caused by: weblogic.deployment.EnvironmentException: [J2EE:160167]The module Prova-ViewController-context-root in application Prova_application1 uses ejb-links but no EJB modules were found for this application.
[05:30:04 PM] See server logs or server console for more details.
[05:30:04 PM] weblogic.application.ModuleException: Could not setup environment
[05:30:04 PM] #### Deployment incomplete. ####
[05:30:04 PM] Remote deployment failed
but there is such refernce into the web.xml and I bound the Model project into the deployment descriptor. I red every post in the web but I still can't face the problem.
The web.xml in the ViewController project contains the EJB reference (automatically created from jdeveloper) and I bound everithing the Model project but it still doesn't work.
In JDeveloper IDE
you need to set ejb-jar.xml path.
- Right click on your project
- Choose Project Properties
- Go to EJB Module
- Set EJB Version (For example: "2.1")
- Set ejb-jar.xml path (For example: "..\src\META-INF\ejb-jar.xml")
I hope it works..