deploy the application on the Simulator console

Similar Questions

• Impossible to deploy my application on the Simulator more

  Since there are 4 days, I can't deploy and run my application on the Simulator more, I get this message all the time:

  Failure of deployment: Info: request shipment: install and launch
  Info: Action: install and launch
  News: Native debugging: on
  Info: File size: 482774
  Info: Installing eir.bb10.CorporateContacts.testDev_ateContacts1e5ecb89...
  Info: Treatment 482774 bytes

  What could be the problem? I later use NDK, reinstalled all, using 3 different simulators, including the most recent, but without success.

  I'd appreciate any help. It is very annoying, because I can't do any work and ship expected app updates, I face the environment of dev for 4 days! I have worked on many platforms and with many different tools, but I've never experienced anything like this.

  Thanks for the reply!

  I managed to get things running in a similar way. I uninstalled everything, including the NDK and start over. I returned to VMWare Player v.4. I work mainly with outdated Simulator, we run the fastest for me, although later runs now too.

  Yet EACH deployment on a Simulator takes several attempts, I don't remember when was the last time that the deployed application and runs correctly on the first attempt. I also change the download settings, switching between 'install bar' and 'clean install', these two works more often for me. Another thing to try in the meantime is to go for debugging directly, if the race does not...

  It is a terrible experience and it's very laborious, as I end up losing most of my time trying to run my application on the Simulator, instead of productive coding. Sorry BlackBerry, but it's worse that develop for Android, iOS, Windows Phone, Java ME... I develop for these systems and has never had any topic also with any of them.

  One of the reasons for the app started working again maybe do something with the code, because it contained errors, but the construction still successfully passed and they never showed me any error message in the IDE or in the Simulator. Anyway, I'll never know if my code had something to do with the cause of the problem, because the 'hack' held an older VM etc. But I write this so that people know that it can theoretically hinder deployment too.

• Error when deploying to the Simulator application: BUILD FAILED StandardInstall does not exist.

  I get the above error while deploying the blackberry Simulator application. I have
  Download the Java SDK 1.7, Apache Ant, BlackBerry WebWorks Smartphone SDK (OS 7 or earlier) and
  PhoneGap 2.8.1.I put in JDK and Ant path in environment variables.

  The project is to build successfully in the directory of the project with the command "ant blackberry construction."

  Generation of blackberry D:\ProjectBB>ant
  BuildFile: D:\ProjectBB\build.xml
  BlackBerry:
  Update:
  generate-cod-name:
  [echo] Generated name: __NAME__.cod
  clean:
  [Remove] Delete the D:\ProjectBB\build directory
  package-app:
  [mkdir] Created dir: D:\ProjectBB\build\widget
  [copy] Copy of 22 files to D:\ProjectBB\build\widget
  [zip] Building zip: D:\ProjectBB\build\__NAME__.zip
  Update:
  [exec] [INFO] Parsing of the command line options
  [exec] [ERROR] Invalid application - archive name of archive is not valid
  BUILD SUCCESSFULLY
  Total time: 4 seconds

  While deploying Simulator using 'ant blackberry simulator load' command in the command prompt, it
  shows build failed with the error message "StandardInstall does not exist.

  Responsible for blackberry D:\ProjectBB>Ant-Simulateur
  BuildFile: D:\ProjectBB\build.xml
  BlackBerry:
  Load Simulator:
  generate-cod-name:
  [echo] Generated name: __NAME__.cod
  clean:
  [Remove] Delete the D:\ProjectBB\build directory
  package-app:
  [mkdir] Created dir: D:\ProjectBB\build\widget
  [copy] Copy of 22 files to D:\ProjectBB\build\widget
  [zip] Building zip: D:\ProjectBB\build\__NAME__.zip
  Update:
  [exec] [INFO] Parsing of the command line options
  [exec] [ERROR] Invalid application - archive name of archive is not valid
  Load Simulator:
  [echo] Simulator directory = C:\Program Files\Research in Motion\BlackBerry WebWorks SDK
  2.3.1.5\simpack\7.0.0.318
  [echo] Simulator directory = C:\Program Files\Research in Motion\BlackBerry WebWorks SDK
  2.3.1.5\simpack\7.0.0.318
  [echo] Simulator of executable = C:\Program Files\Research in Motion\BlackBerryWebWorks SDK
  2.3.1.5\simpack\7.0.0.318/9930.bat
  [echo] All simulators of closing...
  [exec] No sessions running.
  [exec] Result: 1
  [echo] MDS directory = C:\Program Files\Research in Motion\BlackBerry WebWorks SDK 2.3.1.5/mds
  BUILD FAILED
  D:\ProjectBB\build.XML:51: The following error occurred when executing
  This line:
  D:\ProjectBB\blackberry.XML:153: D:\ProjectBB\build\StandardInstall does not exist.

  Total time: 7 seconds

  Please help me solve this problem

  Thanks in advance

  For the version of the SDK BlackBerry Smartphone (i.e. BBOS), please note that you need JDK1.6 and there are also 32 bits.

  Can you please try this change (uninstall previous versions of the JDK/JRE) and only install JDK1.6 32-bit (it will automatically install the JRE too.)

  As well, I see a problem in the community newspapers:

  [exec] [ERROR] Invalid application - archive name of archive is not valid

  There seems to be a problem with the name of the ZIP file:
  __Name__.zip

  Can you please try to remove the symbols _ the name of the archive?

• Problem to the Simulator application deployment

  Hi all

  I installed the Simulator and QNX. The Simulator starts fine and when I go to the window > Preferences > Blackberry and launch the deployment of Blackberry, my Simulator is found and added.  However, it did not create a build for the Simulator configuration (I have that by default) and so I can't deploy to test.

  I'm running Windows 7 pro with VMWare workstation 8

  Help, please!

  Thank you Smartek respondent

  It is, I tried another example of project and that was very good. When I looked back to the original sample (cascades recipe book) I built wrong.  This example seems to contain several different projects, and once I chose the right pair, my debug Simulator was there.

• Ripple error deployment to the simulator fails

  Hi, I'm taking my first steps in development of BB. My company asked me to do a BB - app with IBM work lamp. I installed the SDK Webworks, waving and a BB Simulator (model 9900). I also added the necessary environment variables on Windows 7. I did a hybrid application that contains the html, css and javascript. After the creation and deployment of the local console of the work light, I can open the app with ripple. After the start of the services, I can pack and start the work of packing App., but the deployment on the simulator fails. I get the following error:

  Spawning Simulator 9900 - 7.0.0.384...

  stderr: CreateProcessW: the system cannot find the specified file.

  Exit take flight for 9900 - 7.0.0.384

  I have seen this error on the forum, but others had when packing. I get it through to the Simulator. Can someone help me with this?

  I solved my problem by choosing another Simulator, 9860-model. Ripple now starts the Simulator, which is extremely slow. The hotswap function crashes immediately, but the Simulator works with my application. However I am concerned that blackberry development tools is so buggy. But as long as I don'tn use the simulator that's good enough.

• BB-Ant-tools and deployment to the Simulator

  Hello world:

  I have a library intern that I developed called Ichabod required by one of our applications, Spyder, which runs on the operating system Blackberry 4.5.0 (our original goal was to 8330 devices).  I had all this work with bb-ant-tools to compile the library, which is located in a separate project, and deploy it in C:\Program Files\eclipse\plugins\net.rim.ejde.componentpack4.5.0_4.5.0.21\components\simulator.  The Spyder application debugged very well in the eclipse plugin (I use Galileo with the 1.1.2 version of the plugin RIM).

  Today, however, I went to debug the Spyder application after making a few changes to the code (no code changes have been made in Toad) and found that the application could not find the module Ichabod suddenly.  I noticed that there is now a directory net.rim.ejde.componentpack4.5.0_4.5.0.28\ in my eclipse plugins folder, thinking that maybe I've updated component packs without realizing account, I adjusted the path target library of Ichabod and rebuilt with bb-ant-tools.  The same problem.  So, I tried to delete the .cod and all associated files the two directories 4.5.0.21 and 4.5.0.28, recompiled the Ichabod library to deploy in two places and found that it worked with 4.5.0.21, but not with 4.5.0.28 (it is not listed in the screen modules under settings, either).

  I checked the .cod file is present in the components\simulator folder, but I can't understand why the simulators do not recognize the file.

  Any suggestions?

  My build.xml ant-bb-tools script is attached.

  Thank you

  ~ Scott

  So it turns out, after removing the 4.5.0.28 Eclipse plugin and put it back, it was what was causing my problems.  I don't know if this has anything to do with it, but I also removed the JDE 4.5.0 library (which has been correctly updated version 28) from the path of construction of the project Ichabod and replaced by the JDE even.

  After all of this nonsense, my library now appears in the Simulator.

• Can deploy app in the Simulator, but not to the device

  Sorry about this newbie question, but how is it that a simple HelloWorld application compiled in Eclipse runs just fine on the Simulator, but cannot be installed on a 8320 Curve by the Blackberry Desktop Software?

  I use the latest version at all.  The message returned by the desktop software is:

  ! There was an error importing files.
  No additional applications can be found. Your file can
  contain applications that already exist in the list of applications,
  are not compatible for your device, or errors.

  However, I am able to deploy the application on the handset using the command line tool:

  C:\Eclipse\plugins\net.rim.ejde\vmTools\JavaLoader.exe -usb load \workspace\HelloTest\deliverables\Standard\5.0.0\HelloTest.jad
  

  This installs the application, which then runs correctly on the device.  I can then reload the list of app on the Blackberry Desktop Software tool and it shows HelloTest, but under the properties of the Application-> dependencies it says:

  "Application not available (net_rim_cldc).

  It seems that some dependence crept in the generation of the application and that confuses the desktop tool.  The curve is running 4.5 OS.

  Should I just throw this office tool, or how can I clean the application so that it installs correctly?  Obviously, this is just foreplay before building a much broader application, and I wish I had these little glitches will hamper ASASP.

  Thanks for any help!

  You should be able to download a plugin 4.5 on the site to update. Go to "help > install new software" to open the screen of software available. If you have not yet done so, add the updated BlackBerry site to your Eclipse configuration:

  1. Click on "available software Sites.
  2. Click on the button 'Add '.
  3. Enter a name such as 'BlackBerry update location' and set the location http://www.blackberry.com/go/eclipseUpdate/3.5/java
  4. Click OK, then OK again to return to the screen of the software available

  The 'working with' menu drop-down, select the location of BlackBerry Update (or whatever you named it). Expand the BlackBerry Java plug-in category and you should be able to select an appropriate plug-in version.

• Cannot deploy the bar file BB10 Simulator.

  As the title,

  I have try all the possible method to deploy my bar of file Simulator BB10 running on VMware player without a bit of luck.

  The IP address that I use is the one indicated in the developer section of the simulated device:
  169.254.0.1

  no luck, I can't even ping the device to the windows console.

  Any idea?

  If you are connected to a VPN, it can cause connection problems to the Simulator.

  Could you try reboot the Simulator in bridged mode?  You can change this under the network option in the settings of your virtual machine.  If you do not have to go through NAT, which could cause you problems, this will put the Simulator on your physical network card.

  Also are you able to telnet/ftp to the Simulator?  You can identify yourself as devuser/devuser.

• Flash Builder does not appear to be deployed to the Simulator:

  Hey guys!

  So here's the deal. I am running Win7 with the IDE Flash Builder Burrito. I followed the guide on the BB step by step to create my first Hello World project. When I try to debug, FB seems to show that it has installed the successful application on the Simulator, but still waiting to connect to the application until it finally expires with the message "the Flash BUilder debugger cannot connect to the running application".

  Host machine, I ping IP of the Simulator, and the mode of development.

  I inserted the target IP address in the Debug menu (it's 192.168.88.128) and the debug host is the IP address of the host too (10.0.3.136). I entered the correct device as password.

  Scratching my head here now, what Miss me?

  Alright! It is very very annoying. I discovered that I was in fact trying to deploy on the previous version of the Simulator... Sorry to lose all time on it. Consider this a rookie mistake

• Is it possible to deploy the application without WiFi?

  I have a fair amount of coding "on the go" (in the train, airport, airplane, etc.) where do not always have access to a wifi hotspot. Is there a way to deploy my application on the actual device (not the Simulator) without wifi? For example connect you via USB / DM and deployed this way? I was not able to find all the information, but also any posts in question with definitive answers?

  When you connect your PB to your PC via the USB port, the Playbook installs a network driver on the PC with an address like this:

  169.254.xxx.xxx

  the driver on the PC points to the network address:

  169.254.xxx. (xxx + 1)

  and chooses the IP USB PB as the gateway address, so they can talk.

  You should be able to deploy to your PB via USB.  I use FB 4.5 to deploy, and it works with USB and WIFI.  A problem is your IP address changes when you unplug the USB key, then you will need to reconfigure.

• Application of background visible on a real device (all well in the Simulator)

  Hello

  I developed a small backgroundapplication, which shows a menu entry in the app phone "call via Asterisk. If I choose this option a defined number is called. Later, I want to add the number as dtmf tones.

  The application uses excactly as expected in the device Simulator 8310-JDE (included in the eclipse plugin) on JDE 4.5. with eclipse.

  But when I deploy the application (signed) to a real 8310 with firmeware v4.5.0.81, it appears an application icon on the desktop (homescreen) of blackberry and the menuentry in the phone app is missing. Why the application is not deployed as a background on the real dev app. ?

  The only difference between the Simulator and real device is the language chosen, but I don't think it's important.

  The application consists of files, as shown below.

  import net.rim.blackberry.api.menuitem.ApplicationMenuItemRepository;import net.rim.device.api.system.Application;
  
  public class Asterisk extends Application {   public static void main(String[] args)    {            // Create a new instance of the application            // and start it's event thread.            new Asterisk().enterEventDispatcher();    }
  
      public Asterisk()    {        //create a new instance of the menuitem       AsteriskMenuItem asterisMenuItem = new AsteriskMenuItem(40);
  
        //get the instance of the standard-menu an ad the new menuitem        ApplicationMenuItemRepository     .getInstance().addMenuItem        (ApplicationMenuItemRepository.MENUITEM_PHONE,asterisMenuItem);
  
      }}
  

  package com.schiffl.mobile.asteris;
  
  import net.rim.blackberry.api.invoke.Invoke;import net.rim.blackberry.api.invoke.PhoneArguments;import net.rim.blackberry.api.mail.Message;import net.rim.blackberry.api.menuitem.ApplicationMenuItem;import net.rim.blackberry.api.phone.Phone;import net.rim.blackberry.api.phone.PhoneCall;import net.rim.blackberry.api.phone.PhoneListener;import net.rim.device.api.system.ControlledAccessException;import net.rim.device.api.ui.Field;import net.rim.device.api.ui.UiApplication;
  
  public class AsteriskMenuItem  extends ApplicationMenuItem{     //number to be dialed via Asterisk        String servicenumber  = "1234567";
  
        //using the default constructors here.        AsteriskMenuItem(int order)       {         super(order);     }
  
         //methods we must implement       //Run is called when the menuItem is invoked      public Object run(Object context)     {             /*             * Normally the dialed number could be found in the context object             * because of a bug in the api which is solved in v.4.7 the context            * object is always null for MENUITEM_PHONE so it is necessary to          * use a workaround, here the number is extracted from the field with focus,           * which contains the dialed number           */            Field myField = UiApplication.getUiApplication().getActiveScreen().getFieldWithFocus();           String phoneNumber = myField.toString();
  
            //TODO Convert phoneNumber to dtmf-tones
  
            try           {             PhoneArguments call = new PhoneArguments(PhoneArguments.ARG_CALL,servicenumber);              Invoke.invokeApplication(Invoke.APP_TYPE_PHONE, call);
  
  //                PhoneCall myCall = Phone.getActiveCall();//               myCall.sendDTMFTones(phoneNumber);            }         /*             * The ControlledAccessException is thrown             * if the system administrator restricts access to the phone application           * using application control.          */           catch (ControlledAccessException e)           {             //TODO some exceptionhandling             }
  
           //normally you can do something with the given context inside of the run-method           //because of a bug in the API the context is always null so, we don't use it...           return context;       }
  
         //toString should return the string we want to        //use as the lable of the menuItem        public String toString(){         return "Call via Asterisk";       }
  
  }
  

  The entry for the RRT signature was missing in my .csl file. I change it manually, I added

  '52525400 = RIM API execution' requested signatures, deployed and it works...

• Error trying to deploy the application on the content of webcenter

  Hi, Im trying to deploy an application to webcenter content server, but I get the following error.

  Can someone help me?

  Weblogic Server Exception: weblogic.application. ModuleException: [HTTP:101216] Servlet: 'wcmInitServlet' failed by preloading at startup in a Web application: 'myapp'.

  Oracle.Stellent.WCM.common. LocalizedRuntimeException: oracle.stellent.wcm.client. ApplicationException: application initialization error

  to oracle.stellent.wcm.javaee. ServletApplicationFactory. createInstance (ServletApplicationFactory. ) java: 72)

  to oracle.stellent.wcm.javaee. ServletHelper. initializeApplication (ServletHelper.java:192)

  to oracle.stellent.wcm.javaee. servlet.filter. WCMInitializeServlet.init (WCMInitializeServlet.java:43)

  to javax.servlet.GenericServlet. Init(GenericServlet.Java:241)

  to weblogic.servlet.internal. StubSecurityHelper$ ServletInitAction.run (StubSecurityHelper.java:283)

  to weblogic.security.acl. internal. AuthenticatedSubject. doAs(AuthenticatedSubject. ) java: 321)

  to weblogic.security.service. SecurityManager.runAs (SecurityManager.java:120)

  to weblogic.servlet.internal. StubSecurityHelper. createServlet (StubSecurityHelper.java:64)

  to weblogic.servlet.internal. StubLifecycleHelper. createOneInstance (StubLifecycleHelper.java:58)

  to weblogic.servlet.internal. StubLifecycleHelper. < init > (StubLifecycleHelper.java:48)

  to weblogic.servlet.internal. ServletStubImpl. prepareServlet (ServletStubImpl.java:539)

  to weblogic.servlet.internal. WebAppServletContext. preloadServlet (WebAppServletContext.java:1981)

  to weblogic.servlet.internal. WebAppServletContext. loadServletsOnStartup (WebAppServletContext.java:1955)

  to weblogic.servlet.internal. WebAppServletContext. preloadResources (WebAppServletContext.java:1874)

  to weblogic.servlet.internal. WebAppServletContext.start (WebAppServletContext.java:3154)

  to weblogic.servlet.internal. WebAppModule.startContexts (WebAppModule.java:1518)

  to weblogic.servlet.internal. WebAppModule.start (WebAppModule.java:484)

  to weblogic.application.internal. the stream of . ModuleStateDriver$ 3.next (ModuleStateDriver.java:425)

  to weblogic.application.utils. StateMachineDriver.nextState (StateMachineDriver.java:52)

  to weblogic.application.internal. the stream of . ModuleStateDriver.start (ModuleStateDriver.java:119)

  to weblogic.application.internal. the stream of . ScopedModuleDriver.start (ScopedModuleDriver.java:200)

  to weblogic.application.internal. the stream of . ModuleListenerInvoker. start(ModuleListenerInvoker. ) java: 247)

  to weblogic.application.internal. the stream of . ModuleStateDriver$ 3.next (ModuleStateDriver.java:425)

  to weblogic.application.utils. StateMachineDriver.nextState (StateMachineDriver.java:52)

  to weblogic.application.internal. the stream of . ModuleStateDriver.start (ModuleStateDriver.java:119)

  to weblogic.application.internal. the stream of . StartModulesFlow. activate(StartModulesFlow. ) java: 27)

  to weblogic.application.internal. BaseDeployment$ 2. next (BaseDeployment.java:671)

  to weblogic.application.utils. StateMachineDriver.nextState (StateMachineDriver.java:52)

  to weblogic.application.internal. BaseDeployment.activate (BaseDeployment.java:212)

  to weblogic.application.internal. EarDeployment.activate (EarDeployment.java:59)

  to weblogic.application.internal. DeploymentStateChecker. Activate (DeploymentStateChecker.java:161)

  to weblogic.deploy.internal. targetserver. AppContainerInvoker.activate (AppContainerInvoker.java:79)

  to weblogic.deploy.internal. TargetServer.operations. AbstractOperation.activate (AbstractOperation.java:569)

  to weblogic.deploy.internal. TargetServer.operations. ActivateOperation. activateDeployment (ActivateOperation.java:150)

  to weblogic.deploy.internal. TargetServer.operations. ActivateOperation.doCommit (ActivateOperation.java:116)

  to weblogic.deploy.internal. TargetServer.operations. AbstractOperation.commit (AbstractOperation.java:323)

  to weblogic.deploy.internal. targetserver. DeploymentManager. handleDeploymentCommit (DeploymentManager.java:844)

  to weblogic.deploy.internal. targetserver. DeploymentManager. activateDeploymentList (DeploymentManager.java:1253)

  to weblogic.deploy.internal. targetserver. DeploymentManager. handleCommit (DeploymentManager.java:440)

  to weblogic.deploy.internal. targetserver. DeploymentServiceDispatcher. validation (DeploymentServiceDispatcher. ) java: 163)

  to weblogic.deploy.service. internal.TargetServer. DeploymentReceiverCallbackDeli verer.doCommitCallback (DeploymentReceiverCallbackDeliverer.java:195)

  to weblogic.deploy.service. internal.TargetServer. DeploymentReceiverCallbackDeli verer.access$ 100 (DeploymentReceiverCallbackDeliverer.java:13)

  to weblogic.deploy.service. internal.TargetServer. DeploymentReceiverCallbackDeli humour$ 2.run (DeploymentReceiverCallbackDeliverer.java:68)

  to weblogic.work. SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl. ) java: 545)

  to weblogic.work.ExecuteThread. run (ExecuteThread.java:256)

  to weblogic.work.ExecuteThread. Run(ExecuteThread.Java:221)

  Caused by: oracle.stellent.wcm.client. ApplicationException: application initialization error

  to oracle.stellent.wcm.client. ClientApplication.initialize (ClientApplication.java:316)

  to oracle.stellent.wcm.javaee. . ServletClientApplication < init > (ServletClientApplication.java:54)

  to oracle.stellent.wcm.javaee. ServletApplicationFactory. createInstance (ServletApplicationFactory. ) java: 61)

  ... more than 45

  Caused by: oracle.stellent.ridc. IdcClientException: Content Server not found "SSXARunTime" function

  to oracle.stellent.wcm.core.idc. IdcClientFactory. validateConfiguration (IdcClientFactory.java:166)

  to oracle.stellent.wcm.client. ClientApplication.initialize (ClientApplication.java:267)

  ... more than 47

  Caused by: oracle.stellent.ridc.protocol. ProtocolException: failed to initialize the idc connection: / / myserverip:4444

  to oracle.stellent.ridc.protocol. intradoc.Socket. SocketConnectionManager. initializeConnection (SocketConnectionManager.java:35)

  to oracle.stellent.ridc.protocol. intradoc.Socket. SocketConnectionManager. initializeConnection (SocketConnectionManager.java:22)

  to oracle.stellent.ridc.protocol. impl. SimpleConnectionPool. acquireConnection (SimpleConnectionPool.java:44)

  to oracle.stellent.ridc. IdcClient.sendRequest (IdcClient.java:151)

  to oracle.stellent.wcm.core.idc. AbstractIdcApi.executeService (AbstractIdcApi.java:163)

  to oracle.stellent.wcm.core.idc. impl. AdminApi.runTimeConnect (AdminApi.java:48)

  to oracle.stellent.wcm.core.idc. IdcClientFactory. validateConfiguration (IdcClientFactory.java:148)

  ... more than 48

  Caused by: oracle.stellent.ridc.protocol. ProtocolException: java.net.ConnectException: Connection timed out: connect

  to oracle.stellent.ridc.protocol. intradoc.Socket. SocketConnection.connect (SocketConnection.java:52)

  to oracle.stellent.ridc.protocol. intradoc.Socket. SocketConnectionManager. initializeConnection (SocketConnectionManager.java:33)

  ... more than 54

  Caused by: java.net.ConnectException: Connection timed out: connect

  to java.net. DualStackPlainSocketImpl. connect0(Native Method)

  to java.net. DualStackPlainSocketImpl. socketConnect (DualStackPlainSocketImpl.java:79)

  to java.net. AbstractPlainSocketImpl. doConnect (AbstractPlainSocketImpl.java:339)

  to java.net. AbstractPlainSocketImpl. connectToAddress (AbstractPlainSocketImpl.java:200)

  to java.net. AbstractPlainSocketImpl. Connect (AbstractPlainSocketImpl.java:182)

  impossible. Connect (PlainSocketImpl.java:172)

  to java.net.SocksSocketImpl. Connect (SocksSocketImpl.java:392)

  to java.net.Socket.connect (Socket.java:579)

  to java.net.Socket.connect (Socket.java:528)

  at java.net.Socket. < init >(Socket. ) java: 425)

  at java.net.Socket. < init >(Socket. ) java: 208)

  to oracle.stellent.ridc.protocol. intradoc.Socket. SocketConnection.createSocket (SocketConnection.java:126)

  to oracle.stellent.ridc.protocol. intradoc.Socket. SocketConnection.connect (SocketConnection.java:44)

  ... 55 more

  [09:35:12] caused by: java.lang.Throwable: substituted except oracle.stellent.wcm.client. ApplicationException, who is not a builder of the original - message application initialization error string

  [09:35:12] check the server logs or the console of the server for more details.

  Solved. You must clear the .ear, restart UCM, and then deploy the application again.

• Unable to deploy the EPM Application

  Hello

  I use EMP 11.1.2.3 application and Essbase created in the new library of the Application. But I'm not able to deploy this application to Essbase server.

  Please find the journal of validation below folder. The result indicates success. But when I checked the status in the console work, it is abandoned. Please could you help me to deploy the application.

  Summary of postings
  ==================

  Result: success
  Summary: There was 0 errors and 3 warnings during the validation process. For more details refer to the section setting warning of this journal and a mistake.

  Console work:

  

  Thank you

  Michel K

  Did you do a right click on the application in the application library and run the diagnostics, have you checked the epma and essbase, newspapers is essbase studio works ok as epma use studio to deploy.

  See you soon

  John

• Problem installation AutoVue - deployment of application in the field has failed;

  Full of the error:

  Deployment of application in the field has failed; Deployment error - Exception has occurred in the javax.xml.ws.WebServiceException of wsgen process: cannot create JAXBContext deployment error - Exception has occurred in the javax.xml.ws.WebServiceException of wsgen process: cannot create JAXBContext.

  Sun GlassFish Enterprise Server v2.1.1

  This error occurs when == > http://localhost:4848 / | Console mgt GlassFish 2.1.1 | Web applications | Deploy | Web application, AutoVueWS.war

  
  

  Background:

  I am an Adobe Flex coder threw in a Silverlight project, trying to get a JavaBean to work.

  My task is to get a DGN file to display in my Silverlight application. I tried to fix this using AutoVue as a web service returns an image and displaying this image on my control. This, of course works fine on the last machine of developers. However, I've been totally failed to install on the client server. I have no real idea of what I'm doing with the GlassFish/Java/AutoVue for this project section. Any help would be greatly appreciated

  
  

  -I have have Glassfish installed v2.1.1 and seems to work correctly.

  -I used it C:\Program Files (x86)\Java\jdk1.7.0_21\bin\jar.exe' cvf - AutoVueWS.war - C AutoVueWS.

  to compile the war file.

  -Server = Pro, 2 GB, Windows 7 64-bit * Virtual Machine
  

  Post edited by: 6bf38c5b-5aea-4186-9e77-bf1326cfd283

  New "6bf38c5b-5aea-4186-9e77-bf1326cfd283," Hi

  If all you need to AutoVue for is the conversion of an input format (for example, DGN) in a PNG image format, so yes, it's a case of using the AutoVue Web Services API (more precisely "convert it" Web Service). In this case, you should proceed with the question of GlassFish forums so they can help solve the deployment problem.

  However, depending on how you obtained your Silverlight solution implemented, it might be even more efficient/transparent to avoid the conversion completely process and simply stir the applet AutoVue in the interface of your solution. In this case, users would see their files (in whatever format or DGN) directly within the AutoVue applet, and you can customize the user interface of applet according to the needs (in terms of menus/toolbars tools/etc). If this is of interest to you, check out the Guide of AutoVue API at http://docs.oracle.com/cd/E37436_01/otn/pdf/E37455_01.pdf

  And to answer your last question - no, there is no way to communicate directly with the server of AutoVue. The AutoVue API and the API of Services Web AutoVue are the two APIs on the client side.

  Thank you

  Graham

• Deploying the application to the stand-alone WebLogic problem

  Hello!
  I have a problem with the stand-alone WebLogic Server applications.
  We migrated to JDeveloper 11.1.1.5 to 11.1.2.1. I followed the instructions on this page: https://blogs.oracle.com/imc/entry/standalone_weblogic_domain_for_adf to deploy our application of ADF on AdminServer. Everything worked OK.
  
  Then I followed the instructions on this page: http://docs.oracle.com/cd/E21043_01/web.1111/e13813/custom_jrf.htm to apply with our "ADF_server" the server JRF managed and got this:
  WLS: / offline > applyJRF ('ADF_server', ' / Oracle/Middleware/user_projects/domains/our_domain ')
  Read the/Oracle/Middleware/user_projects/domains/our_domain area of applyJRF
  Copy the configuration files JRF/Oracle/Middleware/oracle_common/modules/Oracle/Middleware/user_projects/domains/our_domain/config/fmwconfig/servers/ADF_server
  Components JRF target to "ADF_server".
  Update changes JRF to/Oracle/Middleware/user_projects/domains/our_domain field in offline mode
  It's probably OK?
  
  When I try to deploy a problem occurs on a managed server 'ADF_server':
  * [10: 55:08] Weblogic Server Exception: weblogic.application.ModuleException: could not load the webapp: "ADFMainApplication-ViewController-context-root."
  * [10: 55:08] caused by: weblogic.management.DeploymentException: error: unresolved Webapp library makes reference to ' [ServletContext@1542360219[app:ADFMainApplication_Project1_ADFMainApplication module: root ADFMainApplication-ViewController-context-path: / ADFMainApplication-ViewController-context-root spec-version: 2.5] ", defined in weblogic.xml [Extension name: jsf Specification-Version: 2, exact match: false] *.
  * [10: 55:08] see the server logs or the console of the server for more details.*
  * [10: 55:08] weblogic.application.ModuleException: failed to load the webapp: "ADFMainApplication-ViewController-context-root."
  * [10: 55:08] deployment cancelled.*
  * [10: 55:08] - incomplete deployment. *
  * [10: 55:08] remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer). *
  
  What should I do to run the managed server? Help, please.
  Best regards, Marko

  You did to be sure that the 11.1.1.5.0 adf runtime has been installed on the managed server before installing Upgrade patches to 11.1.2.1.0?

  If this isn't the case, it is the problem. The new runtime environment is installed automatically if the olny one has been set up correctly, my personal conclusion from my tests. If you want to learn more about this check http://tompeez.wordpress.com/2011/06/25/upgrading-wls-10-3-5-with-adf-runtime-11-1-2-0-0-sherman-patch/ and http://tompeez.wordpress.com/2011/06/29/follow-up-upgrading-wls-10-3-5-with-adf-runtime-11-1-2-0-0-sherman-patch/.

  You can make the threethings:
  1. Open Enterprise Manager, select your managed server and hope you see a message like "JRF aply to this managed server" (don't remember the exact wording). To do this, and libraries must configure OK.
  2. open the administration console and select the necessary shared libraries and add your manages the target server. Problem is that you don't know what libs are needed. If you don't mind target libraries to the managed server. Not sure if this causes problems later.
  3 write information on the managed server as port, domain names machine name. Remove the server managed the installation of WLS. It must be very sad that you upgrade and which should be no application or shared library of your one deployed on the managed server. After removal of the old successful server closes wls and start it again (just for security). Now, create a new managed server with all names, ports, and other information like the old using the quick start tool.

  I prefer the 3 method, this one worked for me all the time.

  Timo