ALSB Proxy services deployment management

Hi all

I have a problem now.
We have to many services running in a domain ALSB proxies.
Some of them need to transfer hundreds of XML MB data very frequently. They are listening to a JMS queue. And when they work, they will cause the entire system too heavy-loads of work.

So, we want to add a new server in this area ALSB to run proxy services data transfer.
Because the data transfer proxy services have too many dependencies to separate, our thought is to deploy all of the projects on the new server and manage proxies operating only with the new server data transfer.

Is this possible? Can I clarify some proxy services JMS running only on server1 and other services proxy running on server2 Server (server1 and server2 are in the same domain) in ALSB?

Thanks in advance.

Garriot Zhang

Is this possible? Can I clarify some proxy services JMS running only on server1 and other services proxy running on server2 Server (server1 and server2 are in the same domain) in ALSB?

N ° when a proxy is deployed, it gets deployed on all servers. OSB does not explicitly control which server proxy must be deployed.

Maury

Tags: Fusion Middleware

Similar Questions

  • ALSB Proxy service

    Hi all

    We are not able to launch a service proxy ALSB of BPEL? Please help me on this issue.

    Thank you and best regards,
    Idrissa.

    How to get the URL of the WSDL Proxy OSB was my question?

    Not all proxy servers have WSDL that are associated with them. for example Proxy type AnyXML or AnySOAP or MessageType will not just what WSDL.
    Proxies that are of type WSDL services will be the effective WSDL accessible via http://machine:port / your URI. Not all proxy servers have WSDL.

    Suppose that you have set the WSDL proxy by name test "myproxy" in the structure of folders like "wsdlbasedtest/sometest".
    http://machine:port / wsdlbasedtest/sometest/myproxy? WSDL

    Feel free to respond if the explanation is not clear above.

    Thank you
    Maury

  • Deploying files proxy services in clustered environment

    Hello

    To deploy a file proxy service in a clustered environment, it is necessary to deal specifically in the implementation of the proxy service to ensure that the files can be processed by the managed servers.

    If I understand correctly, you can create a distributed queue which is linking to wlsb.internal.transport.task.queue.file and local queues on managed servers can be added as members of the distributed queue.

    Currently, the file is getting treated via the server managed, which is the target server poller for the proxy file service. The file is not be treated if the file passes through the other managed server and remains in the repertoire of the scene.

    Any help will be appreciated. Please let me know if you count more details.

    Thank you

    At SKB: Hard to believe none of the Maury of post was helpful or appropriate. Please, mark to help other readers in the future.

  • OSB - Manager of errors in binding to the proxy service

    Hello!

    I had a proxy service that queries a POP3 server to download emails and process them.
    My question: How can I bind an error handler to the proxy service to notice when the POP3 server is not available?
    So, I would put an alert when the OSB loses the connection to the mail server. I tried to put an error handler to the top component of the mail flow page, but it does not work...
    Could someone help me?
    Thank you!

    Viktor

    For the transport of poller (e-mail/FTP/File, etc.), it is not possible to intercept the transport layer errors, in your service error handler. Re: OSB - Manager of errors in FTP to TransportException transport

    Thank you
    Maury

    Published by: Manoj Neelapu on June 28, 2010 15:51

  • OSB: Job manager associate a proxy service

    Hello

    Can someone tell me please how to associate workmanager (already present in the weblogic administration console) with a proxy service?

    Thank you.
    Kalpana.

    You will find in the proxy service configurations "Political Intervention" here you can associate managers work with the proxy service

  • Upload file in the Proxy Service ALSB

    Hello

    I need to download a file from one system to another system by the Proxy Service.

    With the Proxy Service, you can download a file by using the FTP protocol. But, how a upload a file?

    Thank you and best regards,
    Charrier

    Hello..

    You can use a business type Messaging service.

  • OSB cluster-HTTP 404 error proxy service

    Hi all
    I have a set cluster in place with 2 managed servers. I packed a proxy of sbconsole to test if I can reach the managed server form an external service. I have not yet defined front load balancer.
    OSB server1: rdoelapp001011:61703
    OSB:Server2:rdoelapp001013:61703
    Server Administrator: rdoelapp001011:61701

    When I try to access the http proxy using one osb server host and port I get a 404 error (from the administration console that I could see that all servers are running)
    surprisingly, I was successful (200) when I use admin server host and port.
    That means that the proxy is not get deployed to the managed server, it is deployed to the server administrator
    I looked into a few document weblogic/OSB, I couldn't see anything specific about the proxy HTTP deployment to the osb servers in a cluster

    How could make sure deploy on the cluster to the server administrator
    I also tried creating a file poller proxy to see if I get "Managed server" option to be set. But I don't see that option here.

    Any help will be greatly appreciated.

    Published by: 818591 on February 21, 2011 20:52

    No, I didn't create cluster wizard config. I had a domain created with just the server admin and no server managed. I was doing development using server admin. Then I had to extend it to test the configuration of the cluster

    It is the root cause of the problem. When you created the field, you created a single server domain and so everything is deployed on the management server. Later even if you have created the cluster and the managed server, but still applications are targeted to Server Admin, because it will not automatically get targeted to the cluster. Best solution would be to create a new field that has cluster (while creating the domain itself, create the cluster) and export the configuration of current domain of OSB and import it into the domain of the cluster.

    Kind regards
    Anuj

  • Message access control in the OSB proxy service when the Service Type is the Any SOAP Service

    Hello

    We have a proxy OSB service where the Service Type is 'no matter what SOAP Service'. We use Auth.xml to authenticate messages to achieve this proxy service.

    It is, ca we apply Message this proxy access control so that only user A is allowed to sent message has and only user B is allowed to message sent B?

    Us know if the proxy OSB service is based on a wsdl, then we can apply access control message for each operation in the Security tab - and thus specify which user can access the operation. But unfortunately, we have not a wsdl, because this service proxy is a proxy gateway and must accept any SOAP message reaches.

    For example, if the user name in the SOAP header is msgAUser, get is accepted.

    "< soapenv:Envelope xmlns:soapenv ="http://schemas.xmlsoap.org/soap/envelope/">"

    < soapenv:Header >

    "< xmlns:wsse wsse: Security ="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">."

    < wsse: UsernameToken >

    < wsse:Username >msgAUser< / wsse:Username >

    < wsse:Password >msgApwd< / wsse:Password >

    < / wsse: UsernameToken >

    < / wsse: Security >

    < / soapenv:Header >

    < soapenv:Body >

    <Get>

    ...

    < /Get>

    < / soapenv:Body >

    < / soapenv:Envelope >

    If the user name in the SOAP header is msgBUser, then MessageB is accepted.

    "< soapenv:Envelope xmlns:soapenv ="http://schemas.xmlsoap.org/soap/envelope/">"

    < soapenv:Header >

    "< xmlns:wsse wsse: Security ="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">."

    < wsse: UsernameToken >

    < wsse:Username >msgBUser< / wsse:Username >

    < wsse:Password >msgBpwd< / wsse:Password >

    < / wsse: UsernameToken >

    < / wsse: Security >

    < / soapenv:Header >

    < soapenv:Body >

    <MessageB>

    ...

    < /MessageB>

    < / soapenv:Body >

    < / soapenv:Envelope >

    Any suggestions please?

    Understood.

    My current client, we have faced the same problem and implemented a similar design which nevertheless has important benefits.

    The problem with proxy input all SOAP is not only in the complexities of authentication. Most important, resources fine grain (thread) management becomes impossible: proxy entry has a workmanager, one constraint of son max. If any single service behind entered proxy knows an influx of requests (because of a peak or a misconfigured customer), he eats the workmanager dry and the rest of the services become too inadmissible.

    In this spirit, we have implemented the following diagram. It's a little more complicated, but it serves us well for a few years already:

    EntryProxy 1-> Interceptor entering Proxy-> Proxy 1

    EntryProxy 2-> Interceptor entering Proxy-> Proxy 2

    ...

    Enter proxy doesn't do Nothing but shall forward the request for interception of incoming traffic. Power of Attorney of the entry, however, has its own WSDL, authentication and the workmanager which allows precise control.

    Another important aspect of a proxy of the entry, it is that it passes a custom header containing the name of the destination of the interceptor, e.g. TargetURI = "ProxyService/Paypal/Paypal.

    Incoming Interceptor Proxy performs all recording, the error handling and other common tasks.

    Then, according to the last header, the proxy of the interceptor makes a dynamic call to route to the specified destination.

    Yes, this design has an additional moving part - a proxy entry - but he a) works b) guard control all in our hands. The entry proxy is a very small point; When I need to make a new one, I just copy an existing one and replace the WSDL file and the value of the TargetURI - 30 seconds of work.

    Hope that helps.

    Vlad

    http://vladimirdyuzhev.com

  • Standard deployment failed installation foundation services deployed on the application server

    Good day ~

    Let me preface this with I have very limited exposure to Oracle products - thank you for your patience.

    I was busy learning, to install and prepare the Oracle EMP 11.1.2.3 components.

    Environment:

    New installation - I use Oracle Enterprise Performance Management System Standard Deployment Guide and the Guide of Installation and Configuration.

    Windows 2008 R2 - single server for all instances.

    SQL 2008 R2 - on a separate server.

    I started with the deployment guide Standard following all the steps for "installation of the Services of the Foundation" and at the end of the installation, it shows 'Impossible' for these red x products/task and status said Configuration is complete.

    The newspaper that I pointed at by using 'Help' EPM_ORACLE_INSTANCE/diagnostics/logs/config/configtool_summary.log says:

    (10 December 2013 12.48.49 PM): move the Foundation Hyperion [000 min 37sec] [PRE] - pre-configuration

    (10 December 2013 12.48.49 PM): pass [000 min 00 sec] [COM] Hyperion Foundation - the common settings

    (10 December 2013 12.49.48 PM): pass [000 min 58 sec] [COM] Hyperion Foundation - configure Oracle Configuration Manager

    (10 December 2013 12.49.52 PM): move the Foundation Hyperion [000 min 03sec] [DB] - database configuration

    (10 December 2013 12.50.01 PM): pass [000 min 04 sec] [PRE] Provider Services - pre-configuration

    (10 December 2013 12.55.40 PM): pass [005 min 38 sec] [PRE] Performance Management architect - pre-configuration

    (10 December 2013 12.55.41 PM): pass [000 min 00 sec] [REG] Performance Management architect - register with Shared Services

    (10 December 2013 12.55.44 PM): pass [000 min 03sec] [DB] Performance Management architect - database configuration

    (10 December 2013 12.56.15 PM): pass [000 min 30 sec] [VCC] Performance Management architect - configure the server of Dimension

    (10 December 2013 12.56.32 PM): pass [000 min 17 sec] [PRE] Essbase Studio - pre-configuration

    (10 December 2013 12.56.33 PM): pass [000 min 00 sec] [REG] Essbase Studio - register with Shared Services

    (10 December 2013 12.56.38 PM): pass [000 min 04 sec] [DB] Essbase Studio - database configuration

    (10 December 2013 12.56.38 PM): pass [000 min 00 sec] [PRE] calculation Manager - pre-configuration

    (10 December 2013 12.56.38 PM): pass [000 min 00 sec] [REG] calculation Manager - register with Shared Services

    (10 December 2013 12.56.39 PM): pass [000 min 00 sec] [DB] calculation Manager - database Configuration

    (10 December 2013 12.57.39 PM): pass [000 min 59 sec] [PRE] Reporting and analysis - pre-configuration

    (10 December 2013 12.57.40 PM): pass [000 min 00 sec] [REG] Reporting and analysis - register with Shared Services

    (10 December 2013 12.57.47 PM): pass [000 min 07 sec] [DB] Reporting and analysis - database configuration

    (10 December 2013 12.58.14 PM): pass [000 min 27 sec] [FSC] Reporting and analysis - configure the Services Framework

    (10 December 2013 12.58.15 PM): pass [000 min 00 sec] [RMI] Reporting and analysis - configure the Ports of RMI financial statement

    (10 December 2013 12.58.56 PM): failure [000 min 40 sec] [APP] Hyperion Foundation - deploy to the application server

    (10 December 2013 12.58.56 PM): failure [000 min 00 sec] [APP] Provider Services - deploy to the application server

    (10 December 2013 12.58.56 PM): failure [000 min 00 sec] [APP] performance management architect - deploy to the application server

    (10 December 2013 12.58.56 PM): failure [000 min 00 sec] [APP] performance management architect - deploy to the application server

    (10 December 2013 12.58.56 PM): failure [000 min 00 sec] [APP] calculation Manager - deploy to the application server

    (10 December 2013 12.58.56 PM): failure [000 min 00 sec] [APP] Reporting and analysis - deploy to the application server

    (10 December 2013 12.58.56 PM): failure [000 min 00 sec] [APP] Reporting and analysis - deploy to the application server

    (10 December 2013 12.58.56 PM): failure [000 min 00 sec] [APP] Workspace - deploy to the application server

    (10 December 2013 12.59.18 PM): pass [000 min 21 sec] [PRE] financial management - pre-configuration

    (10 December 2013 12.59.28 PM): move financial management [000 min 10 sec] [HDC] - DCOM configuration

    (10 December 2013 01.00.56 PM): move the Foundation Hyperion [001 min 27 sec] [WEB] - configure the Web server

    (10 December 2013 01.00.56 PM): pass [000 min 00 sec] [LWA] Hyperion Foundation - configure a logical address for Web Applications

    (10 December 2013 01.01.41 PM): iron loop [000 min 03sec] [BEW] on the task pane

    Newspapers are vague and I don't know where to go from here. Any ideas?

    Thank you in advance.

    Hello

    Please check if you are able to run Weblogic if you use as a Weblogic application server.

    Because it is the application server that establishes the communication between components.

    Thank you

    Amith

  • Error importing ResourceObject xml file in Deployment Manager

    Hello world

    I get this error by making import of HRPeopleSoftResourceObjects.xml (A resource object xml file) in the Deployment Manager. I do this step of reconciliation Authoritative (Trusted Source).

    Error that says:- not present attribute in EntityDefination to user: ExpectedReturnDate.

    ExpectedReturnDate is a field of the UDF (Customize). I did the import of metadata and sandbox for this field create this attribute to IOM. I see this attribute on the user details screen as well as in the User Table by IOM. Ideally this error should be, no popup. I do this import of reconciliation.

    I pulled and checked all xml as (UserEO.xml.xml, userEO.xml.xml, userVO.xml, UserVO.xml.xml) of oracle.iam.console.identity.self-service.ear_V2.0_metadata1 files and found ExpectedReturnDate field is available.

    I use: IOM Version - Oracle 11g Release 2
    Version of database - 11.2.0
    WebLogic version - 10.3

    Please let me know how to fix this error.

    Appreciate your response and your support!

    Best regards
    Vijay Kumar

    The console design, open your resource object. Recon tab and click on the button create a profile reconciliation.

    -Kevin

  • access to the original inside the proxy service message

    I have the proxy (serviceType = Web Service, WSDL) service that is available to the client endpoint and I want to record the incoming message to the file on the disk. However, I want to persist any incoming message exectly (at the byte level) as it was sent by the sender (so with the envelope).
    Inside of the proxy service I have access to variables such as header, body etc. However, they are not good for my purpose because they differ from the corresponding parts of the original message. For example xmlns:soapenv = namespace "http://schemas.xmlsoap.org/soap/envelope/" in the original message
    defined only at the level of the envelope and not the header or body. But in the header and body available inside the proxy service variables they (namespaces) are visible. Mayby there are more differences, but this one is visible at a time.
    It is therefore possible to access (in order to save it) original message somehow? Any magical variable? Or mayby there is a way of saying the osb to be persisted (incoming query) in file? (it would be enough for me (of course I need file name).) I manage file by myself more far away).
    All advice appreciated

    If you choose the type of service that WSDL based or service of any SOAP, then OSB motor deconstruct the incoming SOAP envelope and complete parts of the envelope (header, body etc) to automatically correct context variables. This occurs before the flow of messages of proxy service is initiated, so you can't do anything. In the proxy service, you will receive the deconstructed only SOAP message.
    If you wish to record the exact message that has been received by the OSB, then change the type of service to (or create another proxy service in front of the existing proxy) type Messaging with text or binary content. Or you can also choose AnyXML service type, in which case the incoming SOAP envelope will be available inside variable $body in mail flow.

  • How to configure proxy services to use the file transport?

    Hello

    I configured a proxy service to query for files in the specified folder. And it is configured to use the file transport.

    While running, I get the exception - follwing


    < 27 April 2012 4:08:28 PM GMT + 05:30 > < error > < WliSbTransports > < BEA-381602 > < error has occurred during the elections of the ProxyService service endpoint resource $ ServiceTypes_SB$ BinaryService: javax.naming.NameNotFoundException: while trying to search for "wlsb.internal.transport.task.queue.file" did not find subcontext "wlsb. Solved "; other name "wlsb/internal/transport/task/queue / '.
    javax.naming.NameNotFoundException: while trying to search for "wlsb.internal.transport.task.queue.file" did not find subcontext "wlsb. Solved "; other name "wlsb/internal/transport/task/queue / '.
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    Truncated. check the log file full stacktrace

    Ask for help to solve this problem.

    Thanks in advance.

    Concerning
    Shyam.V

    Internal JMS queues depends on OSB are not there for some reason any.

    Are all correctly target JMS servers?

    How did you create the domain and all the managed servers are started?

  • Failed to create the Proxy service with transport JCA

    Hello everyone.
    I have some questions when trying to create the ftp with jca transport service. I followed the instructions in this tutorial:
    http://blogs.Oracle.com/MarkSmith/entry/osb_and_ftp_adapter_in_11g

    I stuck at step 4, cannot create proxy service to use JCA file I created by JDeveloper 11 g (11.1.1.5). When I specify the file of jca proxy service, an error message returned:
    <ALSB Console> <BEA-494002> <Internal error occured in OSBConsole : Transport exception occurred with the following message:
    Invalid JCA file for JCA proxy service. If you are creating a Proxy from a Business Service, please select a different transport type (for example, http). If not, JCA file must contain JCA activation spec properties.
    And here's my content created by JDeveloper jca file:
    <adapter-config name="myJCA_FTP_service" adapter="FTP Adapter" wsdlLocation="myJCA_FTP_service.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
      
      <connection-factory location="eis/ftp/MyFtpAdapter"/>
      <endpoint-interaction portType="Put_ptt" operation="Put">
        <interaction-spec className="oracle.tip.adapter.ftp.outbound.FTPInteractionSpec">
          <property name="PhysicalDirectory" value="/home/FTP-shared/upload"/>
          <property name="FileType" value="ascii"/>
          <property name="Append" value="false"/>
          <property name="FileNamingConvention" value="osb_%SEQ%"/>
          <property name="NumberMessages" value="1"/>
        </interaction-spec>
      </endpoint-interaction>
    
    </adapter-config>
    Is there someone who had attempted to use JCA adapter Ftp transport already? Please give me a suggestion.
    Any response is appreciated

    Best regards, Cuong Pham

    If you have selected the operation PUT you can only generate a business of the JCA service.

  • WebLogic. The Deployment Manager

    Can I deploy adf on weblogic server applications in jdeveloper 11.1.1.3.

    I need to deploy the application web adf using ANT or weblogic. Responsible for the deployment.

    However, I get errors as follows:


    --------------------------------------------------------------------------------

    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.

    C:\users\administrator > d:

    D:\ > cd D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server\bin

    D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server\bin > setDomainEnv.cmd
    D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server > java weblogic. The Deployment Manager
    adminurl - http://localhost:7001 - user weblogic-password eu1-deploy - download E:\SOAworkspace\otnapp\deploy\otnapp_application1.ear
    WebLogic. Deployer invoked with options: adminurl - http://localhost:7001 - user weblogic - deploy - download E:\SOAworkspace\otnapp\deploy\otnapp_application1.ear
    javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException
    to weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl. < init > (WebLogicDeploymentManagerImpl.java:121)
    at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)
    at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:496)
    at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:297)
    at weblogic.deploy.api.tools.deployer.Deployer.perform (Deployer.java:137
    )
    at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)

    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:115)
    in weblogic. Deployer.Run (deployer. Java:70)
    in weblogic. Deployer.main (deployer. Java:54)
    Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:141)
    at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
    to weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl. < init > (WebLogicDeploymentManagerImpl.java:118)
    at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)
    at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:496)
    at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:297)
    at weblogic.deploy.api.tools.deployer.Deployer.perform (Deployer.java:138
    )
    at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)

    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:116)
    ... 2 more
    Caused by: javax.naming.CommunicationException [root exception is java.net.Conne
    ctException: http://localhost:7001: Destination unreachable; nested exception is
    :
    java.net.ProtocolException: result not specified - Tunneling is the HTTP s
    Server host: 'localhost' and the port: '7001' a WebLogic Server? No available at destination router]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)
    at weblogic.jndi.Environment.getContext(Environment.java:315)
    at weblogic.jndi.Environment.getContext(Environment.java:285)
    at weblogic.jndi.Environment.createInitialContext(Environment.java:208)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:192)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:170)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getContext(ServerConnectionImpl.java:328)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getEnvironment(ServerConnectionImpl.java:300)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:139)
    at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
    to weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl. < init > (WebLogicDeploymentManagerImpl.java:118)
    at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)
    at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:496)
    at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:297)
    at weblogic.deploy.api.tools.deployer.Deployer.perform (Deployer.java:137
    )
    at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)

    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:115)
    ... 2 more
    Caused by: java.net.ConnectException: http://localhost:7001: Destination unreach
    capable; nested exception is:
    java.net.ProtocolException: result not specified - Tunneling is the HTTP server to the host: 'localhost' and the port: '7001' a WebLogic Server? No router available at destination
    at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
    to weblogic.jndi.WLInitialContextFactoryDelegate$ 1.run(WLInitialContextFactoryDelegate.java:345)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
    ... 19 more
    Caused by: java.rmi.ConnectException: Destination unreachable; nested exception
    is:
    java.net.ProtocolException: result not specified - Tunneling is the HTTP server to the host: 'localhost' and the port: '7001' a WebLogic Server? No provision rou
    to destination
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)

    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)

    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer (RJVMFinder.java:238
    )
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteCluster(RJVMFinder.java:316)
    at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:205)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
    to weblogic.jndi.WLInitialContextFactoryDelegate$ 1.run(WLInitialContextFactoryDelegate.java:345)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
    at weblogic.jndi.Environment.getContext(Environment.java:315)
    at weblogic.jndi.Environment.getContext(Environment.java:285)
    at weblogic.jndi.Environment.createInitialContext(Environment.java:208)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:192)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:170)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getContext(ServerConnectionImpl.java:328)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getEnvironment(ServerConnectionImpl.java:300)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:139)
    at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:150)
    to weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl. < init > (WebLogicDeploymentManagerImpl.java:118)
    at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)
    at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:496)
    at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:297)
    at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:138)
    at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)

    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:116)
    ... 2 more
    Unable to connect to 'http://localhost:7001': Destination unreachable; nested exception is:
    java.net.ProtocolException: result not specified - Tunneling is the HTTP server to the host: 'localhost' and the port: '7001' a WebLogic Server? No provision rou
    to destination. Make sure that the url is an administrator of the server running and that the credentials are correct. If you use the http protocol, the tunnel must be enabled on the management server.

    D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server >

    Re: How to use weblogic. The Deployment Manager

  • The use of weblogic. The Deployment Manager

    Can I deploy this application of adf to weblogic server in jdeveloper 11.1.1.3.
    The use of weblogic. Responsible for the deployment in weblogic 10.3.3? I get an error as follows:

    ----------------------------------------------------------------

    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.

    C:\users\administrator > d:

    D:\ > cd D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server\bin

    D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server\bin > setDomainEnv.cmd
    D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server > java weblogic. The Deployment Manager
    adminurl - http://localhost:7001 - user weblogic-password eu1-deploy - download E:\SOAworkspace\otnapp\deploy\otnapp_application1.ear
    WebLogic. Deployer invoked with options: adminurl - http://localhost:7001 - user weblogic - deploy - download E:\SOAworkspace\otnapp\deploy\otnapp_application1.ear
    javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException
    to weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl. < init > (WebLogicDeploymentManagerImpl.java:121)
    at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)
    at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:496)
    at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:297)
    at weblogic.deploy.api.tools.deployer.Deployer.perform (Deployer.java:137
    )
    at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)

    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:115)
    in weblogic. Deployer.Run (deployer. Java:70)
    in weblogic. Deployer.main (deployer. Java:54)
    Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:141)
    at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
    to weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl. < init > (WebLogicDeploymentManagerImpl.java:118)
    at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)
    at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:496)
    at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:297)
    at weblogic.deploy.api.tools.deployer.Deployer.perform (Deployer.java:138
    )
    at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)

    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:116)
    ... 2 more
    Caused by: javax.naming.CommunicationException [root exception is java.net.Conne
    ctException: http://localhost:7001: Destination unreachable; nested exception is
    :
    java.net.ProtocolException: result not specified - Tunneling is the HTTP s
    Server host: 'localhost' and the port: '7001' a WebLogic Server? No available at destination router]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)
    at weblogic.jndi.Environment.getContext(Environment.java:315)
    at weblogic.jndi.Environment.getContext(Environment.java:285)
    at weblogic.jndi.Environment.createInitialContext(Environment.java:208)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:192)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:170)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getContext(ServerConnectionImpl.java:328)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getEnvironment(ServerConnectionImpl.java:300)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:139)
    at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
    to weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl. < init > (WebLogicDeploymentManagerImpl.java:118)
    at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)
    at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:496)
    at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:297)
    at weblogic.deploy.api.tools.deployer.Deployer.perform (Deployer.java:137
    )
    at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)

    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:115)
    ... 2 more
    Caused by: java.net.ConnectException: http://localhost:7001: Destination unreach
    capable; nested exception is:
    java.net.ProtocolException: result not specified - Tunneling is the HTTP server to the host: 'localhost' and the port: '7001' a WebLogic Server? No router available at destination
    at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
    to weblogic.jndi.WLInitialContextFactoryDelegate$ 1.run(WLInitialContextFactoryDelegate.java:345)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
    ... 19 more
    Caused by: java.rmi.ConnectException: Destination unreachable; nested exception
    is:
    java.net.ProtocolException: result not specified - Tunneling is the HTTP server to the host: 'localhost' and the port: '7001' a WebLogic Server? No provision rou
    to destination
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)

    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)

    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer (RJVMFinder.java:238
    )
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteCluster(RJVMFinder.java:316)
    at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:205)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
    to weblogic.jndi.WLInitialContextFactoryDelegate$ 1.run(WLInitialContextFactoryDelegate.java:345)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
    at weblogic.jndi.Environment.getContext(Environment.java:315)
    at weblogic.jndi.Environment.getContext(Environment.java:285)
    at weblogic.jndi.Environment.createInitialContext(Environment.java:208)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:192)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:170)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getContext(ServerConnectionImpl.java:328)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getEnvironment(ServerConnectionImpl.java:300)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:139)
    at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:150)
    to weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl. < init > (WebLogicDeploymentManagerImpl.java:118)
    at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:86)
    at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:496)
    at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:297)
    at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:138)
    at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)

    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:116)
    ... 2 more
    Unable to connect to 'http://localhost:7001': Destination unreachable; nested exception is:
    java.net.ProtocolException: result not specified - Tunneling is the HTTP server to the host: 'localhost' and the port: '7001' a WebLogic Server? No provision rou
    to destination. Make sure that the url is an administrator of the server running and that the credentials are correct. If you use the http protocol, the tunnel must be enabled on the management server.

    D:\weblogicSA2011\wlserver_10.3\samples\domains\wl_server >

    It seems that the Protocol is not correct (unable to connect to 'http://localhost:7001': Destination unreachable)

    You can try the t3 Protocol, for example,

    java weblogic.Deployer -adminurl t3://localhost:7001 -username weblogic -password welcome1 -listapps
    

Maybe you are looking for