Set EJB jar file in manager server - weblogic

Im new to weblogic Can you please advise how to set the ejb file in weblogic 11g console parameters for manager servers. I have to do the deployment of an EJB application.
Can you please help?
Thanks

Start the WebLogic Server Administration Console.
In the left pane of the Console, click Deployments and then click on Install
Locate the EAR, WAR or JAR file you would like to configure and then next
Select a Target Server from among Available Servers and then next->finish.

Mr. Pal, You could deploy the DS.jar as library it is the radio button. You might be missed that option whil deploying it. Target can be AdminServer or ManagedServers or Cluster that you can mention as per your choice.

Related

Weblogic server won’t start, because a bad.jar was deployed in it. But I can’t start the admin console, in order to remove the .jar

My Weblogic server was running fine inside my Eclipse. But then I accidentally deployed an .ear into my Weblogic server (using the server's Admin Console) which conflicts with another .ear, and now my Weblogic server won't start up. I know how to remove the .ear. The way to remove it is to go to the Admin Console, choose Deployments, checkmark the offending .ear and then choose stop and delete. But I can't get to the Admin Console because the Weblogic server won't start up.
I want to undeploy it, but I can't, because I can't start up the Admin Console. I also tried undeploying it with the command line, but the command requires communicating with a running server.
The error message in the Eclipse console says: "Failed to initialize the application 'EILoggingSharedLib [LibSpecVersion=2.22,LibImplVersion=2.22]" due to error weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed to deploy library Extension-Name: EILoggingSharedLib, Specification-Version: 2.9, Implementation-Version: 2.9, because of conflicting library Manifest values, and library information registered with the server: [Specification-Version: 2.9 vs. 2.22, Implementation-Version: 2.9 vs. 2.22]. Check the library MANIFEST.MF file and correct version information there to match server settings, or undeploy the misconfigured library."
This is the command line command I used:
C:\bea12c\wlserver\server\lib>java -cp weblogic.jar weblogic.Deployer -verbose -noexit -adminurl http://localhost:7016 -username (myusername) -password (mypassword) -name Dev12c -undeploy EILoggingSharedLib -timeout 300
weblogic.Deployer invoked with options: -verbose -noexit -adminurl http://localhost:7016 -username weblogic -name Dev12c -undeploy EILoggingSharedLib -timeout 300
Unexpected Error Initializing Deployer: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 'http://localhost:7016': Destination 0:0:0:0:0:0:0:1, 7016 unreachable; nested exception is:
java.net.ConnectException: Could not connect to /0:0:0:0:0:0:0:1; No available router to destination. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
I also tried starting the server with startweblogic.sh with the following command, using the same ID and password that I use to log into the admin console (when it was running). But it didn't help:
startweblogic.sh username=(myusername) password=(mypassword)
Thank you!
First, try to remove your application from deployed applications with Eclipse. If it does not work, edit the ${DOMAIN_HOME}/config/config.xml file and remove the declaration of your application. Then start your server.
I found a solution. My Weblogic server that had the problem was at http://localhost:7016. Since it's a localhost server, all the libraries and apps deployed to that localhost are in a directory in my C: drive where my Weblogic server installation is. I deleted the offending .ear using File Explorer, then the Weblogic server started up fine. I was able to go into the Admin Console and delete them again from there. After that, all was good. Thank you, Emmanuel and Wesley.

Intellij / Websphere run config says "address localhost:8880 is already in use"

This is my first attempt at creating a Websphere Local run configuration in Intellij and obviously I need some help.
First question: is Websphere supposed to be running when I run the configuration?
Second question: when I run the configuration and Webshpere is not running Intellij will say 'cannot ping localhost:8880', so probably Websphere should be running. When I start Websphere and then start the Intellij run config it says "address localhost:8880 is already in use" and then "Unable to open debugger port (127.0.0.1:62019): java.net.SocketException: 'socket closed'".
Here is my setup:
Third question: from the Websphere admin console I got that port 8880 is configured as the SOAP_CONNECTOR_ADDRESS. Is Intellij supposed to use that?
Thanks!
The following worked for me:
Go to run/debug configuration and click on +
Choose Remote (and not Websphere Server)
Change port to the port you want to use(I choose 7777)
To answer your question: no, if you want to start the server from IntelliJ, you should first check the server is stopped.
For solving the problem: Have you checked if WebSphere is running as a service automatically?
For doing it on Windows:
Open a "File Explorer" window
Right click on "My Computer"
Click on "Manage"
Click on "Services and Applications"
Click on "Services"
Look for "IBM WebSphere Application Server"
Check if it's running and stop it, change it to manual if you want to start server from IntelliJ without repeating this whole process everytime you log in Windows.

MobileFirst 7.1 Server Configuration Tool - Admin Console deployment failed with JVM error

I am trying to deploy the MobileFirst Admin Operational console using Server Configuration Tool. Started the configuration tool as root user. Create a configuration and saved the xml. Pressed the "Deploy" button. Its failed with JVM terminated Exit code -1 error.
MobileFirst Server Version 7.1.0.0-MFPF-Server-IF201510051721
WebSphere 8.5.5.7
Installation Manager JRE:jre_7.0.7001.20140909_1712
After this error, I am able to see the Admin console application and admin services application in WebSphere. But in Configuration Tool not able to create / add runtime under this configuration. It says no configuration found.
After this error, I am able to see the Admin console application and admin services application in WebSphere. But in Configuration Tool not able to create / add runtime under this configuration. It says no configuration found.
This is not a solution to the JVM crash you experiment, but a workaround to enable to be able to add the runtime (I understand from the above description that the crash happens after the Server Configuration Tool saved the configuration and deployed it).
Go to (homeDir)/.mobilefirst_platform_server/server-configuration-tool. You should find a directory named after your configuration. In that directory, you should find a file named (ConfigName).xml. Copy this file as (ConfigName).lastdeployed (ie same name as the xml file but change the suffix). The Server Configuration Tool would have created this file after deployment completion (and uses it for later operations such as uninstall) and it uses it as an indicator that the configuration is deployed.

restarting documetum server repository not show in drop down list in login page

I have just install the developer edition of documentum it was working successfully on window 7. but whenever I restart my system then login page don’t have any repository in drop down list. kindly help me
Startup sequence is very important for Documentum.
Correct startup Sequence is
Documentum DocBroker Service
Documentum Docbase Service "Repository Name"
Documentum Java Method Server
your application (for example Apache Tomcat with Webtop or Taskspace)
Usually on Windows it is Windows Services. When you just restart your server windows can start it in different order. To automate this procedure it is possible to configure Windows Service Dependencies.
Most of the times when this problem occurs, repository didn't start yet, and docbroker doesn't have information about it (repository didn't informed docbroker about its availlability).
If you look in the repository log (located under %DOCUMENTUM%\dba\log) you will see at the end of the startup process line like
Thu Jul 31 15:55:33 2014 301000 [DM_DOCBROKER_I_PROJECTING]info: "Sending information to
Docbroker located on host (TESTSERVER) with port (1489). Information: (Config(documentum),
Proximity(1), Status(Open))."
At this point docbroker knows about this repository and your client applications will have it in the list of available repositories.

Websphre portal does not startup

When I try to start up a websphere portal server, it hangs at the line :
Server WebSphere_Portal open for e-business
and although it means that the server started up successfully, it is not...because in the progress bar, i stll see 'Starting.....' I have tried deleting the wstemp and temp directories but beyond that I am not sure what I can do to debug the problem.
The server with the same profile starts up great from another workspace, but when I come to this workspace, it just hangs at
Server WebSphere_Portal open for e-business
I am using RAD 7 and portal 6.1
Kaushik,
Try and change the connection type between RAD and WebSphere Portal.Switch it between SOAP and RMI and see if that makes a difference.
Double click the server and in the property editor you can specify the connection method.
Check this link out
http://www-01.ibm.com/support/docview.wss?uid=swg21207553
HTH
Manglu