BRFPlus Vs BRM (Java)

Hi,
1) Can someone give a comparison between BRFPlus and BRM Java, ie, feature-wise ?
2) How can BRFPlus integrate with WDP ABAP and R/3 or other business suite?
3) Since WDP ABAP does not supported by BPM for UI, what other workflow can be used to integrate BRFPlus and WDP ABAP ?
Thanks in advance.
- julius

Hi Julius,
What you should consider is not ABAP or Java Stack but rather both together - i.e. taking the Dual Stack option. 
Yes the data all comes from the ABAP stack and all the SAP Business Workflow Engine and related transactions are in the ABAP stack.
The Universal Worklist Inbox is the Java component that brings the ABAP work items to the Java Portal via an extraction process - and provides connectors for bringing Java work items to the Portal as well... e.g. Collaborative Workflow. My understanding is that the UWL will also provide the user face for relevant parts of BRF/BPM.
The only option to integrate traditional workflow administration transactions at this stage would be via SAPGUI for HTML. But this is usually not needed - the workflow administrator works mainly in the ABAP stack, and the UWL provides all necessary conversions for user activities and actions.
In any case there are many other reasons why Dual Stack is the best approach - such as wanting to print forms or use interactive forms with Adobe Document Services, which is another area that requires both Java (for the engine) and ABAP for the data.
Having a Dual Stack helps to future proof you for new functionality such as BRF, BRM etc. as the decisions on where new functionality is placed are complex and it is not unusual for both stacks to be required for a complete solution.
Regards,
Jocelyn

Similar Messages

  • SAP NW BRM (java) and ABAP Customizing Tables

    Hi,
    A lot of "rules" of standard SAP (ERP for example) is traditionally located in Customizing Tables. What is the nicest way to integrate those "rules" with NW BRM without creating double maintenance, or UI disconnects (where the user has 2 apps open, BRM-UI (NWDS) and SAPgui)?

    Arti, this was quite an open question, I'm aware. Thanks for replying though.
    We would like to offer Business Users (probably BPXs) the ability to modify rules. For example, approval amount for PO.
    BRM seems the most likely candidate in this respect, especially since we use BPM heavily. But of course we use ERP  functionality (with its customizing) as well.
    We see an overlap in BRM decision tables and ERP Customizing Tables ("steering" tables, also Masterdata, non-transportable data). A lot of decisions / checks require the same data, but we don't want to maintain this both in ERP and BRM.
    Any ideas on this?

  • Comparision - BRM and BRFPlus

    Hello folks,
    I have a basic understanding of BRM (Java) and BRFPlus (ABAP) rule management engines.
    We want to define rules primarily (to start with) to use within ECC business workflows for Agent determination and I know BRFPlus is a way to go because integrating Business workflow and BRFPlus will be easier as they are on the same stack (ABAP).
    However due to some peculiar governance requirement of us, we are leaning towards using BRM(Java) for building rules. So here is what I am looking for...
    1) What are the disadvantages for using BRM(Java) when the primary purpose is to build rules for use in business workflow? I am looking for some sort of comparision between BRFPLus and BRM.
    2) Build rules using BRM, generate a Web service and call the webservices from a business workflow BG task, IS that a way to go if we decide to use BRM and not BRFplus? It would be great if someone who may have done this can share their experience/recommendations...
    Thanks,
    Saurabh

    Hi Carstern,
    We are looking at developing late this year with go-live mid next year.
    We are already on EhP4.
    The current (first) business scneario - Define rules for Agent determination in Workflow
    Here is why we are looking at BRM in addition to BRFPlus for use in ECC Business workflow..
    We design a template solution for use by mutiple organizations...So the rules that we design/build using BRFPlus will be controlled by us and not by those organizations...
    One of the organizations is already planning to set up BRM and they want complete control over any changes that may need to be made later to the rules. So we are exploring the possibility of that organization maintaining their rules in BRM and if we can invoke those rules either directly from the ECC workflow for Agent determination or going through BRFPlus using connector.
    What would be the best way to do it?
    1) Publish BRM rules as web services and consume it for ECC business workflow agent determination directly from workflow OR
    2) Make ECC business workflow always use BRFPlus and let BRFPlus talk to BRM through connector
    I appreciate your help,
    Saurabh

  • Can we call brfplus (ecc) from brfplus (crm) ?

    Hi Guys,
    We have two brms connectors in brfplus - Netweaver BRM or External
    can I use the external one to call brfplus (let's say on ecc) from a brfplus on crm ?
    Or should we use a different approach ?
    Thank you,
    Regards,
    Michal Krawczyk

    When talking about a central BRFplus system you have to distinguish between design time and runtime.
    With DSM you have one design time and can deploy decision services to several systems (without transport) which ensures an optimal governance of your business rules in your whole landscape. You don't need to transport the rule systems. But here the generated code is executed in your local systems: ERP, CRM...
    Does a central BRFplus system make sense. This is difficult to answer. Usually a decision service is called from an application (SAP standard or custom development) and so the rule system uses the data types of the system and local execution guarantees performance.
    But is possible, that a decision service needs input from other systems (data or calculations from otehr decision services). Such scenarios should be seen like SOA scenarios exposing their functionality as a set of services.
    So my question is why you want centralization. Do you want a central development, governance and deployment? Then DSM is the answer and established a central source of truth executed on various systems. Or do you have many decision services on various systems working together in a single service call? In this case you tie the systems together in terms of releases, availability and so on. This has its costs and you should have good reasons for it.
    Best Regards,
    Tobias

  • Upgrading Oracle from 11.1.0.7 to 11.2 INVALIDATES Rules Manager ?Any Idea

    Operating system is HP UX ia64 and I used Automatic upgrade method using DBUA
    SQL> select substr(comp_name,1,40) comp_name, status, substr (version,1,10) version from dba_registry order by comp_name;
    COMP_NAME STATUS VERSION
    JServer JAVA Virtual Machine VALID 11.2.0.1.0
    Oracle Database Catalog Views VALID 11.2.0.1.0
    Oracle Database Java Packages VALID 11.2.0.1.0
    Oracle Database Packages and Types VALID 11.2.0.1.0
    Oracle Enterprise Manager VALID 11.2.0.1.0
    Oracle Expression Filter VALID 11.2.0.1.0
    Oracle Real Application Clusters INVALID 11.2.0.1.0
    Oracle Rules Manager INVALID 11.2.0.1.0 ---------------------------------------have anybody encoountered this Plz help
    Oracle Workspace Manager VALID 11.2.0.1.0
    Oracle XDK REMOVED 11.1.0.7.0
    Oracle XML Database VALID 11.2.0.1.0
    Thanks for Help in advance
    Gagan

    Hello EveryOne!
    I also have the same problem.
    I tried to run the rulpatch script but the problem still the same.
    I'm on AIX 5.3
    the script output says:
    .. loading the Expression Filter/BRM Java library
    call sys.dbms_java.loadjava(' -v -f -r -schema exfsys rdbms/jlib/ExprFilter.jar')
    ERROR at line 1:
    ORA-29532: Java call terminated by uncaught Java exception:
    oracle.aurora.server.tools.loadjava.ToolsError:
    Error during loadjava: Failures occurred during processing.
    Check trace file for details
    ORA-06512: at "SYS.DBMS_JAVA", line 655.
    The Oracle Components :
    COMP_NAME STATUS PROCEDURE
    Oracle Expression Filter VALID VALIDATE_EXF
    Oracle Rules Manager                     INVALID VALIDATE_RUL
    Oracle XML Database VALID DBMS_REGXDB.VALIDATEXDB
    Oracle Enterprise Manager VALID
    Oracle Database Catalog Views VALID DBMS_REGISTRY_SYS.VALIDATE_CATALOG
    Oracle Database Packages and TypesVALID DBMS_REGISTRY_SYS.VALIDATE_CATPROC
    JServer JAVA Virtual Machine VALID INITJVMAUX.VALIDATE_JAVAVM
    Oracle Database Java Packages VALID DBMS_REGISTRY_SYS.VALIDATE_CATJAVA
    Thanks for the answers.
    Zs

  • 招聘J2EE高级程序员/分析员/数据库开发人员

    招聘J2EE高级程序员/分析员/数据库开发人员
    招聘职位:J2EE高级程序员(深圳):
    4 年以上 IT 工作经验
    掌握OCBRM (Oracle Communication for Billing, Revenue Management) Java API 开发技术 (必须)
    熟练J2EE Web开发技术
    月薪10000左右
    招聘职位:J2EE高级程序员(深圳):
    1. 3年以上J2ee开发经验,熟练掌握JSP,Servlet,Struts, Spring 和Hibernet.
    2. 要求具备Portal项目(Jboss/Oracle/IBM/BEA)开发经验.
    3. 熟练掌握数据库,能理解和维护复杂的SQL, 熟悉Oracle者优先.
    4. 熟悉Oracle PL/SQL或者 Devloper6i 者优先.
    5. 语言表达流畅思维清晰,善于和客户沟通,能听说广东话优先.
    月薪5-7K
    本职位具体联系人:李先生 电话:0755-26499588-17 email:[email protected]
    招聘职位:J2EE系统分析员(深圳):
    1 4年以上J2EE系统开发、分析设计和项目管理经验
    2 精通Java,UML, design pattern
    3 熟悉无线分布式系统开发项目
    4 熟悉大型项目的需求分析、架构设计、开发流程以及文档
    月薪8-10K
    本职位具体联系人:李先生 电话:0755-26499588-17email:[email protected]
    招聘职位:HyperionDeveloper:
    1 2年以上大型数据库应用系统开发经验,熟悉一种以上主流数据库(Oracle、IBMDB2、Sybase、Informix、MicrosoftSQLServer);
    2 至少1年DW系统前端展现工作经验,精通Hyperion系列产品,特别是Hyperion Essbase/Hyperion Reporting/Hyperion Planning;
    3 工作认真、负责,有良好的团队合作精神,良好的分析能力与沟通技巧;
    良好的沟通表达(英语或广东话)和英文文档交付能力;
    月薪5-7K
    招聘职位:HyperionAdvancedDeveloper:
    1.Daily loading of data/metadata into the Liz Claiborne Hyperion application
    (s)
    2.Ability to use Application Manager/Administration Services to design,
    create and maintain applications, databases, data load rules, calc scripts
    and report scripts.
    3.Works with internal customers to consistently improve and refine processes
    and procedures as it related to Planning & Analysis.
    4.Collaborates with the Director Financial Planning & Analysis in the
    development of the Strategic Plan, Annual Budget and monthly forecast’s.
    5.Manage security within the Hyperion suite
    6.Designs, Develops, and implements new reporting & analysis solutions within
    the Hyperion suite
    7.Serve as Internal Functional Helpdesk as it relates to the Hyperion suite.
    8.Design & Maintain documentation on system process flows, changes, enhancements.
    9.Must be able to act independently to resolve problems.
    10.Other duties and projects as required
    11.Create and Maintain reports within Microstrategy Business Intelligence application
    12.Ability to create and maintain reports written in JDE
    月薪8K左右
    招聘公司简介:                 
      该软件有限公司座落在商业繁华的罗湖区,公司成立于2001年,是香港最大的软件上市公司之一的下属子公司,现聘有一百二十余名员工。该公司主要为中国市场不同的客户提供资讯科技服务,包括:㈠制造行业的中小企业客户,提供自主研发ERP产品的解决方案和服务;㈡公共事业的客户,提供全球企业资产管理(EAM)领域的领导者——Datastream公司的产品D7i资产管理系统及MP2设备维修管理系统在华南地区的技术支持服务;㈢交通运输物流行业的客户,提供信息科技解决方案及项目外包工程服务。
      结合集团公司国际化的先进管理经验,及公司拥有的一支专业IT服务队伍,以及致力于为国内更多客户提供符合现代企业生产流程需求之资源管理软件的专业服务态度。该公司已经成功帮助全球最大码头服务商提供项目工程服务,并成为其长期的合作伙伴。
    0
     我顶!
    查阅更多相关主题的帖子: BRM JAVA J2EE ORACLE OCBRM

    Hi,
    though I understand you are looking to hire someone with a specific skill set, one that includes speaking your language, it would be good to post this in English as well to avoid confusion.
    Seeing that you posted the same post to other forums as well does make it look as Spam, which I have the feeling it is not. However, this is just another reason to at least provide a summary of what the non general readable portion contains.
    Frank

  • Difference between SAP PI ( Process Integration ) and SAP PO ( Process Orchestration )

    Hi,
    What is SAP PO ( Process Orchestration ) ?  How SAP PO is different from SAP PI.
    Regards
    Ravi Grover

    Hi Ravi,
    You can refer above helpful links, shared by hareesh and Harish
    Here is one heirarchy for better understanding of NW PO
    PI is straight forward : either Single Stack(AEX) or DS
    In SAP NW PO(bundle of PI + BPM + BRM)  we have 3 options:
    1. We have Single stack option , on one System i.e. All together, BRM(Java) + BPM(Java) + PI(AEX)
    2. We have Single stack option, on Seperate Systems i.e. {BRM(Java) + BPM(Java)} on one system + PI(AEX) on seperate
    3. BPM(Java) + BRM(Java) on one system and PI(DS) on one system
    However PI 7.31 can also be installed individually(i.e. without NW BPM and BRM)
    Thanks,
    Aman

  • BRM / BRFplus product compatibility list

    Hi all,
    Has there been a BRFplus / BRM product compatibility list created?  I'm looking for something that highlights the crossover functionality, and more importantly, the times when one product would be better to use than another.
    All I have seen so far is answers like 'When you are using the java stack use BRM' or 'When you are using ABAP stack use BRFplus'.  This is sometimes a little too vague though since so many of SAP's products integrate with each other in some way or another.
    If we could have a nice list that highlighted the best combination's of tools, that would be nice.  For example if we could easily find out which rules product would integrate best with a CRM / ERP landscape.  Or which rules product would work best if we were planning to use BPM alongside our CRM / ERP system and required our rules to consumed as web services in an SOA environment.
    Right now I'm finding lots of information on both products, but since the products are so similar it's hard to know which one to use for a given scenario.
    Any guidance appreciated!
    Thanks,
    Lee

    Hi Chris,
    We are stil working on a paper for comparison and a roadmap to bring both engines more closely together. There are some differences but there is also many similar things in the two products.
    Just give us some more time.
    BR,
    Carsten

  • BRM,BRF and BRFPLUS

    Hi,
    I am new to BRM,BRF and BRFPLUS.
    Can you please let me know the following
    1.Exact difference between BRM and BRF/BRFPLUS and between BRF and BRFPLUS?
    2.Any documents for basic concepts for all these having the explanation of basic things used like actions,expressions,rules etc
    3.Step by step basic example for BRM,BRF and BRFPLUS
    Thanks in advance

    Ok, firstly as one of your moderators - please do not shout in large font. That will not win you friends or get you answers any more quickly.  Please read the rules of engagement for correct etiquette on this site The Rules of Engagement
    Secondly your question goes over the boundary of two spaces.  You will get better responses, and are more likely to get responses if you ask them in the forum of the appropriate space, and avoid mixing topics as much as possible.
    BRM and BRFplus are discussed in the Business Rules Management space http://scn.sap.com/community/brm 
    In the Overview section on the main page of the space is a link to an overview document explaining the difference between some of theses technologies http://scn.sap.com/docs/DOC-26748
    BPM is discussed in the Business Process Management and Composition space http://scn.sap.com/community/bpm  Again on the main page of the space in the Overview area are Getting Started documents that include further links to basic knowledge for newbies.
    You should find these helpful.
    Thirdly, if you have new questions please start a new discussion.  Extended an existing discussion to a new set of questions tends to confuse the answers and reduces the number of responses you are likely to receive.
    Hope that helps
    Jocelyn

  • BRFPlus - license with NW fundation for 3rd party - SAP PO applies ?

    Hi,
    I got the impression that in order to use BRFPlus we need to have SAP NW fundation license for 3rd party,
    does anyone know, if we have SAP PO (process orchestration) which has a restricted SAP NW fundation license for 3rd party
    (to be used only with BPM, PI and BRM), can we use BRFPlus from PI ?
    Thank you for any comments,
    Regards,
    Michal Krawczyk

    Hi Michal,
    no idea about the licensing question, but I think you need an additional license due to the Java stack, but this has to be answered by an expert of SAP.
    Concerning the usage of BRFplus from PI: The only way I know to use the BRFplus functions from PI is via webservices generated out of the functions.
    The other way round is a little more comfortable as you can use the BRMS Connector expression.
    BR
    Christian

  • BRFplus Best Practises

    This is a question to Carsten or anybody that has some thoughts on the subject:
    I'm appointed BPM general on my project and will use this power to enforce separation between business logic and the application whenever possible. This means heavy use of BRFplus. I also plan to leave the business logic to key business users that are unusually competent for this type of project.
    This means that the business users have to build, maintain, test and monitor all the rules built by BRFplus (as well as all other business logic). We have to integrate them in SolMan test scenarios, mass test them with scripts, monitor execution results, have easy UI's everywhere, etc, etc. We will be on EH 702.
    So, what have other customers used BRFplus to do? Which good examples and ideas can you provide? Best practises? Good solution customers are happy with?
    I have a pretty good idea what we should achieve with this product but more ammunition to force a best practise in the BPM arena is always good to have. Also, I'm lazy, who figure out what someone else has already done.
    Cheers
    Martin

    Hi Martin,
    Do you plan to use BRFplus (rules engine for the ABAP stack) or NW BRM (rules engine for the Java stack)? In the current release both engines can call into the other. In future of course we want to go one step further for rules exchange. In case you use BPM I assume you know BRM, since it is tightly integrated into BPM. Of course you could call BRFplus from BPM through a WebService or RFC.
    Goring live with EHP 702 is strongly recommended for complex scenarios. EHP 701 is only good for simple scenarios.
    Maybe it is best we setup a call to discuss the other questions. Will yo attend TechEd? We can also meet at TechEd Vienna or Phoenix. My colleagues will do the Bangalore and Shanghai sessions.
    BR,
    Carsten

  • Deploy java components error in NW7.4 installation

    Hi Experts,
    I am installing NW 7.4, i have done all the pre-installation steps but i am getting error at deploy java components.
    please find the log. please help me in this it is very urgent. I need your experience.
    An error occurred while processing option SAP NetWeaver 7.4 Support Release 2 > MaxDB > SAP Systems > Optional Standalone Units > Process Orchestration > Standard System > Process Integration and Orchestration Package( Last error reported by the step: Execution of Deploy Controller Runner tool '"C:\Program Files\sapinst_instdir\NW740SR2\ADA\INSTALL\STANDALONE\STD\PICP\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW740SR2/ADA/INSTALL/STANDALONE/STD/PICP/install/lib;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_jce.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_jsse.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_smime.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/iaik_ssl.jar;\\PO/sapmnt/POP/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/POP/J00/j2ee/j2eeclient/sap.com~tc~exception~impl.jar;D:/usr/sap/POP/J00/j2ee/j2eeclient/sap.com~tc~je~clientlib~impl.jar;D:/usr/sap/POP/J00/j2ee/j2eeclient/sap.com~tc~logging~java~impl.jar;C:/Program Files/sapinst_instdir/NW740SR2/ADA/INSTALL/STANDALONE/STD/PICP/install/lib/tc~je~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:\Program Files\sapinst_instdir\NW740SR2\ADA\INSTALL\STANDALONE\STD\PICP\deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host PO --port 50004' aborts with return code 104. Error message is 'Component:BI_UDI ( sap.com) Status:Aborted Description:. SOLUTION: Check 'C:\Program Files\sapinst_instdir\NW740SR2\ADA\INSTALL\STANDALONE\STD\PICP\log\dc_log\deploy_api.0.log' and 'deploycontroller.log' for more information.). You can now:
    Choose Retry to repeat the current step.
    Choose Log Files to get more information about the error.
    Stop the option and continue later.
    Log files are written to C:\Program Files/sapinst_instdir/NW740SR2/ADA/INSTALL/STANDALONE/STD/PICP.
    Regards,
    Patan Thavaheer.

    Hi manu,
    Please find the error log.
    [ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    [ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
      at javax.naming.InitialContext.init(InitialContext.java:223)
      at javax.naming.InitialContext.<init>(InitialContext.java:197)
      at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
      at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
      at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
      at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
      at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
      ... 14 more
    Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
      at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
      at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
      ... 16 more
    [ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    [ Info ] +++ Wait for server response +++. Deploying offline [31] seconds. Will timeout in [14,368] seconds.
    [ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
      at javax.naming.InitialContext.init(InitialContext.java:223)
      at javax.naming.InitialContext.<init>(InitialContext.java:197)
      at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
      at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
      at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
      at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
      at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
      ... 14 more
    Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
      at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
      at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
      ... 16 more
    [ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    [ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
      at javax.naming.InitialContext.init(InitialContext.java:223)
      at javax.naming.InitialContext.<init>(InitialContext.java:197)
      at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
      at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
      at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
      at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
      at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
      ... 14 more
    Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
      at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
      at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
      ... 16 more
    [ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    [ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
      at javax.naming.InitialContext.init(InitialContext.java:223)
      at javax.naming.InitialContext.<init>(InitialContext.java:197)
      at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
      at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
      at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
      at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
      at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
      ... 14 more
    Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
      at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
      at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
      ... 16 more
    [ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    [ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
      at javax.naming.InitialContext.init(InitialContext.java:223)
      at javax.naming.InitialContext.<init>(InitialContext.java:197)
      at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
      at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
      at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
      at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
      at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
      ... 14 more
    Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
      at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
      at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
      ... 16 more
    [ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    [ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
      at javax.naming.InitialContext.init(InitialContext.java:223)
      at javax.naming.InitialContext.<init>(InitialContext.java:197)
      at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
      at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
      at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
      at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
      at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
      ... 14 more
    Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
      at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
      at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
      ... 16 more
    [ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    [ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50597]. Check if the host and port specified are correct and AS Java is up and running.
    javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
      at javax.naming.InitialContext.init(InitialContext.java:223)
      at javax.naming.InitialContext.<init>(InitialContext.java:197)
      at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
      at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
      at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
      at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
      at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
      ... 14 more
    Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50597]
      at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:501)
      at java.lang.Thread.run(Thread.java:763)
    [ Error ] Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50597]. Check if the host and port specified are correct and AS Java is up and running.
    [ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
      at javax.naming.InitialContext.init(InitialContext.java:223)
      at javax.naming.InitialContext.<init>(InitialContext.java:197)
      at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
      at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
      at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
      at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
      at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
      ... 14 more
    Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
      at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
      at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
      ... 16 more
    [ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    [ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
      at javax.naming.InitialContext.init(InitialContext.java:223)
      at javax.naming.InitialContext.<init>(InitialContext.java:197)
      at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
      at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
      at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
      at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
      at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
      ... 14 more
    Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
      at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
      at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
      ... 16 more
    [ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    [ Info ] +++ Wait for server response +++. Deploying offline [48] seconds. Will timeout in [14,351] seconds.
    [ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
      at javax.naming.InitialContext.init(InitialContext.java:223)
      at javax.naming.InitialContext.<init>(InitialContext.java:197)
      at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
      at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
      at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
      at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
      at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
      ... 14 more
    Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
      at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
      at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
      ... 16 more
    [ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    [ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50615]. Check if the host and port specified are correct and AS Java is up and running.
    javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
      at javax.naming.InitialContext.init(InitialContext.java:223)
      at javax.naming.InitialContext.<init>(InitialContext.java:197)
      at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
      at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
      at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
      at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
      at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
      ... 14 more
    Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50615]
      at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:501)
      at java.lang.Thread.run(Thread.java:763)
    [ Error ] Could not establish connection to AS Java on [PO:50004]. End of stream is reached unexpectedly during input from Socket[addr=/192.168.2.87,port=50004,localport=50615]. Check if the host and port specified are correct and AS Java is up and running.
    [ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
      at javax.naming.InitialContext.init(InitialContext.java:223)
      at javax.naming.InitialContext.<init>(InitialContext.java:197)
      at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
      at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
      at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
      at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
      at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
      ... 14 more
    Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
      at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
      at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
      ... 16 more
    [ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    [ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
      at javax.naming.InitialContext.init(InitialContext.java:223)
      at javax.naming.InitialContext.<init>(InitialContext.java:197)
      at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
      at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
      at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
      at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
      at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
      at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
      at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
      at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
      ... 14 more
    Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813)
      at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362)
      at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123)
      at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
      at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
      ... 16 more
    [ Error ] Could not establish connection to AS Java on [PO:50004]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running.
    [ Info ] +++ Deployment of session ID [21] finished with status [Error] +++. [[ deployerId=1 ]] [[#3: 340.111 sec]] [
    ===== Summary - Deploy Result - Start =====
    Type | Status  : Count
    > SCA(s)
       - [Aborted] : [80]
    > SDA(s)
       - [Success] : [80]
       - [Admitted] : [1189]
    Type | Status  : Id
    > SCA(s)
       - [Aborted] : name: 'BI_UDI', vendor: 'sap.com', name: 'COMP_BUILDT', vendor: 'sap.com', name: 'CU-BASE-JAVA', vendor: 'sap.com', name: 'CU-BASE-WD', vendor: 'sap.com', name: 'DATA-MAPPING', vendor: 'sap.com', name: 'ECM-CORE', vendor: 'sap.com', name: 'ESCONF_BUILDT', vendor: 'sap.com', name: 'ESMP_BUILDT', vendor: 'sap.com', name: 'LM-TOOLS', vendor: 'sap.com', name: 'MMR_SERVER', vendor: 'sap.com', name: 'MOIN_BUILDT', vendor: 'sap.com', name: 'NWTEC', vendor: 'sap.com', name: 'EP-BASIS', vendor: 'sap.com', name: 'SERVICE-COMP', vendor: 'sap.com', name: 'SWLIFECYCL', vendor: 'sap.com', name: 'UKMS_JAVA', vendor: 'sap.com', name: 'KM-KW_JIKS', vendor: 'sap.com', name: 'INTG_VIS', vendor: 'sap.com', name: 'SAP_XIADMIN', vendor: 'sap.com', name: 'SAP_XITOOL', vendor: 'sap.com', name: 'PI-SCP-EXT', vendor: 'sap.com', name: 'PI-SCP-BUILDT', vendor: 'sap.com', name: 'BPEM-CORE', vendor: 'sap.com', name: 'BPEM-FACADE', vendor: 'sap.com', name: 'BPEM-COLLAB', vendor: 'sap.com', name: 'BPEM-BASE', vendor: 'sap.com', name: 'BPEM-BUILDT', vendor: 'sap.com', name: 'BPEM-CONTENT', vendor: 'sap.com', name: 'BPEM-HIM', vendor: 'sap.com', name: 'BPEM-MM', vendor: 'sap.com', name: 'BPEM-MON', vendor: 'sap.com', name: 'BPEM-PP', vendor: 'sap.com', name: 'BPEM-WDUI', vendor: 'sap.com', name: 'BPEM-CUUI', vendor: 'sap.com', name: 'BRMS-BASE', vendor: 'sap.com', name: 'BRMS-BUILDT', vendor: 'sap.com', name: 'BRMS-CORE', vendor: 'sap.com', name: 'BRMS-FACADE', vendor: 'sap.com', name: 'BRMS-WDUI', vendor: 'sap.com', name: 'BRMS-MON', vendor: 'sap.com', name: 'FP-INFRA', vendor: 'sap.com', name: 'CU-BASE-WD-EXT', vendor: 'sap.com', name: 'TM-WLUI', vendor: 'sap.com', name: 'BPEM-ACC', vendor: 'sap.com', name: 'CAF-MF', vendor: 'sap.com', name: 'CAF-UI', vendor: 'sap.com', name: 'COLLAB-ADP', vendor: 'sap.com', name: 'CAF', vendor: 'sap.com', name: 'BI-BASE-S', vendor: 'sap.com', name: 'BI-BASE-B', vendor: 'sap.com', name: 'BI-BASE-E', vendor: 'sap.com', name: 'SEA-CORE', vendor: 'sap.com', name: 'SEA-FACADE', vendor: 'sap.com', name: 'SEA-UI', vendor: 'sap.com', name: 'BI-WDEXT', vendor: 'sap.com', name: 'CU-WD4VC-ADPT', vendor: 'sap.com', name: 'ECM-APPS', vendor: 'sap.com', name: 'ECM-STORE', vendor: 'sap.com', name: 'EP-ADMIN', vendor: 'sap.com', name: 'EP_BUILDT', vendor: 'sap.com', name: 'EP-CONNECTIVITY', vendor: 'sap.com', name: 'EP-MODELING', vendor: 'sap.com', name: 'EP-RUNTIME', vendor: 'sap.com', name: 'UWLJWF', vendor: 'sap.com', name: 'VCFREESTYLEKIT', vendor: 'sap.com', name: 'VCCORERT', vendor: 'sap.com', name: 'VCBASE', vendor: 'sap.com', name: 'VCKITBI', vendor: 'sap.com', name: 'VCFRAMEWORK', vendor: 'sap.com', name: 'VTP_BUILDT', vendor: 'sap.com', name: 'WDEXTENSIONS', vendor: 'sap.com', name: 'WD-FLEX', vendor: 'sap.com', name: 'ECM-ADMIN', vendor: 'sap.com', name: 'ECM-JEE-COMP', vendor: 'sap.com', name: 'SAP_XIESR', vendor: 'sap.com', name: 'SAP_XIGUILIB', vendor: 'sap.com', name: 'XI_CNT_SAP_BASIS', vendor: 'sap.com', name: 'INTG_VIS_DCJ', vendor: 'sap.com', name: 'SAP_XIAF', vendor: 'sap.com', name: 'SOAMON', vendor: 'sap.com',
    > SDA(s)
       - [Success] : name: 'com.sap.ip.bi.sdk.dac.connector.odbodll', vendor: 'sap.com', name: 'com.sap.glx.mapping.lib', vendor: 'sap.com', name: 'com.sap.glx.common.rt.lib', vendor: 'sap.com', name: 'tc~lm~ctc~confs~service_sda', vendor: 'sap.com', name: 'bi~mmr~dictionary', vendor: 'sap.com', name: 'bi~mmr~deployer', vendor: 'sap.com', name: 'com.sap.portal.pcm.indexingservice', vendor: 'sap.com', name: 'com.sap.netweaver.rtmf.server', vendor: 'sap.com', name: 'tc~rtmf~service', vendor: 'sap.com', name: 'com.sap.aii.sca.xi.svc', vendor: 'sap.com', name: 'com.sap.aii.sca.maas.svc', vendor: 'sap.com', name: 'tc~bpem~eventlog~ddic', vendor: 'sap.com', name: 'com.sap.glx.base.lib', vendor: 'sap.com', name: 'com.sap.glx.container.dbschema', vendor: 'sap.com', name: 'com.sap.glx.rrhandlermanager.svc', vendor: 'sap.com', name: 'com.sap.glx.repository.handler.dbschema', vendor: 'sap.com', name: 'com.sap.glx.core.svc', vendor: 'sap.com', name: 'com.sap.glx.contextcontainer.dbschema', vendor: 'sap.com', name: 'com.sap.glx.core.dbschema', vendor: 'sap.com', name: 'com.sap.glx.core.svc.facade', vendor: 'sap.com', name: 'tc~bpem~index~ddic', vendor: 'sap.com', name: 'tc~bpem~base~svc', vendor: 'sap.com', name: 'com.sap.glx.repository.dbschema', vendor: 'sap.com', name: 'tc~bpem~bl~lib', vendor: 'sap.com', name: 'tc~bpem~base~type~plib', vendor: 'sap.com', name: 'com.sap.glx.repository.ifc', vendor: 'sap.com', name: 'com.sap.glx.repository.svc', vendor: 'sap.com', name: 'tc~bpem~base~lib', vendor: 'sap.com', name: 'tc~bpem~tm~ddic', vendor: 'sap.com', name: 'tc~bpem~shared~lib', vendor: 'sap.com', name: 'tc~brms~engine~lib', vendor: 'sap.com', name: 'tc~brms~ws~svc', vendor: 'sap.com', name: 'tc~brms~repository~svc', vendor: 'sap.com', name: 'tc~brms~io~plib', vendor: 'sap.com', name: 'tc~brms~acl~plib', vendor: 'sap.com', name: 'tc~brms~ddic', vendor: 'sap.com', name: 'tc~brms~wdui~plib', vendor: 'sap.com', name: 'caf~um~relgroups~ddic', vendor: 'sap.com', name: 'tc~esi~sea~schema~ddic', vendor: 'sap.com', name: 'tc~esi~sea~service', vendor: 'sap.com', name: 'tc~esi~sea~api~lib', vendor: 'sap.com', name: 'com.sap.portal.healthChecks', vendor: 'sap.com', name: 'com.sap.portal.fpn.migration.fpnmigrationlib', vendor: 'sap.com', name: 'com.sap.portal.landscape.config', vendor: 'sap.com', name: 'tc~pp~gpal~deploylistener', vendor: 'sap.com', name: 'com.sap.portal.fpn.service', vendor: 'sap.com', name: 'com.sap.portal.smart.smartsrv', vendor: 'sap.com', name: 'com.sap.obn.migration.obnmigrationlib', vendor: 'sap.com', name: 'tc~kmc~bc.uwl~api', vendor: 'sap.com', name: 'devserver_lib', vendor: 'sap.com', name: 'vc_ds_service', vendor: 'sap.com', name: 'vc_generation', vendor: 'sap.com', name: 'ds_repository', vendor: 'sap.com', name: 'ds_environment', vendor: 'sap.com', name: 'visualcomposer_server_api', vendor: 'sap.com', name: 'SAPMetamodelFW', vendor: 'sap.com', name: 'SAPBuildPluginHandler', vendor: 'sap.com', name: 'tc~ecm~svc~deploy', vendor: 'sap.com', name: 'com.sap.aii.adapter.rfc.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.ispeak.svc', vendor: 'sap.com', name: 'com.sap.aii.af.maas.lib', vendor: 'sap.com', name: 'com.sap.aii.af.ifc.facade', vendor: 'sap.com', name: 'com.sap.aii.adapter.marketplace.lib', vendor: 'sap.com', name: 'com.sap.aii.adapter.jdbc.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.bc.svc', vendor: 'sap.com', name: 'com.sap.aii.af.int.svc.facade', vendor: 'sap.com', name: 'com.sap.aii.af.svc.facade', vendor: 'sap.com', name: 'com.sap.aii.mapping.lib.facade', vendor: 'sap.com', name: 'com.sap.aii.adapter.file.svc', vendor: 'sap.com', name: 'com.sap.aii.af.lib.facade', vendor: 'sap.com', name: 'com.sap.aii.proxy.svc.facade', vendor: 'sap.com', name: 'com.sap.aii.adapter.marketplace.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.ispeak.dbs', vendor: 'sap.com', name: 'com.sap.aii.adapter.mail.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.ws.cxf.lib', vendor: 'sap.com', name: 'com.sap.aii.proxy.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.xi.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.http.svc', vendor: 'sap.com', name: 'com.sap.aii.adapter.jms.svc', vendor: 'sap.com', name: 'com.sap.aii.af.axis.lib', vendor: 'sap.com',
       - [Admitted] : name: 'com.sap.ip.bi.sdk.monitoring', vendor: 'sap.com', name: 'bi~sdk~resultset', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checks', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checko', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.xmla.x', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.jdbc', vendor: 'sap.com', name: 'tc~bi~sdk', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.ds', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.fields', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.java', vendor: 'sap.com', name: 'bi~sdk~core', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.sys', vendor: 'sap.com', name: 'bi~sdk~query', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.datasource.sync', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checkj', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.xmla', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.checkx', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.odbo', vendor: 'sap.com', name: 'sc~bi_udi', vendor: 'sap.com', name: 'com.sap.ip.bi.sdk.dac.connector.sapq', vendor: 'sap.com', name: 'sc~comp_buildt', vendor: 'sap.com', name: 'sc~cu-base-java', vendor: 'sap.com', name: 'tc~cu~base~java~ear', vendor: 'sap.com', name: 'tc~cu~base~wd~adapter~wd2wd~ps', vendor: 'sap.com', name: 'tc~cu~base~wd~core', vendor: 'sap.com', name: 'tc~cu~base~wd~adapter~wd2wd', vendor: 'sap.com', name: 'sc~cu-base-wd', vendor: 'sap.com', name: 'tc~cu~base~wd~intapi', vendor: 'sap.com', name: 'tc~cu~base~wd~utils', vendor: 'sap.com', name: 'tc~cu~base~wd~contract~ps', vendor: 'sap.com', name: 'sc~data-mapping', vendor: 'sap.com', name: 'tc~ecm~core', vendor: 'sap.com', name: 'sc~ecm-core', vendor: 'sap.com', name: 'tc~ecm', vendor: 'sap.com', name: 'sc~esconf_buildt', vendor: 'sap.com', name: 'sc~esmp_buildt', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~model', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~taskplnr', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~processviewer', vendor: 'sap.com', name: 'tc~lm~itsam~lmr~app', vendor: 'sap.com', name: 'tc~bcf~prov~ddic', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~initialsetuptables', vendor: 'sap.com', name: 'tc~lm~itsam~ui~ctc~wd', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~master', vendor: 'sap.com', name: 'tc~lm~aci~engine~sapctrl~wsproxy', vendor: 'sap.com', name: 'tc~lm~aci~engine~ddic', vendor: 'sap.com', name: 'tc~slm~ui_maintain', vendor: 'sap.com', name: 'tc~archtech~browser_ume', vendor: 'sap.com', name: 'tc~slm~ui_jnet', vendor: 'sap.com', name: 'tc~lm~ctc~itsam~kpi', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~defaultui', vendor: 'sap.com', name: 'tc~bcf~ws~ddic', vendor: 'sap.com', name: 'tc~lm~aci~vpm~wsproxy~sap', vendor: 'sap.com', name: 'tc~bcf~prov~wd', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~compif', vendor: 'sap.com', name: 'tc~bcf~lib~ear', vendor: 'sap.com', name: 'tc~lm~itsam~ui~sys~overview~xi~wd', vendor: 'sap.com', name: 'tc~lm~aci~virtual~vmware~wsproxy', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~resource', vendor: 'sap.com', name: 'tc~bcf_xi~ear', vendor: 'sap.com', name: 'tc~archtech~sbook_wd', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~other_ear', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~aclog', vendor: 'sap.com', name: 'tc~bcf~prov~ear', vendor: 'sap.com', name: 'tc~sec~sanity~jmx~sda', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~locator', vendor: 'sap.com', name: 'tc~slm~ui_review', vendor: 'sap.com', name: 'tc~lm~aci~engine~csm~wsproxy', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~utils', vendor: 'sap.com', name: 'tc~archtech~browser~viewer~xmlui', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~sldregisterapp', vendor: 'sap.com', name: 'sc~lm-tools', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~services', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~vpm', vendor: 'sap.com', name: 'tc~lm~ctc~confs~startup_app', vendor: 'sap.com', name: 'tc~lm~itsam~ui~overview~panel~interface', vendor: 'sap.com', name: 'tc~lm~itsam~ui~avail~panel', vendor: 'sap.com', name: 'tc~bcf~ws~ear', vendor: 'sap.com', name: 'tc~slm~ui_slm', vendor: 'sap.com', name: 'tc~lm~itsam~ui~thresholds~wd', vendor: 'sap.com', name: 'tc~lm~ctc~ccl~rep~hist~ddic', vendor: 'sap.com', name: 'tc~lm~aci~engine~archconfig', vendor: 'sap.com', name: 'tc~lm~itsam~ui~sysinfo', vendor: 'sap.com', name: 'tc~lm~aci~engine~hstctrl~wsproxy', vendor: 'sap.com', name: 'tc~lm~ctc~nwa~spc~config_ear', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~types', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~model', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~overview', vendor: 'sap.com', name: 'tc~slm~ui_navigation', vendor: 'sap.com', name: 'tc~archtech~sbook_init_j2ee', vendor: 'sap.com', name: 'tc~bcf~prov~ddic~content', vendor: 'sap.com', name: 'tc~sld~destsvc_dic', vendor: 'sap.com', name: 'tc~bizc~ws~ear', vendor: 'sap.com', name: 'tc~archtech~browser', vendor: 'sap.com', name: 'tc~archtech~sbook_j2ee', vendor: 'sap.com', name: 'tc~sec~sanity~wd', vendor: 'sap.com', name: 'tc~lm~itsam~ui~nwso~cfg~db', vendor: 'sap.com', name: 'tc~lm~itsam~ui~perf~panel', vendor: 'sap.com', name: 'tc~archtech~browser~dbschema', vendor: 'sap.com', name: 'tc~bcf~transport~ddic', vendor: 'sap.com', name: 'tc~lm~aci~apps~wd~ui~acenable', vendor: 'sap.com', name: 'tc~lm~nzdm~crr~ui', vendor: 'sap.com', name: 'bi~mmr~mini_md_library', vendor: 'sap.com', name: 'bi~mmr~mini_mm_library', vendor: 'sap.com', name: 'bi~mmr~api', vendor: 'sap.com', name: 'bi~mmr~webToolsEAP', vendor: 'sap.com', name: 'bi~mmr~bi_library', vendor: 'sap.com', name: 'bi~mmr~bi_ear', vendor: 'sap.com', name: 'bi~mmr~mmrlib', vendor: 'sap.com', name: 'bi~mmr~reportmodel_library', vendor: 'sap.com', name: 'bi~mmr~cwm_1.0_library', vendor: 'sap.com', name: 'bi~mmr~reportmodel_ear', vendor: 'sap.com', name: 'bi~mmr~jnet', vendor: 'sap.com', name: 'bi~mmr~cwm_1.0_ear', vendor: 'sap.com', name: 'sc~mmr_server', vendor: 'sap.com', name: 'bi~mmr~mmrapplib', vendor: 'sap.com', name: 'bi~mmr~mof_1.4_library', vendor: 'sap.com', name: 'bi~mmr~amlib', vendor: 'sap.com', name: 'bi~mmr~mini_mm_ear', vendor: 'sap.com', name: 'bi~mmr~mini_md_ear', vendor: 'sap.com', name: 'bi~mmr~bi_repository', vendor: 'sap.com', name: 'bi~mmr~metamodel_library', vendor: 'sap.com', name: 'bi~mmr~mof_1.4_ear', vendor: 'sap.com', name: 'bi~mmr~ejb', vendor: 'sap.com', name: 'bi~mmr~metamodel_ear', vendor: 'sap.com', name: 'sc~moin_buildt', vendor: 'sap.com', name: 'sc~nwtec', vendor: 'sap.com', name: 'tc~di~sdic~support~wd', vendor: 'sap.com', name: 'com.sap.portal.supportability.isolde.api', vendor: 'sap.com', name: 'com.sap.portal.pcd.textrepository', vendor: 'sap.com', name: 'com.sap.portal.prt.cache', vendor: 'sap.com', name: 'com.sap.portal.htmlb', vendor: 'sap.com', name: 'tc~jpe~dbschema', vendor: 'sap.com', name: 'com.sap.portal.design.urdesigndataless', vendor: 'sap.com', name: 'com.sap.portal.pcm.admin.pcdimplservice', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.notification', vendor: 'sap.com', name: 'sc~ep-basis', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.clusterinformation', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.contentconverter', vendor: 'sap.com', name: 'tc~epbc~pcd~pars~srvgl', vendor: 'sap.com', name: 'com.sap.portal.pcd.admintools.ucdadmin', vendor: 'sap.com', name: 'com.sap.portal.pcd.aclservice', vendor: 'sap.com', name: 'com.sap.portal.design.ui5designdataless', vendor: 'sap.com', name: 'com.sap.security.ume.consistencycheck', vendor: 'sap.com', name: 'com.sap.portal.pcd.admintools.configuration', vendor: 'sap.com', name: 'com.sap.portal.pcd.umwrapperservice', vendor: 'sap.com', name: 'tc~epbc~prt~apps~restricted', vendor: 'sap.com', name: 'rtmfcommunicator', vendor: 'sap.com', name: 'com.sap.portal.themes.lafservice', vendor: 'sap.com', name: 'tc~epbc~resourcerepository~api', vendor: 'sap.com', name: 'com.sap.portal.usermapping', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.hooks', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.authentication', vendor: 'sap.com', name: 'com.sap.portal.pcd.softcacheservice', vendor: 'sap.com', name: 'com.sap.portal.pcm.metadata.service', vendor: 'sap.com', name: 'tc~epbc~pcm~pcmadminimplsrv', vendor: 'sap.com', name: 'com.sap.portal.design.vc5designdataless', vendor: 'sap.com', name: 'com.sap.portal.pcd.basicrolefactory', vendor: 'sap.com', name: 'tc~supportplatform~wd', vendor: 'sap.com', name: 'com.sap.portal.design.portaldesigndata', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.prtconnection', vendor: 'sap.com', name: 'com.sap.portal.runtime.prtws', vendor: 'sap.com', name: 'com.sap.portal.resourcerepository', vendor: 'sap.com', name: 'com.sap.portal.pcd.lockservice', vendor: 'sap.com', name: 'irj', vendor: 'sap.com', name: 'tc~epbc~prt~apps', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.xsltransform', vendor: 'sap.com', name: 'com.sap.portal.pcd.traceservice', vendor: 'sap.com', name: 'tc~epbc~pcm~ext', vendor: 'sap.com', name: 'com.sap.portal.design.portaldesigndataless', vendor: 'sap.com', name: 'tc~rtmf~wdtestapp', vendor: 'sap.com', name: 'com.sap.portal.pcd.basictransport', vendor: 'sap.com', name: 'com.sap.portal.pcd.glservice', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.idcounters', vendor: 'sap.com', name: 'com.sap.portal.design.urdesigndata', vendor: 'sap.com', name: 'com.sap.portal.usermanagement.admin', vendor: 'sap.com', name: 'tc~epbc~ume~ep5~deprecated', vendor: 'sap.com', name: 'tc~jpe~engine', vendor: 'sap.com', name: 'tc~epbc~pcd~pars~restricted', vendor: 'sap.com', name: 'tc~ep~useragent~api', vendor: 'sap.com', name: 'com.sap.portal.runtime.gwtintegration', vendor: 'sap.com', name: 'tc~bc~jpe~engine~api', vendor: 'sap.com', name: 'com.sap.portal.runtime.system.connection', vendor: 'sap.com', name: 'com.sap.portal.usermanagement', vendor: 'sap.com', name: 'com.sap.portal.pcd.configservice', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.soap', vendor: 'sap.com', name: 'pcm_ext_libSDA', vendor: 'sap.com', name: 'com.sap.portal.runtime.application.document', vendor: 'sap.com',

  • I need Fusion help creating a demo of BRM JCA Resource Adapter

    I need Fusion help creating a demo of BRM JCA Resource Adapter.
    I know BRM well but am clueless with Fusion.
    I am trying to figure out what Fusion products to download and install and how I manipulate the Fusion side to manipulate BRM.
    My BRM docs say:
    Installing the BRM JCA Resource Adapter ->
    Software requirements
    (yada yada install a bunch of BRM stuff I know how to do)
    The adapter must be deployed on a J2EE 1.4-compliant application server that has implemented the JCA 1.5 specification. The adapter runs only in a managed environment. (Does this imply some particular Fusion package?)
    (more yada yada about installing more BRM packages I know how to do)
    Deploying and configuring the BRM JCA Resource Adapter ->
    Overview of the BRM JCA Resource Adapter configuration procedure
    The procedure for setting up the BRM JCA Resource Adapter includes the following tasks:
    Installing the adapter on your BRM system, if you have not already done so. See Installing the BRM JCA Resource Adapter.
    Generating the schema files for the adapter. See Generating the schema files for your system. (links to some BRM commands np)
    Specifying how to construct XML tags. See Specifying the XML tags for extended fields. (links to an oob file included with directions on how to address BRM customizations np)
    Generating the WSDL files for the adapter. See Generating the WSDL files for your system. (links to an oob file with directions to configure. I could use some help if/when I get this far)
    The last two look pretty important but I haven't a clue. I pasted the text from the docs below.
    Deploying the adapter on your application server. See Deploying the BRM JCA Resource Adapter on an Oracle application server.
    Connecting the adapter to the BRM software. See Connecting the adapter to BRM in Oracle AS.
    Deploying the BRM JCA Resource Adapter on an Oracle application server
    The adapter is dependent on Java Archive (JAR) files to deploy properly. The following table lists the JAR files that the adapter requires from each application in your system.
    Application
    JAR files
    J2EE application server
    classes12.jar, connector15.jar, and jta.jar
    Oracle BPEL process
    bpm-infra.jar, orabpel-thirdparty.jar, orabpel.jar, and xmlparserv2.jar
    BRM J2EE Resource Adapter
    pcm.jar and pcmext.jar
    Apache
    xercesImpl.jar
    If you are deploying the adapter in a standalone Oracle Containers for Java EE (OC4J) instance, make sure these JAR files are available to the class loader that is loading the adapter.
    If you are deploying the adapter by using Oracle SOA Suite, these JAR files are available as part of the oracle.bpel.common code source. You import these libraries as follows:
    Open the Oracle_home/j2ee/Instance/config/applications.xml configuration file for the J2EE instance.
    Add the oracle.bpel.common entry (shown in bold below) to the imported-shared-libraries section of the file:
    <imported-shared-libraries>
    <import-shared-library name="adf.oracle.domain"/>
    <import-shared-library name="oracle.bpel.common"/>
    </imported-shared-libraries>
    Save and close the file.
    Restart the application server or the J2EE instance.
    After you make the JAR files available, deploy the adapter on the Oracle application server by using either the Oracle Application Server (Oracle AS) Application Server Control (ASC) or the Oracle admintool.jar file. Copy the adapter archive file (BRM_home/apps/brm_integrations/jca_adapter/OracleBRMJCA15Adapter.rar) from the installation directory to a location that is accessible to the adapter deployment tool. You can then open and deploy the archive file on your application server.
    After successful deployment, return the applications.xml file to its original settings and add the oracle.bpel.common codesource to the BRM Adapter oc4j-ra.xml file:
    Open the Oracle_home/j2ee/Instance/config/applications.xml configuration file for the J2EE instance.
    Remove the following oracle.bpel.common entry (shown in bold below):
    <imported-shared-libraries>
    <import-shared-library name="adf.oracle.domain"/>
    <import-shared-library name="oracle.bpel.common"/>
    </imported-shared-libraries>
    Save and close the file.
    Open the JCA Resource Adapter oc4j-ra.xml file from the Oracle_home/j2ee/Instance/application-deployments/default/BRMAdapterDeploymentName directory.
    Add the oracle.bpel.common entry (shown in bold below) to the oc4j-connector-factories section of the file:
    <oc4j-connector-factories...>
    <imported-shared-libraries>
    <import-shared-library name="oracle.bpel.common"/>
    </imported-shared-libraries>
    <oc4j-connector-factories>
    Save and close the file.
    Restart the application server or the J2EE instance.
    For more information about deploying the adapter, see your application server’s documentation.
    Connecting the adapter to BRM in Oracle AS
    You connect the adapter to the BRM software by creating connection pools and connection factories. As part of the adapter deployment, the application server creates oc4j-ra.xml from the packaged ra.xml. The ra.xml file is located in the Oracle_home/j2ee/Instance/connectors/AdapterDeploymentName/AdapterDeploymentName/META-INF directory. For example, Oracle_home/j2ee/home/connectors/BRMAdapter/BRMAdapter/META-INF/ra.xml.
    Use the resource adapter home page from the Oracle AS ASC page to create connection pools and connection factories.
    Create your connection pool by following the performance and tuning guidelines in Configuring Connection Pooling in OC4J in Oracle Containers for J2EE Resource Adapter Administrator's Guide. See download.oracle.com/docs/cd/B31017_01/web.1013/b28956/conncont.htm.
    Make sure you set the pool’s Maximum Connections parameter (maxConnections XML entity) equal to or greater than the Oracle BPEL process manager’s dspMaxThreads parameter. For more information, see Oracle BPEL Process Manager Performance Tuning in Oracle Application Server Performance Guide for 10g Release 3 (10.1.3.1.0) at download.oracle.com/docs/cd/B31017_01/core.1013/b28942/tuning_bpel.htm.
    Note To set up JCA Resource Adapter transaction management in BPEL, you must create a private connection pool and set its Inactive Connection Timeout property (inactivity-timeout XML entity) to 0. See About JCA Resource Adapter transaction management in BPEL for more information.
    Create as many connection factories as your system needs. For each connection factory, specify the following:
    The JNDI location for the connection factory.
    The connection pool to use.
    How to connect to BRM by using these entries:
    Entry
    Description
    ConnectionString
    Specify the protocol, host name, and port number for connecting to the BRM software. For example: ip Server1 12006.
    DBNumber
    Specify the database number for the BRM database. For example, enter 1 or 0.0.0.1 for database 0.0.0.1.
    InputValidation
    Specifies whether to validate the input XMLRecord:
    True — The adapter validates the input XMLRecord against the opcode schema.
    False — The adapter does not validate the input XMLRecord.
    The default is False.
    This overrides any other validation parameter specified in the WSDL file.
    OutputValidation
    Specifies whether to validate the output XMLRecord:
    True — The adapter validates the output XMLRecord against the opcode schema.
    False — The adapter does not validate the output XMLRecord.
    The default is False.
    This overrides any other validation parameter specified in the WSDL file.
    LoginType
    Specifies the authentication method:
    1 — The adapter logs in to BRM by using the specified login name and password.
    0 — The adapter logs in to BRM by using the specified service type and POID ID.
    The default is 1.
    UserName
    Specifies the login name the adapter uses for logging in to the BRM software.
    Note This entry is required only if LoginType is set to 1.
    Password
    Specify the password the adapter uses for logging in to the BRM software.
    Note This entry is required only if LoginType is set to 1.
    PoidID
    Specifies the POID ID. This entry should be set to 1.
    ServiceType
    Specifies the service the adapter uses to log in to the BRM software.
    The default is /service/pcm_client.
    You have successfully configured the adapter to connect to BRM.

    I need Fusion help creating a demo of BRM JCA Resource Adapter.
    I know BRM well but am clueless with Fusion.
    I am trying to figure out what Fusion products to download and install and how I manipulate the Fusion side to manipulate BRM.
    My BRM docs say:
    Installing the BRM JCA Resource Adapter ->
    Software requirements
    (yada yada install a bunch of BRM stuff I know how to do)
    The adapter must be deployed on a J2EE 1.4-compliant application server that has implemented the JCA 1.5 specification. The adapter runs only in a managed environment. (Does this imply some particular Fusion package?)
    (more yada yada about installing more BRM packages I know how to do)
    Deploying and configuring the BRM JCA Resource Adapter ->
    Overview of the BRM JCA Resource Adapter configuration procedure
    The procedure for setting up the BRM JCA Resource Adapter includes the following tasks:
    Installing the adapter on your BRM system, if you have not already done so. See Installing the BRM JCA Resource Adapter.
    Generating the schema files for the adapter. See Generating the schema files for your system. (links to some BRM commands np)
    Specifying how to construct XML tags. See Specifying the XML tags for extended fields. (links to an oob file included with directions on how to address BRM customizations np)
    Generating the WSDL files for the adapter. See Generating the WSDL files for your system. (links to an oob file with directions to configure. I could use some help if/when I get this far)
    The last two look pretty important but I haven't a clue. I pasted the text from the docs below.
    Deploying the adapter on your application server. See Deploying the BRM JCA Resource Adapter on an Oracle application server.
    Connecting the adapter to the BRM software. See Connecting the adapter to BRM in Oracle AS.
    Deploying the BRM JCA Resource Adapter on an Oracle application server
    The adapter is dependent on Java Archive (JAR) files to deploy properly. The following table lists the JAR files that the adapter requires from each application in your system.
    Application
    JAR files
    J2EE application server
    classes12.jar, connector15.jar, and jta.jar
    Oracle BPEL process
    bpm-infra.jar, orabpel-thirdparty.jar, orabpel.jar, and xmlparserv2.jar
    BRM J2EE Resource Adapter
    pcm.jar and pcmext.jar
    Apache
    xercesImpl.jar
    If you are deploying the adapter in a standalone Oracle Containers for Java EE (OC4J) instance, make sure these JAR files are available to the class loader that is loading the adapter.
    If you are deploying the adapter by using Oracle SOA Suite, these JAR files are available as part of the oracle.bpel.common code source. You import these libraries as follows:
    Open the Oracle_home/j2ee/Instance/config/applications.xml configuration file for the J2EE instance.
    Add the oracle.bpel.common entry (shown in bold below) to the imported-shared-libraries section of the file:
    <imported-shared-libraries>
    <import-shared-library name="adf.oracle.domain"/>
    <import-shared-library name="oracle.bpel.common"/>
    </imported-shared-libraries>
    Save and close the file.
    Restart the application server or the J2EE instance.
    After you make the JAR files available, deploy the adapter on the Oracle application server by using either the Oracle Application Server (Oracle AS) Application Server Control (ASC) or the Oracle admintool.jar file. Copy the adapter archive file (BRM_home/apps/brm_integrations/jca_adapter/OracleBRMJCA15Adapter.rar) from the installation directory to a location that is accessible to the adapter deployment tool. You can then open and deploy the archive file on your application server.
    After successful deployment, return the applications.xml file to its original settings and add the oracle.bpel.common codesource to the BRM Adapter oc4j-ra.xml file:
    Open the Oracle_home/j2ee/Instance/config/applications.xml configuration file for the J2EE instance.
    Remove the following oracle.bpel.common entry (shown in bold below):
    <imported-shared-libraries>
    <import-shared-library name="adf.oracle.domain"/>
    <import-shared-library name="oracle.bpel.common"/>
    </imported-shared-libraries>
    Save and close the file.
    Open the JCA Resource Adapter oc4j-ra.xml file from the Oracle_home/j2ee/Instance/application-deployments/default/BRMAdapterDeploymentName directory.
    Add the oracle.bpel.common entry (shown in bold below) to the oc4j-connector-factories section of the file:
    <oc4j-connector-factories...>
    <imported-shared-libraries>
    <import-shared-library name="oracle.bpel.common"/>
    </imported-shared-libraries>
    <oc4j-connector-factories>
    Save and close the file.
    Restart the application server or the J2EE instance.
    For more information about deploying the adapter, see your application server’s documentation.
    Connecting the adapter to BRM in Oracle AS
    You connect the adapter to the BRM software by creating connection pools and connection factories. As part of the adapter deployment, the application server creates oc4j-ra.xml from the packaged ra.xml. The ra.xml file is located in the Oracle_home/j2ee/Instance/connectors/AdapterDeploymentName/AdapterDeploymentName/META-INF directory. For example, Oracle_home/j2ee/home/connectors/BRMAdapter/BRMAdapter/META-INF/ra.xml.
    Use the resource adapter home page from the Oracle AS ASC page to create connection pools and connection factories.
    Create your connection pool by following the performance and tuning guidelines in Configuring Connection Pooling in OC4J in Oracle Containers for J2EE Resource Adapter Administrator's Guide. See download.oracle.com/docs/cd/B31017_01/web.1013/b28956/conncont.htm.
    Make sure you set the pool’s Maximum Connections parameter (maxConnections XML entity) equal to or greater than the Oracle BPEL process manager’s dspMaxThreads parameter. For more information, see Oracle BPEL Process Manager Performance Tuning in Oracle Application Server Performance Guide for 10g Release 3 (10.1.3.1.0) at download.oracle.com/docs/cd/B31017_01/core.1013/b28942/tuning_bpel.htm.
    Note To set up JCA Resource Adapter transaction management in BPEL, you must create a private connection pool and set its Inactive Connection Timeout property (inactivity-timeout XML entity) to 0. See About JCA Resource Adapter transaction management in BPEL for more information.
    Create as many connection factories as your system needs. For each connection factory, specify the following:
    The JNDI location for the connection factory.
    The connection pool to use.
    How to connect to BRM by using these entries:
    Entry
    Description
    ConnectionString
    Specify the protocol, host name, and port number for connecting to the BRM software. For example: ip Server1 12006.
    DBNumber
    Specify the database number for the BRM database. For example, enter 1 or 0.0.0.1 for database 0.0.0.1.
    InputValidation
    Specifies whether to validate the input XMLRecord:
    True — The adapter validates the input XMLRecord against the opcode schema.
    False — The adapter does not validate the input XMLRecord.
    The default is False.
    This overrides any other validation parameter specified in the WSDL file.
    OutputValidation
    Specifies whether to validate the output XMLRecord:
    True — The adapter validates the output XMLRecord against the opcode schema.
    False — The adapter does not validate the output XMLRecord.
    The default is False.
    This overrides any other validation parameter specified in the WSDL file.
    LoginType
    Specifies the authentication method:
    1 — The adapter logs in to BRM by using the specified login name and password.
    0 — The adapter logs in to BRM by using the specified service type and POID ID.
    The default is 1.
    UserName
    Specifies the login name the adapter uses for logging in to the BRM software.
    Note This entry is required only if LoginType is set to 1.
    Password
    Specify the password the adapter uses for logging in to the BRM software.
    Note This entry is required only if LoginType is set to 1.
    PoidID
    Specifies the POID ID. This entry should be set to 1.
    ServiceType
    Specifies the service the adapter uses to log in to the BRM software.
    The default is /service/pcm_client.
    You have successfully configured the adapter to connect to BRM.

  • Deploying BRM JCA on Weblogic 10.3

    We are trying to prototype invoking APIs through Webservices exposed by BRM JCA.
    In the Oracle BRM manual it is mentioned that certain Jars need to be present in order for BRM JCA to deploy successfully.
    1. J2EE application server
    classes12.jar, connector15.jar, and jta.jar
    2. Oracle BPEL process
    bpm-infra.jar, orabpel-thirdparty.jar, orabpel.jar, and xmlparserv2.jar
    3. Apache
    xercesImpl.jar
    We have only classes12.jar, jta.jar, xercesImpl.jar.
    My question is whether it is absolutely necessary for these jars to be present, and if so where can I find it.
    Right now we are getting Deployment error when we try to deploy BRM JCA on Weblogic 10.3
    <Dec 10, 2010 2:17:07 PM GMT+05:30> <Warning> <Connector> <BEA-190155> <Compliance checking/validation of the resource a
    dapter E:\BRM74Tools\JCA\jca_adapter\OracleBRMJCA15Adapter.rar resulted in the following warnings:
    The ra.xml <resourceadapter-class> class 'oracle.tip.adapter.brm.BRMResourceAdapter' should implement java.io.Serializab
    le but does not.>
    <Dec 10, 2010 2:17:07 PM GMT+05:30> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment req
    uest with ID '1291970826812' for task '0'. Error is: 'weblogic.application.ModuleException: [1] The ra.xml <connectionfa
    ctory-interface> class 'oracle.tip.adapter.api.OracleConnectionFactory' was not found in the resource adapter archive/ap
    plication.
    [2] The ra.xml <connectionfactory-impl-class> class 'oracle.tip.adapter.brm.BRMConnectionFactory' could not be loaded fr
    om the resource adapter archive/application because of the following error: java.lang.NoClassDefFoundError: oracle/tip/a
    dapter/api/OracleConnectionFactory'
    weblogic.application.ModuleException: [1] The ra.xml <connectionfactory-interface> class 'oracle.tip.adapter.api.OracleC
    onnectionFactory' was not found in the resource adapter archive/application.
    [2] The ra.xml <connectionfactory-impl-class> class 'oracle.tip.adapter.brm.BRMConnectionFactory' could not be loaded fr
    om the resource adapter archive/application because of the following error: java.lang.NoClassDefFoundError: oracle/tip/a
    dapter/api/OracleConnectionFactory
    at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:229)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
    Truncated. see log file for complete stacktrace
    >
    <Dec 10, 2010 2:17:07 PM GMT+05:30> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy ta
    sk for application 'OracleBRMJCA15Adapter'.>
    <Dec 10, 2010 2:17:07 PM GMT+05:30> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: [1] The ra.xml <connectionfactory-interface> class 'oracle.tip.adapter.api.OracleC
    onnectionFactory' was not found in the resource adapter archive/application.
    [2] The ra.xml <connectionfactory-impl-class> class 'oracle.tip.adapter.brm.BRMConnectionFactory' could not be loaded fr
    om the resource adapter archive/application because of the following error: java.lang.NoClassDefFoundError: oracle/tip/a
    dapter/api/OracleConnectionFactory
    at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:229)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
    Truncated. see log file for complete stacktrace
    >
    <Dec 10, 2010 2:17:07 PM GMT+05:30> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.app
    lication.ModuleException: [1] The ra.xml <connectionfactory-interface> class 'oracle.tip.adapter.api.OracleConnectionFac
    tory' was not found in the resource adapter archive/application.
    [2] The ra.xml <connectionfactory-impl-class> class 'oracle.tip.adapter.brm.BRMConnectionFactory' could not be loaded fr
    om the resource adapter archive/application because of the following error: java.lang.NoClassDefFoundError: oracle/tip/a
    dapter/api/OracleConnectionFactory
    at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:229)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1223)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperatio
    n.java:208)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:16
    0)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(Deploymen
    tReceiverCallbackDeliverer.java:171)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiv
    erCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCal
    lbackDeliverer.java:47)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >

    Hi jamavalom,
    I have exactly the same problem with deployment of JCA Adapter, except I collected all requested jar files, and put them in WEBLOGIC_CLASSPATH inside /wlserver_10.3/common/bin/commEnv.sh file, and afterward restarted the WebLogic server. Here are the contents of configuration *.xml files:
    ra.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <connector xmlns="http://java.sun.com/xml/ns/j2ee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd"
    version="1.5">
    <display-name>Oracle BRM Adapter</display-name>
    <vendor-name>Oracle CGBU</vendor-name>
    <eis-type>Oracle BRM</eis-type>
    <resourceadapter-version>1.0</resourceadapter-version>
    <resourceadapter>
    <resourceadapter-class>oracle.tip.adapter.brm.BRMResourceAdapter</resourceadapter-class>
    <outbound-resourceadapter>
    <connection-definition>
    <managedconnectionfactory-class>
    oracle.tip.adapter.brm.BRMManagedConnectionFactory
    </managedconnectionfactory-class>
    <!-- protocol, hostname and port -->
    <config-property>
    <config-property-name>ConnectionString</config-property-name>
    <config-property-type>java.lang.String</config-property-type>
    <config-property-value>ip hostname 12007</config-property-value>
    </config-property>
    <config-property>
    <config-property-name>PoidID</config-property-name>
    <config-property-type>java.lang.Long</config-property-type>
    <config-property-value>1</config-property-value>
    </config-property>
    <config-property>
    <config-property-name>ServiceType</config-property-name>
    <config-property-type>java.lang.String</config-property-type>
    <config-property-value>/service/pcm_client</config-property-value>
    </config-property>
    <!-- Login type 1 - Authentication by username/password,
    0 - authentication by service and poid id0 -->
    <config-property>
    <config-property-name>LoginType</config-property-name>
    <config-property-type>java.lang.Integer</config-property-type>
    <config-property-value>1</config-property-value>
    </config-property>
         <!-- ConnectionPoolMaxsize - Pool Max size used by pfc.jar -->
    <config-property>
    <config-property-name>ConnectionPoolMaxsize</config-property-name>
    <config-property-type>java.lang.Integer</config-property-type>
    <config-property-value>50</config-property-value>
    </config-property>
         <!-- ConnectionPoolMinsize - Pool Mn size used by pfc.jar -->
    <config-property>
    <config-property-name>ConnectionPoolMinsize</config-property-name>
    <config-property-type>java.lang.Integer</config-property-type>
    <config-property-value>25</config-property-value>
    </config-property>
    <!-- UserName and Password for Login type 1 -->
    <config-property>
    <config-property-name>UserName</config-property-name>
    <config-property-type>java.lang.String</config-property-type>
    <config-property-value>root.0.0.0.1</config-property-value>
    </config-property>
    <config-property>
    <config-property-name>Password</config-property-name>
    <config-property-type>java.lang.String</config-property-type>
    <config-property-value>&amp;aes|08|0D5E11BFDD97D2769D9B0DBFBD1BBF7E5D40C305EDF3D77DF111AAB8F781E92122</config-property-value>
    </config-property>
    <!-- Input and Output schema validation-->
    <config-property>
    <config-property-name>InputValidation</config-property-name>
    <config-property-type>java.lang.Boolean</config-property-type>
    <config-property-value>false</config-property-value>
    </config-property>
    <config-property>
    <config-property-name>OutputValidation</config-property-name>
    <config-property-type>java.lang.Boolean</config-property-type>
    <config-property-value>false</config-property-value>
    </config-property>
         <!-- MultiDB - true - Transaction opened on the incoming database
                   - false- Transaction opened on default DB -->
    <config-property>
    <config-property-name>MultiDB</config-property-name>
    <config-property-type>java.lang.Boolean</config-property-type>
    <config-property-value>false</config-property-value>
    </config-property>
         <!-- AverageOpcodeCount - Determines number of managed connections
                        created on the fly. Its the average number
                        of opcodes executed per thread -->
    <config-property>
    <config-property-name>AverageOpcodeCount</config-property-name>
    <config-property-type>java.lang.Integer</config-property-type>
    <config-property-value>5</config-property-value>
    </config-property>
    <connectionfactory-interface>
    oracle.tip.adapter.api.OracleConnectionFactory
    </connectionfactory-interface>
    <connectionfactory-impl-class>
    oracle.tip.adapter.brm.BRMConnectionFactory
    </connectionfactory-impl-class>
    <connection-interface>
    oracle.tip.adapter.brm.IBRMConnection
    </connection-interface>
    <connection-impl-class>
    oracle.tip.adapter.brm.BRMConnection
    </connection-impl-class>
    </connection-definition>
    <transaction-support>XATransaction</transaction-support>
    <authentication-mechanism>
    <authentication-mechanism-type>
    BasicPassword
    </authentication-mechanism-type>
    <credential-interface>
    javax.resource.spi.security.PasswordCredential
    </credential-interface>
    </authentication-mechanism>
    <reauthentication-support>false</reauthentication-support>
    </outbound-resourceadapter>
    </resourceadapter>
    </connector>
    weblogic-ra.xml:
    <weblogic-connector xmlns="http://www.bea.com/ns/weblogic/weblogic-connector" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-connector http://www.bea.com/ns/weblogic/weblogic-connector/1.0/weblogic-connector.xsd">
    <enable-access-outside-app>true</enable-access-outside-app>
    <enable-global-access-to-classes>true</enable-global-access-to-classes>
    <outbound-resource-adapter>
    <connection-definition-group>
    <connection-factory-interface>oracle.tip.adapter.api.OracleConnectionFactory</connection-factory-interface>
    <connection-instance>
    <jndi-name>eis/BRM</jndi-name>
    <connection-properties>
    <logging>
         <log-filename>eisBRM.log</log-filename>
                                  <logging-enabled>true</logging-enabled>
                                  <rotation-type>bySize</rotation-type>
                                  <number-of-files-limited>true</number-of-files-limited>
                                  <file-count>3</file-count>
                                  <file-size-limit>100</file-size-limit>
                                  <rotate-log-on-startup>true</rotate-log-on-startup>
                                  <log-file-rotation-dir>c:/mylogs</log-file-rotation-dir>
                                  <rotation-time>10:00</rotation-time>
                                  <file-time-span>24</file-time-span>
                             </logging>
                             <properties>
                                  <property>     
                   <name>ConnectionString</name>
                   <value>ip blrhpdv3.idc.oracle.com 12011</value>
                   </property>
                   <!-- Database number, Poid ID0 and Service type -->
                   <property>
                   <name>PoidID</name>
                   <value>1</value>
                   </property>
                   <property>
                   <name>ServiceType</name>
                   <value>/service/pcm_client</value>
                   </property>
                   <!-- Login type 1 - Authentication by username/password,
                   0 - authentication by service and poid id0 -->
                   <property>
                   <name>LoginType</name>
                   <value>1</value>
                   </property>
                   <property>
                   <name>ConnectionPoolMaxsize</name>
                   <value>20</value>
                   </property>
                   <property>
                   <name>ConnectionPoolMinsize</name>
                   <value>10</value>
                   </property>
                   <!-- UserName and Password for Login type 1 -->
                   <property>
                   <name>UserName</name>
                   <value>root.0.0.0.1</value>
                   </property>
                   <property>
                   <name>Password</name>
                   <value>&amp;aes|08|0D5E11BFDD97D2769D9B0DBFBD1BBF7E5D40C305EDF3D77DF111AAB8F781E92122</value>
                   </property>
                   <!-- Input and Output schema validation-->
                   <property>
                   <name>InputValidation</name>
                   <value>false</value>
                   </property>
                   <property>
                   <name>OutputValidation</name>
                   <value>false</value>
                   </property>
                   <property>
                   <name>MultiDB</name>
                   <value>false</value>
                   </property>
                   <!-- The AverageOpcodeCount parameter specifies the number of Opcode calls in a Thread -->
                   <property>
                   <name>AverageOpcodeCount</name>
                   <value>1</value>
                   </property>
                        </properties>
                        </connection-properties>
                        </connection-instance>
                   </connection-definition-group>
              </outbound-resource-adapter>
    </weblogic-connector>
    Thank you in advance for help,
    BR,
    Mario

  • Consuming BRM Webservice in Web Dynpro on NW 7.3

    Hello,
    I've got a big problem comsuming a Business Rules Management (BRM) Webservice (Netweaver 7.3) in my Web Dynpro app.
    In WSNavigator the webservice is running fine and fully functional.
    I created a custom controller by using the "apply template" function and selecting the mentioned webservice, which I have imported before.
    The following methods were created within the custom controller: executeInvokeRules() and initRequest_InvokeRules() .
    When I just execute the webservice the error, that there are mandatory input parameters occures. That's OK!
    But when I want to set the values to the attribtues in my custom controller, the following error occures:
    com.sap.tc.webdynpro.progmodel.context.ContextModelException: Node(ConfigureAngebot/PreisfindungRController.Request_InvokeRules.RequestAufpreisfindung.Aufpreise_1.AufpreiseType_1.Preise_1, class=de.mycomp.mydevision.bau.angebot.admin.wd.wd.comp.configureangebot.wdp.IPublicPreisfindungRController$IPreise_1Node): <modelObject class="de.mycomp.mydevision.bau.angebot.admin.wd.wd.models.preisfindungr.AufpreiseType_Sequence1__"><target roleName="Preise"></target></modelObject> delivered no object for supplying relation role Preise, but the relation cardinality requires one
      at com.sap.tc.webdynpro.progmodel.context.DataNode.supplyRelation(DataNode.java:229)
    Any help would be apprecited.
    Thanks ahead,
    Bernd

    Hello Bernd,
    this error is a singleton characteristic issue. You get this error if you try to use singleton context node without setting lead selection before. If you are using singleton context nodes and want to set attributes, you have to work like this:
    ISingletonNode singletonNode = wdContext.createAndAddSingletonNode();
    wdContext.nodeSingletonParent.setLeadSelection(singletonParent.index());
    wdContext.currentSingletonParent.setExampleValue("Test");
    For Lead selection you can also use constant IWDNode.LEAD_SELECTION
    BR , Alex

Maybe you are looking for

  • Using Mac OS 10.7.2 in Photoshop updated 12.0.4 I can not change Print Preferences

    I updated my Mac to OS 10.7.2 and I also updated my Adobe to 12.0.4, when I open Adobe Photoshop, open file, make changes, when I go to print, it defaults to 11 in X 8.5 in and when I click print preferance, nothing happens.. it will not allow me to

  • "Writer" Module not working in web service mode

    Hi, I designed a experiment to do a prediction work and automatically write the result to AzureSqlServer. I published  a web service from the experiment to trigger the prediction procedure, it worked very well until February. But from then on, the da

  • How to transfer mail.app to new MBP?

    Is there a way I can transfer my Mail.app settings and messages to my new MBP without having to migrate all of my data to the new machine? Looking fwd to your responses.

  • TS3988 iCloud set up Query

    if two phones are linked to the same account...and set up under icloud... how can i uninstall one of the phones so that both phones stop picking up each other's phone contacts?

  • [iPhone] Can't play multiple compressed sounds, seems to block!

    I'm writing an app that needs to play a variety of audio samples of different lengths back to back, but only one at a time. The system I came up with works great when using WAV files or whenever running on the simulator no matter what audio type, but