Doubts about configurate services with JBI

Hi people,
I have been looking for a way to develop a wizard for configuration of services in different ESBs from my web application.
I took a look at some presentations (like http://80.69.93.183/sun-evenementen/pdf/jbi_openesb.pdf and http://mediacast.sun.com/users/~armin/media/SunTechDays2007_OpenESB.pdf), and I would like ask you about possibilities to configure services in a ESB using JBI.
What I really want to do is allow that my web application connects to some ESBs to configure services into them. It's like to have the web interface that some of them provide to make the configuration from my web application.
I have been talking about this with some guys and two possibilities that they gave me are:
1. To develop everything into the web application and send the information through JMX.
2. To develop a generator of XML content (in memory) and send it the ESB, where it would has another implementation made by me, like a module (one of the guys said me that this could be a JBI Service Engine), which would receive the XML content generated by the web application.
Using the first one possibility, I would have all solution into my application and developing the other one, I would have one implementation to each ESB that I want to connect to if it wouldn't be done with JBI (I think.. right? Because it seams that it would be the same if I do it with JBI).
One guy told me that the second one would be the best, because, until he knows (based on the PoCs (proof of concept) he made, with JBossESB, Mule and WebSphere ESB), some of the ESBs he tested require some manual configuration to publish the services to be accessed through the ESB. He didn't do anything with JBI and didn't know anything about this.
Another thing is that if I deploy only once a JBI Service Engine (SE), I can do the configuration of every service I want to publish in the ESB through this SE. In other words, I won't need to ask to the admin of ESB do the configuration to me (or do it through the web interface of ESB).
Please, does anybody know if all the ESBs that support JBI give an interface to another application connects to them to configures services?
I thank you in advance for any information!
Regards,
Luiz

Similar Messages

Doubt about Bulk Collect with LIMIT

Hi
I have a Doubt about Bulk collect , When is done Commit
I Get a example in PSOUG
http://psoug.org/reference/array_processing.html
CREATE TABLE servers2 AS
SELECT *
FROM servers
WHERE 1=2;
DECLARE
CURSOR s_cur IS
SELECT *
FROM servers;
TYPE fetch_array IS TABLE OF s_cur%ROWTYPE;
s_array fetch_array;
BEGIN
OPEN s_cur;
LOOP
    FETCH s_cur BULK COLLECT INTO s_array LIMIT 1000;
    FORALL i IN 1..s_array.COUNT
    INSERT INTO servers2 VALUES s_array(i);
    EXIT WHEN s_cur%NOTFOUND;
END LOOP;
CLOSE s_cur;
COMMIT;
END;If my table Servers have 3 000 000 records , when is done commit ? when insert all records ?
could crash redo log ?
using 9.2.08

muttleychess wrote:
If my table Servers have 3 000 000 records , when is done commit ? Commit point has nothing to do with how many rows you process. It is purely business driven. Your code implements some business transaction, right? So if you commit before whole trancaction (from business standpoint) is complete other sessions will already see changes that are (from business standpoint) incomplete. Also, what if rest of trancaction (from business standpoint) fails?
SY.

Doubts about RAC infraestructure with one disk array

Hello everybody,
I'm writing to you because we have a doubt about the correct infrastructure to implement RAC.
Please, let me first explain the current design we are using for Oracle DB storage. Currently we are running several standalone instances in several servers, all of them connected to a SAN disk storage array. As we know this is a single point of failure we have redundant controlfiles, archiveds and redos both in the array and in the internal disk of each server, so in case array completely fails we “just” need to recover nightly cold backup, apply archs and redos and everything it's ok. This can be done because we have standalone instances and we can assume this 1 hour downtime.
Now we want to use these servers and this array to implement a RAC solution and we know this array is our single point of failure and wonder if it's possible to have a multinode RAC solution (not RAC One Node) with redundant controlfiles/archs/redos in internal disks. Is it possible to have each node writing full RAC controlfiles/archs/redos in internal disks and apply these files consistently when the ASM filesystem used for RAC is restores (i.e. with a softlink in an internal disk and using just one node)? Or maybe the recommended solution is to have a second array to avoid this single point of failure?
Thanks a lot!

cssl wrote:
Or maybe the recommended solution is to have a second array to avoid this single point of failure?Correct. This is the proper solution.
In this case you can also decide to simply use striping on both arrays, then mirror array1's data onto array2 using ASM redundancy options.
Also keep in mind that redundancy is also need for the connectivity. So you need at least 2 switches to connect to both arrays, and dual HBA ports on each server, with 2 fibres running, one to each switch. You will need multipath driver s/w on the server to deal with the multiple I/O paths to the same storage LUNs.
Likewise you need to repeat this for your Interconnect. 2 private switches, 2 private NICs on each server that are bonded. Then connect these 2 NICs to the 2 switches, one NIC per switch.
Also do not forget spares. Spare switches (one each for storage and Interconnect). Spare cables - fibre and whatever is used for the Interconnect.
Bottom line - not a cheap solution to have full redundancy. What can be done is to combine the storage connection/protocol layer with the Interconnect layer and run both over the same architecture. Oracle's Database Machine and Exadata Storage Servers do this. You can run your storage protocol (e.g. SRP) and your Interconnect protocol (TCP or RDS) over the same 40Gb Infiniband infrastructure.
Thus only 2 Infiniband switches are needed for redundancy, plus 1 spare. With each server running a dual port HCA and a cable to each of these 2 switches.

UCCX - 8.0.2 - Doubt about critical services

Hi Guys,
About the Services UCCX in Control Center, except: Cisco Unified CCX Engine, Cisco Unified CCX Database service (many criticals). Are There anothers services considered many critical to UCCX work?
System Services
Cisco Unified CCX SNMP Java Adapter
Cisco Unified CCX Perfmon Counter Service
Cisco Unified CCX DB Perfmon Counter Service
Cisco Unified CCX Cluster View Daemon
Cisco Unified CCX Engine
Cisco Unified CCX Voice Subagent
Admin Services
Cisco Unified CCX Serviceability
Cisco Unified CCX Administration
DB Services
Cisco Unified CCX Database service.
Desktop Services
Cisco Desktop Recording and Playback Service
Cisco Desktop VoIP Monitor Service
Cisco Desktop LDAP Monitor Service
Cisco Desktop Sync Service
Cisco Desktop Call/Chat Service
Cisco Desktop Agent E-Mail Service
Cisco Desktop Browser and IP Phone Agent Service
Cisco Desktop License and Resource Manager Service
Cisco Desktop Enterprise Service
Cisco Desktop Recording and Statistics Service
Thanks,
Wilson

Hi,
You will have to first define the phrase: "for UCCX to work."
For example:
If all you care about is pinging the server then, no, none of those services are critical.
If you want UCCX to only answer inbound calls, then a certain subset of the services are critical.
If you want UCCX to deliver calls to Agents, then add a few more services.
If you need HA, then add another.
If you need Outbound, or DB integration, call recording, silent monitoring, or e-mail, etc, you'll add more services to the list.
To learn about the services, you can read the UCCX SRND, the Serviceability Guide, and then check out the Cisco Live presentation: BRKCCT-3005
Anthony Holloway
Please use the star ratings to help drive great content to the top of searches.

Doubt about Agent Inbox with ERMS and NON-ERMS

Hi All.
We have configured both ERMS and NON-ERMS email receiving (to make some tests) and we verify that only the workitem generated by the NON-ERMS workflow (WS14000164) is shown in the IC Web Client Inbox. The workitem generated by the ERMS workflow (WS00200001) is shown only in the SBWP transaction. Is this right???
We believe that our agent inbox configurations are correct, because it is working fine for NON-ERMS emails.
There is some trick to make the generated ERMS workitens be shown in the IC Web Client Inbox?
Thanks in advance!!!

Hi Julio,
You will NOT be able to get the workitems created by the standard ERMS wokflow (WS00200001) into your inbox, because SAP's assumption is that ERMS precisely replaces manual inbox assignment work by some automation (Response Management).
Even if you add the ERMS task 207914 in transaction CRMC_IC_AUICOMM, this configuration will be made inactive by the workitem search-engine. You can observe this in method CL_CRM_IC_AUI_WI->IF_GENIL_SO_HANDLER~GET_LIST, around line 210:
read table lt_wflows with key object = co_erms_email_task into ls_wflows.
if ls_wflows is not initial.
delete table lt_wflows with table key object = co_erms_email_task.
endif.
If you still want to see ERMS WIs in your inbox, make a copy of WF WS00200001; in copy, replace task 207914 with your own one, that you add in trx CRMC_IC_AUICOMM. Deactivate triggering event of WF WS00200001; activate triggering event of your own one. No changes in SO28 necessary.
But you may then think about what should happen when one wants to postprocess an ERMS WI displayed in inbox; because some ERMS processing may already have taken place: incoming e-mail may already have been linked automatically to an existing service ticket. You should then support easy navigation to that ticket, and forbid e-mail is linked again manually.
Hope this makes topic clearer
Kind regards
Walter

Doubt about Web Service Client

Hi,
I'm triyng consuming a WSDL file. When I create a Web Service Client with the URL of the WSDL, the compilation shows this message:
init:
wscompile-init:
Created dir: C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\classes
Created dir: C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc
IISelector-client-wscompile:
Copying 1 file to C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\wsdl
advertencia: Procesando la operación "GeneraTurno" que no se ajusta a WS-I con el estilo RPC y la codificación SOAP
advertencia: Procesando la operación "ActivaTurno" que no se ajusta a WS-I con el estilo RPC y la codificación SOAP
advertencia: Procesando la operación "EliminaTurno" que no se ajusta a WS-I con el estilo RPC y la codificación SOAP
advertencia: Procesando la operación "DevOcupacion" que no se ajusta a WS-I con el estilo RPC y la codificación SOAP
advertencia: Procesando la operación "DevTurnosADesp" que no se ajusta a WS-I con el estilo RPC y la codificación SOAP
advertencia: Procesando la operación "Helloword" que no se ajusta a WS-I con el estilo RPC y la codificación SOAP
advertencia: Procesando la operación "DevElementosDigiturno" que no se ajusta a WS-I con el estilo RPC y la codificación SOAP
BUILD SUCCESSFUL (total time: 3 seconds)
What does it mean?, and how can I solve it?
Thanks in advance.

When I build the project shows this warnings:
init:
deps-jar:
wscompile-init:
IISelector-client-wscompile:
web-service-client-generate:
Created dir: C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\empty
Compiling 63 source files to C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\classes
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_ActivaTurno_RequestStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_ActivaTurno_RequestStruct_SOAPBuilder.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_ActivaTurno_RequestStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_ActivaTurno_ResponseStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_ActivaTurno_ResponseStruct_SOAPBuilder.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_ActivaTurno_ResponseStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevElementosDigiturno_RequestStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevElementosDigiturno_RequestStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevElementosDigiturno_ResponseStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevElementosDigiturno_ResponseStruct_SOAPBuilder.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevElementosDigiturno_ResponseStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevOcupacion_RequestStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevOcupacion_RequestStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevOcupacion_ResponseStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevOcupacion_ResponseStruct_SOAPBuilder.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevOcupacion_ResponseStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevTurnosADesp_RequestStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevTurnosADesp_RequestStruct_SOAPBuilder.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevTurnosADesp_RequestStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevTurnosADesp_ResponseStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevTurnosADesp_ResponseStruct_SOAPBuilder.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevTurnosADesp_ResponseStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_EliminaTurno_RequestStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_EliminaTurno_RequestStruct_SOAPBuilder.java:3: warning: unmappable character for encoding UTF-8
62 warnings

Doubt about applet communicating with the SIM

Greetings,
I have this doubt: I am developing a web site which contains a java applet. The web site is going to be available at some web server. The web site is going to be accessed by mobile phones. The idea is that, somehow, the applet communicates with the mobile phone and extract info from the SIM Card for authentication. I still wondering if it is possible and the possible drawbacks or alternatives.
Thank you in advance,
Fernando

Hi,
you definitely have to sign your applet to do that.
Check in the forum "Security -> Signed applet". You'll find the information you need to sign an applet.
For example check at: http://forum.java.sun.com/thread.jsp?forum=63&thread=174214

Doubt about actions.xml with actions and roles

Hi all,
we are using a file like actions.xml for use them in Web Dynpro applications describing actions like:
Is it possible to describe GROUPs assigning roles to them in the same XML instead of doing this using the useradmin application? We need to describe the roles in the XML because we are using around 25 ROLEs and 15 GROUPs.
We appreciate if you can show us the complete description with an example for defining those GROUPs in the XML with all the tags and properties neccesary.
Thanks in advance.
Raú

This feature is one of the hidden features SAP has for deploying stuff to NW. I'm sure there is a way for that, but its not documented, as the role extension is also not documented. I don't know why SAP is hidding this extremly useful features to normal developers. Especially for product development they are so usefull.
Did you know, that its possible to deploy database content (not just tables!) with a special DC and an XML file in a special format? Just another example of hidden features in SAP Netweaver.

Doubt about abap dynamic with performs.

Good Morning Gurus.
1-I have the tables of price in internal table ( t_a530 , T_a951 ... etc ).
2- I need filter data by field datbi and datab.
3-Can I create a perform to pass a table and after pass other table with other format to taht same perform ?
4-It abap dynamic.
5-II do not want to create several performs because I can make only one (with my logic to all tables)
Can you help me?
Thanks.

The program is already doing this except:
    where DATBI => sy-datum
         and DATAB <= sy-datum.
in my program is:
    where DATBI => sy-datum
if I change it then dont select duplicate matnrs?
because today my problem is it:
He slects all before sy-datum then if the material has 3 entries he show all.
And I need the most current only.

Doubts about use of REPORTS_SERVERMAP with Forms11g HA

Hi,
I'm configuring a Linux 64bits Forms/Reports 11g HA environment, the point is that i have two nodes, each one with its Forms and Reports servers, let's say FormsA and ReportsA for the first node and FormsB and ReportsB for the seconde node.
i want FormsA to be able to call reports from ReportsB and FormsB to be able to call reports from ReportsA.
I've been reading about REPORT_SERVERMAP
http://docs.oracle.com/cd/E12839_01/bi.1111/b32121/pbr_conf003.htm#autoId5
But i have some doubts about its use:
1. I will not use a shared cluster file system or any way of cache solution, i will only have my rdf files on each node, and i'm wondering if just by configuring this parameter i will be able to get the effect mentioned above ??
2. The link provided says "Using RUN_REPORT_OBJECT. If the call specifies a Reports Server cluster name instead of a Reports Server name, the REPORTS_SERVERMAP environment variable must be set in the Oracle Forms Services default.env file"
In fact i'm using RUN_REPORT_OBJECT but
what is the Reports Server cluster name ?? and where do i find that name ??
3. Is this configuration well defined:
REPORTS_SERVERMAP=clusterReports:ReportsA;clusterReports:ReportsB
4. At forms applications when using RUN_REPORT_OBJECT, can i assume that the report server name will be the cluster name specified at the REPORTS_SERVERMAP ??
5. Which files should i modify rwservlet.properties or default.env ??
Hope you can help me :)
Regards
Carlos

Hi,
1. I will not use a shared cluster file system or any way of cache solution, i will only have my rdf files on each node, and i'm wondering if just by configuring this parameter i will be able to get the effect mentioned above ??
--> In such case what could go wrong is
Suppose Run_report_object executed jobs successfully to ReportsA
But web.show_document command for getjobid failed ( as ReportsA went down by this time)
--> You will not get the output shown ( though job was successful)
If shared cache was enabled, then Even if ReportsA is down, other cluster member ( say ReportsB)
will respond back to web.show_document.
Point 2,
--> Under HA is it highly recommended to use web.show_document ( a servlet call) to execute reports. This is to help use all HA features at the HTTP , Webcache or load balancer level.
However if there is migrated code or Run_report_object is must, then the recommendations as you see in the pointed document is must.
REPORTS_SERVERMAP setting needs to be configured in rwservlet.properties file and also in default.env Forms configuration file to map the Reports Server cluster name to the Reports Server running on the mid-tier where the Load Balancer forwarded the report request.
For example FormsA, ReportsA, cluster name say rep_cluster
default.env file
REPORTS_SERVERMAP=rep_cluster:ReportsA
Where "rep_cluster" is the Reports Server cluster name and "ReportsA" is the name of the Reports Server running on the same machine as FormsA
rwservlet.properties file
<reports_servermap>rep_cluster:ReportsA</reports_servermap>
At default.env this is not a valid entry
REPORTS_SERVERMAP=clusterReports:ReportsA;clusterReports:ReportsB
what is the Reports Server cluster name ?? and where do i find that name ??
--> This is created via EM on the report server side.
Would recommend to refer following documents at the myoracle support repository
How to Setup Reports HA (High Availability - Clusters) in Reports 11g [ID 853436.1]
REP-52251 and REP-56033 Errors When Calling Reports From Forms With RUN_REPORT_OBJECT Against a Reports Cluster in 11g. [ID 1074804.1]
Thanks

Doubt about preferred or available service.

I have a doubt about preferred or available service.
I have a Oracle RAC with 3 nodes.
I created a service GL, but I didn't setup available instance, only preferred instances with 2 instances (PROD1,PROD2)
srvctl add service -d PROD -s GL -r PROD1,PROD2
My doubt is:
If PROD1 instance dies, I would like to know if rac01 is restored automatically on rac02.
Anybody can help me?
Thanks in advance.
Leonardo.

There are different ways for configure failover... below just an example :
mydatabase.us.com =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.100.124.91)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.100.124.93)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.100.124.95)(PORT = 1521))
(LOAD_BALANCE = yes)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = mydatabase.us.com)
(FAILOVER_MODE =
(TYPE = SELECT)
(METHOD = BASIC)
(RETRIES = 180)
(DELAY = 5)
Or... read the document :
http://docs.oracle.com/cd/B19306_01/network.102/b14213/tnsnames.htm
Regards,
Alex Alvarenga.

HT1349 I want to know about the service of my computer with a serial number CO2GG9LCDJWT

I want to know about the service of my computer with a serial number CO2GG9LCDJWT. As I recall, I bought the service for three years...

Are you perhaps trying to reach Apple Support?
We are all users here, just like you.
Contact Apple Support here:
http://www.apple.com/support/contact/

Doubt about upgration in the service pack

Hi experts,
I have one doubt about upgration of the service packs.How to upgrate one sevice pack to another one . Is there any process to this.
please let me know the things.
Regards
babu

HI,
There is a procedure to upgrade , first you need to update the kernal,ABAP stack,patches,javastack.
see the below links
SAP installation guide
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283
Post Installation steps for activating Adobe Document Services in SAP XI NW 2004S -/people/sravya.talanki2/blog/2006/11/15/post-installation-steps-for-activating-adobe-document-services-in-sap-xi-nw-2004s
Regards
Chilla

Doubt about diference between SAPconsole and SAPmobile

Hello,
     I have been many doubts about diference between sapconsole and sapmobile, if anyone could help me I appreciate.
1) I have ECC6 instaled, the SAP Mobile is compatible with ECC6 or I need of Netweaver Instaled ?
2) If Possible to Install Sap Mobile in ECC6 , I have to Buy a license of sap mobile ?
3) in any product instaled Windows CE have possible to install sap mobile ?
4) In sap console what is the requirement for to do this configuration?
I Anybody to know about this informations please explain for me ?
Thanks

My apology,
    The Basic Diference beteween SAPConsole and SAPMobile is :
SAPConsole ==>
1 ) Don' t need a new Hardaware for to configurate
2 ) Only need a Machine with the IIS service installed
3 ) The SAPGui CD content the SAPCOnsole.exe for configuration
4 ) The equipment like Pocket and datacolletor has been to configurated in a Network( but if to have a entrance in the SAPGUi indicate a SAProuter in another factory is possible to have acesses.. ) is a mandatory. Cause the SAPCOnsle folow the SAPGUI entrances and need a LAN or a WAN configurated.
Advantage
simple to congurated and chip.
Easy to create to new window cause the SAPConsole only plubish this window in Browser.
Disadvantage
Need a lincense for each Poket or Datacolletor, wherever the equipment you will use.
Doesn't have a Database using through Browser (IE6 or IE7) this way , during the processes lost network you go to lost the information not saved.
SAPMobile
1 ) Need the a good Machine with a instance of SAP configurate
2 ) Have to found the EXE in the MarketPlace
3 ) is not publish, and yes a client with the database configurate in equipment
4 ) The equipment like Pocket and datacolletor has been to configurated in a Network
Advantage
Need only one SAP License, doesn't metter how many equipment in use you have.
As the SAPMobile has a Database in the client , if you lost the network it goes to save in the local database and when the network come back , it will to synchronize. This way you don't need to work online every moment, you get to synchronize after.
Disadvantage
You profit in license is your lost in the Machine cause the price of Machine is expensive.
is configurate only in windows Mobile.
The window only can be create for a Developement and not in the SAP, have been created in windows Mobile.
A tip, the both is good but you can do a simple mathematics.
In the SAPConsole how much money you go to spend is the least of the Machine s Price.
If yes confurate the SAPConsole , if not configurate the SAPMobile

Starting out with JBI

In an attempt to introduce myself to JBI, I looked for something relevant to my field (health) and found the video created by Raghunadh Teegavarapu at http://wiki.open-esb.java.net/attach/HL7BC/HL7BCInboundOriginalACKDemo.wmv
As I tried to follow the process exactly, I found my Netbeans 6.1 install was missing a few plugins, so I added
org-netbeans-modules-encoder-hl7-aip.nbm
org-netbeans-modules-encoder-ui-basic.nbm
org-netbeans-modules-wsdlextensions-hl7.nbm
com-sun-encoder-hl7.nbm
com-sun-encoder.nbm
And applied the following .jar to my local Glassfish install
hl7bc.jar
Everything was looking like I was good at following a video, and getting it all right despite slight differences between the Netbeans build shown and my 6.1 install, until I tried to deploy. At that stage I hit the wall with the result shown below. Can anyone offer any advice as to what I am missing?
Thanks
Ianto
---Details from build.xml (run) window---
pre-init:
init-private:
init-userdir:
init-user:
init-project:
do-init:
post-init:
init-check:
init:
init-deploy:
deps-jar:
init:
Building jar: D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_Demo\build\SEDeployment.jar
dist_se:
Expanding: D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_Demo\build\SEDeployment.jar into
D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA\src\jbiServiceUnits\HL7_Original_ACK_Demo
Moving 1 file to D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA\src\jbiServiceUnits\HL7_Original_ACK_Demo
Moving 1 file to D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA\src\jbiServiceUnits\META-INF\HL7_Original_ACK_Demo
deps-javaee-jar:
jbi-build:
Building jar: D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA\build\BCDeployment.jar
Validating CompApp project...
Resolving connections...
Writing connections out to connections.xml...
Generating Service Assembly jbi.xml...
Merging component projects' catalogs...
Generating Binding Component Service Units...
creating sun-file-binding.jar
creating sun-hl7-binding.jar
Creating/Updating CASA...
Filtering Java EE Endpoints...
Deleting: D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA\build\BCDeployment.jar
Building jar: D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA\dist\HL7_Original_ACK_DemoCA.zip
run-jbi-deploy:
[deploy-service-assembly]
Deploying a service assembly...
host=localhost
port=4848
file=D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA/dist/HL7_Original_ACK_DemoCA.zip
[start-service-assembly]
Starting a service assembly...
host=localhost
port=4848
name=HL7_Original_ACK_DemoCA
ERROR: Successful execution of Start: HL7_Original_ACK_DemoCA
WARNING: (JBIMA0405) Start of service assembly HL7_Original_ACK_DemoCA succeeded partially; some service units failed to start.
* Component: sun-hl7-binding
ERROR: (HL7BC_START_1) Error starting service unit due to: null
* Component: sun-bpel-engine
INFO: (JBIMA0409) Lifecycle operation start succeeded for Service Unit HL7_Original_ACK_DemoCA-HL7_Original_ACK_Demo.
* Component: sun-file-binding
INFO: (JBIMA0409) Lifecycle operation start succeeded for Service Unit HL7_Original_ACK_DemoCA-sun-file-binding.
Cleaning up...
[stop-service-assembly]
Stopping a service assembly...
host=localhost
port=4848
name=HL7_Original_ACK_DemoCA
[shutdown-service-assembly]
Shutting down a service assembly...
host=localhost
port=4848
name=HL7_Original_ACK_DemoCA
[undeploy-service-assembly]
Undeploying a service assembly...
host=localhost
port=4848
name=HL7_Original_ACK_DemoCA
D:\JavaDevelopment\XXExperimental\HL7_Original_ACK_DemoCA\nbproject\build-impl.xml:213: Start failure.
BUILD FAILED (total time: 8 seconds)

Here are details from the server.log at time of attempted deployment:
[#|2008-06-26T07:54:49.125+1000|INFO|sun-appserver9.1|com.sun.jbi.framework|_ThreadID=30;_ThreadName=JBI-Ready-Sync;|JBIFW0012: JBI framework startup complete.|#]
[#|2008-06-26T07:55:27.640+1000|INFO|sun-appserver9.1|com.sun.jbi.management|_ThreadID=31;_ThreadName=httpWorkerThread-4848-0;|Deploying service assembly HL7_Original_ACK_DemoCA to target server.|#]
[#|2008-06-26T07:55:27.968+1000|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=32;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;_RequestID=e8711635-8e71-471f-a65f-880d66bc1fc7;|Cannot find CatalogManager.properties|#]
[#|2008-06-26T07:55:28.000+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=32;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;|
Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-file-binding\sun-file-binding\HL7_Original_ACK_Demo\Filewrite_wsdl.wsdl'.|#]
[#|2008-06-26T07:55:28.078+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=32;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;|
Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-file-binding\sun-file-binding\HL7_Original_ACK_Demo\hl7receive_wsdl.wsdl'.|#]
[#|2008-06-26T07:55:28.109+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.HL7BindingDeployer|_ThreadID=33;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;HL7_Original_ACK_DemoCA-sun-hl7-binding;D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding;|Deploying service unit: HL7_Original_ACK_DemoCA-sun-hl7-binding from D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding.|#]
[#|2008-06-26T07:55:28.125+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.ServiceUnitImpl|_ThreadID=33;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|ServiceUnit deploy method called.|#]
[#|2008-06-26T07:55:28.140+1000|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=33;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;_RequestID=3c2d789c-457f-41db-a31a-d3c9ded95d92;|
Cannot find CatalogManager.properties|#]
[#|2008-06-26T07:55:28.156+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=33;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|
Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding\HL7_Original_ACK_Demo\Filewrite_wsdl.wsdl'.|#]
[#|2008-06-26T07:55:28.218+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=33;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|
Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding\HL7_Original_ACK_Demo\hl7receive_wsdl.wsdl'.|#]
[#|2008-06-26T07:55:28.250+1000|INFO|sun-appserver9.1|com.sun.jbi.management.DeploymentService|_ThreadID=31;_ThreadName=httpWorkerThread-4848-0;|JBIMA0402: Service Assembly file:/D:/Program Files/glassfish-v2ur2/domains/domain1/jbi/tmp/upload/7deaef5611ac1b8a7f57fe1/HL7_Original_ACK_DemoCA.zip has been deployed.|#]
[#|2008-06-26T07:55:28.328+1000|INFO|sun-appserver9.1|com.sun.jbi.management|_ThreadID=31;_ThreadName=httpWorkerThread-4848-0;|Starting service assembly HL7_Original_ACK_DemoCA on target server.|#]
[#|2008-06-26T07:55:28.406+1000|INFO|sun-appserver9.1|com.sun.jbi.engine.bpel.BPELSEDeployer|_ThreadID=34;_ThreadName=HL7_Original_ACK_DemoCA-HL7_Original_ACK_Demo;|BPELSEDeployer.starting_BPELSE_deploy_process|#]
[#|2008-06-26T07:55:34.406+1000|INFO|sun-appserver9.1|com.sun.jbi.engine.bpel.EngineHelper|_ThreadID=34;_ThreadName=HL7_Original_ACK_DemoCA-HL7_Original_ACK_Demo;|BPJBI-4016:Loaded BPEL, WSDL and XSD documents for HL7_Original_ACK_DemoCA-HL7_Original_ACK_Demo.|#]
[#|2008-06-26T07:55:34.484+1000|INFO|sun-appserver9.1|com.sun.jbi.engine.bpel.BPELSEDeployer|_ThreadID=34;_ThreadName=HL7_Original_ACK_DemoCA-HL7_Original_ACK_Demo;|BPJBI-5008:Activated an endpoint. Service name {http://enterprise.netbeans.org/bpel/HL7_Original_ACK_Demo/bpelprocess}PartnerLink1, endpoint name hl7receive_wsdlPortTypeRole_myRole|#]
[#|2008-06-26T07:55:34.484+1000|INFO|sun-appserver9.1|com.sun.jbi.engine.bpel.BPELSEDeployer|_ThreadID=34;_ThreadName=HL7_Original_ACK_DemoCA-HL7_Original_ACK_Demo;|BPELSEDeployer.BPELSE_deploy_process_finished|#]
[#|2008-06-26T07:55:34.500+1000|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=35;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;_RequestID=4410f26f-6686-4535-ba7a-8660e40bc5d9;|
Cannot find CatalogManager.properties|#]
[#|2008-06-26T07:55:34.500+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=35;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;|
Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-file-binding\sun-file-binding\HL7_Original_ACK_Demo\Filewrite_wsdl.wsdl'.|#]
[#|2008-06-26T07:55:34.515+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=35;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;|
Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-file-binding\sun-file-binding\HL7_Original_ACK_Demo\hl7receive_wsdl.wsdl'.|#]
[#|2008-06-26T07:55:36.265+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.HL7BindingDeployer|_ThreadID=36;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;HL7_Original_ACK_DemoCA-sun-hl7-binding;D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding;|Initializing service unit: HL7_Original_ACK_DemoCA-sun-hl7-binding from D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding.|#]
[#|2008-06-26T07:55:36.265+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.ServiceUnitImpl|_ThreadID=36;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|ServiceUnit init method called.|#]
[#|2008-06-26T07:55:36.265+1000|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=36;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;_RequestID=5ed8e1b9-af37-4cd5-ad23-140a112d3d28;|
Cannot find CatalogManager.properties|#]
[#|2008-06-26T07:55:36.265+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=36;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|
Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding\HL7_Original_ACK_Demo\Filewrite_wsdl.wsdl'.|#]
[#|2008-06-26T07:55:36.265+1000|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=36;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|
Retrieving document at 'D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding\HL7_Original_ACK_Demo\hl7receive_wsdl.wsdl'.|#]
[#|2008-06-26T07:55:37.109+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.HL7BindingDeployer|_ThreadID=36;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;HL7_Original_ACK_DemoCA-sun-hl7-binding;|HL7BC_Complete_init_SU|#]
[#|2008-06-26T07:55:37.140+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.HL7BindingDeployer|_ThreadID=37;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;HL7_Original_ACK_DemoCA-sun-hl7-binding;|Starting service unit: HL7_Original_ACK_DemoCA-sun-hl7-binding.|#]
[#|2008-06-26T07:55:37.140+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.ServiceUnitImpl|_ThreadID=37;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|ServiceUnit start method called.|#]
[#|2008-06-26T07:55:37.140+1000|SEVERE|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.ServiceUnitImpl|_ThreadID=37;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;hl7receive_wsdlPort;_RequestID=04f2a675-cd21-4a08-b61f-56da459eeef5;|Failed to start inbound message processor for endpoint: hl7receive_wsdlPort.|#]
[#|2008-06-26T07:55:37.140+1000|SEVERE|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.ServiceUnitImpl|_ThreadID=37;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;{http://j2ee.netbeans.org/wsdl/hl7receive_wsdl}hl7receive_wsdlService;hl7receive_wsdlPort;_RequestID=04f2a675-cd21-4a08-b61f-56da459eeef5;|Failed to start the end point with service name {http://j2ee.netbeans.org/wsdl/hl7receive_wsdl}hl7receive_wsdlService and endpoint name hl7receive_wsdlPort: null|#]
[#|2008-06-26T07:55:37.140+1000|SEVERE|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.HL7BindingDeployer|_ThreadID=37;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;_RequestID=04f2a675-cd21-4a08-b61f-56da459eeef5;|Error starting service unit due to: null|#]
[#|2008-06-26T07:55:37.156+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.HL7BindingDeployer|_ThreadID=38;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;HL7_Original_ACK_DemoCA-sun-hl7-binding;|Shutting down service unit: HL7_Original_ACK_DemoCA-sun-hl7-binding.|#]
[#|2008-06-26T07:55:37.156+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.ServiceUnitImpl|_ThreadID=38;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;|ServiceUnit shutdown method called.|#]
[#|2008-06-26T07:55:37.156+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.ServiceUnitImpl|_ThreadID=38;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;HL7_Original_ACK_DemoCA-sun-hl7-binding;|Successfully shutdown service unit: HL7_Original_ACK_DemoCA-sun-hl7-binding.|#]
[#|2008-06-26T07:55:37.218+1000|INFO|sun-appserver9.1|com.sun.jbi.management|_ThreadID=31;_ThreadName=httpWorkerThread-4848-0;|Stopping service assembly HL7_Original_ACK_DemoCA on target server.|#]
[#|2008-06-26T07:55:37.265+1000|INFO|sun-appserver9.1|sun-file-binding.com.sun.jbi.filebc.ServiceUnitImpl|_ThreadID=39;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;|ServiceUnit stop method called.|#]
[#|2008-06-26T07:55:37.265+1000|INFO|sun-appserver9.1|sun-file-binding.com.sun.jbi.filebc.ServiceUnitImpl|_ThreadID=39;_ThreadName=HL7_Original_ACK_DemoCA-sun-file-binding;HL7_Original_ACK_DemoCA-sun-file-binding;|Successfully stopped service unit: HL7_Original_ACK_DemoCA-sun-file-binding.|#]
[#|2008-06-26T07:55:37.312+1000|INFO|sun-appserver9.1|com.sun.jbi.management|_ThreadID=31;_ThreadName=httpWorkerThread-4848-0;|Shutting down service assembly HL7_Original_ACK_DemoCA on target server.|#]
[#|2008-06-26T07:55:37.453+1000|INFO|sun-appserver9.1|com.sun.jbi.management|_ThreadID=31;_ThreadName=httpWorkerThread-4848-0;|Undeploying service assembly HL7_Original_ACK_DemoCA from target server.|#]
[#|2008-06-26T07:55:37.546+1000|INFO|sun-appserver9.1|sun-hl7-binding.com.sun.jbi.hl7bc.HL7BindingDeployer|_ThreadID=40;_ThreadName=HL7_Original_ACK_DemoCA-sun-hl7-binding;HL7_Original_ACK_DemoCA-sun-hl7-binding;D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding;|Undeploying service unit: HL7_Original_ACK_DemoCA-sun-hl7-binding from D:\Program Files\glassfish-v2ur2\domains\domain1\jbi\service-assemblies\HL7_Original_ACK_DemoCA\HL7_Original_ACK_DemoCA-sun-hl7-binding\sun-hl7-binding.|#]
[#|2008-06-26T07:55:37.562+1000|INFO|sun-appserver9.1|com.sun.jbi.management.DeploymentService|_ThreadID=31;_ThreadName=httpWorkerThread-4848-0;|JBIMA0412: Service Assembly with ID : HL7_Original_ACK_DemoCA has been undeployed.|#]
I felt suspicious about the entry
hl7receive_wsdlService and endpoint name hl7receive_wsdlPort: null
So I went hunting in the code, and re-visitted the video to see if I had missed something in amongst the bindings, but I'm not good with wsdl, and everything seemed to match the code shown in the example, so I haven't found a point at which to make a change.
Thanks for the advice on the e-mail alias, I will post there too.
Ianto

Doubts about configurate services with JBI

Similar Messages

Maybe you are looking for