Importing cobol copybook

hi friends,
Is there any way to import COBOL copy book in XI like Websphere Business Integrator does?
Is any one aware of a easier method than creating XML structure of legacy message expected manually?
your suggestions would be highly appreciated.
Thanks in advance.
sachin kotalwar

In XI, if you create a data type with just one attribute, switch over to the XSD tab, you'll note "import & export XSD" are there. If you export, you'll have the shell you need for the the XSD schema. Although you created just one attribute, if you copy that block of lines over & over, XI will accept them back in and expand your layout with whatever fields you add.
To make it easier, I dumped my copybook into an excel sheet, created a mailmerge with word, then copied that back into my exported XSD document... then you can re-import back to XI and all your fields are there.

Similar Messages

Importing COBOL copybook into OSB & converting it to ASCII

Hi,
I want to import a COBOL copybook(.cpy/.copy file) into OSB.
Based on that copybook, there is an EBCDIC file which I want to convert into an ASCII file.
I used Format Builder to import the copybook, but it does not show any indication whether the copybook got imported or not.
Please help... this is urgent..

There was a problem with the copybook... so it was not imported.
The corrected copybook got imported perfectly.

COBOL Copybook

Any idea when OWB will read a COBOL copybook and generate a SQL*Loader control file? The documentation says available in a future release.
Chris Busch
[email protected]

OK, looking at the thread, I can imagine you are looking for an answer. Unfortunately, the partner we were looking at to provide this functionality got bought by another company... basically screwing up our plans to partner. There are still partners out there, that can read Cobol copybooks (e.g. Syncsort) that you could use to pre-process files and then load into Oracle using Warehouse Builder. You could perhaps integrate the third-party calls in the process flow editor as an external process.
Thanks,
Mark.

Error in reversing a cobol copybook

Hi friends,
I have a cobol copybook "xyz.copy" and the corresponding data file 'abc.blank'(EBCDIC format)
I created a datastore with the following details:
Name :MyCobyBookFile
ResourceName: location of the data file.
Under files tab:
File Format :Fixed
Under Columns tab:
Clicked on Reverse Cobol Copybook
File: location of copybook file
Character set: ISO-8859-1(by default)
If i choose:
A) Description Format : EBCDIC and Data Format : EBCDIC .....it gives me error " The File reverse is only possible for delimited files"
B) Description Format : EBCDIC and Data Format : ASCII.....it gives me error " The File reverse is only possible for delimited files"
C) Description Format :ASCII and Data Format : EBCDIC...it gives me error "java.lang.NumberFormatException" for input string "xyz"
Any help would be highly appreciated.
Thanks.

Hi,
Check the SAP note 1252930
Also check point no 7 in the SAP note - 1119073.
Hope the above notes will help to resolve this issue.
Thanks,
Ram

Reverse a Cobol copybook

I have a txt file of a Cobol copybook I'm trying to reverse but I keep getting a null pointer error. I haven't found much more than a paragraph on the subject in any of the ODI documentation. I have over 1,600 fields/columns in that source so reversing the copybook will save me a lot of manual input time. Any help will be greatly appreciated. Thanks.

Hi,
Let me try to help..
Are you sure about this number? Take a look if there is any "redefines" in the copybook... I never saw such amout of columns in a single table and I'm not sure if ODI (or even Oracle) is able to manage such number of columns....
Cezar Santos
[www.odiexperts.com|www.odiexperts.com]

Translating from COBOL copybook format to XML

Hi folks,
A student asked me this question today: Does WLI provide any support for translating
from COBOL copybook format to XML?
The discussion had to do with adapters. I presume that you would have to do this
sort of translation yourself, but I didn't know if something like this were in
the product, somehow.
Also, is there any reference code to an SAP adapter out there that I could take
a look at?
Thanks -
Paul Loefstedt

Hi Paul,
Long time no see. I know BEA's WebLogic Java Adaptor for Mainframe has a utility
to take Cobol copybook and converted to Java Object. Not sure about WLI.
Jim Zhou.
"Paul Loefstedt" <[email protected]> wrote:
>
Hi folks,
A student asked me this question today: Does WLI provide any support
for translating
from COBOL copybook format to XML?
The discussion had to do with adapters. I presume that you would have
to do this
sort of translation yourself, but I didn't know if something like this
were in
the product, somehow.
Also, is there any reference code to an SAP adapter out there that I
could take
a look at?
Thanks -
Paul Loefstedt

Reverse COBOL copybook with REDEFINES

Hi,
How do i reverse a COBOL copybook which contains REDEFINES.
Thanks.

Hi ,
Check the Following link
http://gerardnico.com/doc/odi/webhelp/en/usermanual/designer/model/reverse_cobol_copybook.htm
Reverse a Cobol copybook
Which may helpful for you.
Thanks,
Ananth

Cobol copybook handlers

Dear All
does anybody have some good examples of complex cobol copybook
translations into/out of xml or some other structured format.
Samples/examples would be an excellent start

OK, looking at the thread, I can imagine you are looking for an answer. Unfortunately, the partner we were looking at to provide this functionality got bought by another company... basically screwing up our plans to partner. There are still partners out there, that can read Cobol copybooks (e.g. Syncsort) that you could use to pre-process files and then load into Oracle using Warehouse Builder. You could perhaps integrate the third-party calls in the process flow editor as an external process.
Thanks,
Mark.

Errors in Cobol Copybook

Hi,
I was trying to reverse an EBCDIC file with the Copybook option. But ran into the following error
java.lang.NumberFormatException: For input string: "TIMES"
It was an COBOL table declaration and I have confirmed that the syntax is right. It goes something like this
"OCCURS 1 TO 150 TIMES DEPENDING ON SK68-PIR-NUM-CRIT-NEM."
It works if I remove the entire DEPENDING ON Clause and just replace it with "OCCURS 150", but the data pulled becomes unusable. Does anybody know how to make ODI recognize DEPENDS ON clause? Did anyone achieve this before?
Thanks in Advance.

Hi Md,
It hard to analyse the issue base on the limited information, Are there any error message on the log? Under C:\Program Files\Microsoft SQL Server\MSAS11.\OLAP\Log (this could be different for your server), there are 3 log files that are generated:
msmdrrv.log
FlightRecorderCurrent.trc
FightRecorderBack.trc
The msmdrrv.log simply points to the other two logs. There might be some detail information for this error. Please provide us the detail information about it, so that we can make further analysis.
Regards,
Charlie Liao
TechNet Community Support

Issue in MFL Transformation

Hi All,
I am trying to convert a NON-XML file to XML using MFL in OSB, but I am facing issue in doing so.
The file which I read is in the below format
Group of header and details (Can have multiple header-details group)
11/28/2012|01|3
50|1|001|045775401|001|05/15/2012|05/27/2012|04/07/2012|05/06/2012|47.10
60|2|001|045772801|001|05/15/2012|05/27/2012|04/08/2012|05/07/2012|119.98
30|3|001|045769501|001|05/15/2012|05/27/2012|04/07/2012|05/06/2012|136.80
11/25/2012|02|4
55|4|001|045761101|001|05/15/2012|05/27/2012|04/08/2012|05/07/2012|278.38
30|5|001|045684102|001|05/15/2012|05/27/2012|04/09/2012|05/08/2012|35.99
60|6|001|045683401|001|05/15/2012|99/99/9999|04/09/2012|05/08/2012|734.86
61|7|001|045673701|001|05/15/2012|99/99/9999|04/09/2012|05/08/2012|284.52
The XSD I created using Native file format builder for this file is as follows
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
targetNamespace="http://twc.com/ReadDetailFile"
xmlns:tns="http://twc.com/ReadDetailFile"
elementFormDefault="qualified" attributeFormDefault="unqualified"
nxsd:encoding="ASCII" nxsd:stream="chars" nxsd:version="NXSD">
<xsd:element name="Header">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="TransmissionDate" type="xsd:date"
nxsd:style="terminated" nxsd:terminatedBy="|"></xsd:element>
<xsd:element name="SequenceNumber" type="xsd:string"
nxsd:style="terminated" nxsd:terminatedBy="|"></xsd:element>
<xsd:element name="NoofStatements" type="xsd:string"
nxsd:style="terminated" nxsd:terminatedBy="${eol}"></xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="StatementDetail">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="DivisionId" type="xsd:string" nxsd:style="terminated"
nxsd:terminatedBy="|"></xsd:element>
<xsd:element name="CorpSubCorp" type="xsd:string"
nxsd:style="terminated" nxsd:terminatedBy="|"></xsd:element>
<xsd:element name="SiteId" type="xsd:string" nxsd:style="terminated"
nxsd:terminatedBy="|"></xsd:element>
<xsd:element name="AccountNo" type="xsd:string" nxsd:style="terminated"
nxsd:terminatedBy="|"></xsd:element>
<xsd:element name="StatementCode" type="xsd:string"
nxsd:style="terminated" nxsd:terminatedBy="|"></xsd:element>
<xsd:element name="StatementDate" type="xsd:date"
nxsd:style="terminated" nxsd:terminatedBy="|"></xsd:element>
<xsd:element name="StatementDueDate" type="xsd:date"
nxsd:style="terminated" nxsd:terminatedBy="|"></xsd:element>
<xsd:element name="PeriodFrom" type="xsd:date" nxsd:style="terminated"
nxsd:terminatedBy="|"></xsd:element>
<xsd:element name="PeriodTo" type="xsd:date" nxsd:style="terminated"
nxsd:terminatedBy="|"></xsd:element>
<xsd:element name="Due" type="xsd:decimal" nxsd:style="terminated"
nxsd:terminatedBy="${eol}"></xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Detail">
<xsd:complexType>
<xsd:sequence maxOccurs="unbounded" minOccurs="1">
<xsd:element ref="tns:Header" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="tns:StatementDetail" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
But this is not working for me. Any help is highly appreciated in solving this issues.
Thanks in Advance!!
Thanks,
Anju

Hi Dibya,
Can you try configuring OSB Proxy Service (Message Type - binary) and test your service. Let me know the process how you have created MFL file using cobol copybook. I mean, have you imported cobol copybook using import option available in MFL editior?

Loading COBOL file - blocked variable records and varying size arrays

We would like to use ODI 11g to regularly to parse and load into Oracle DB 11g complex files that originate on the MVS mainframe.
Key file characteristics are:
1. EBCDIC encoding
2. file contains blocked records - each block starts with a 4-byte Block Descriptor Word (BDW). BDW bytes 1-2 specify the block length stored as a 16-bit unsigned integer, i.e. PIC (5) COMP in COBOL.
3. each file block contains multiple variable size records - BDW is followed by 1 or more variable length records. Each record starts with a 4-bytes Record Descriptor Word (RDW). RDW bytes 1-2 specify the record length stored as 16 bit unsigned integer, i.e. PIC (5) COMP in COBOL.
4. each file record contains number of scalar fields and several varying-size arrays - COBOL OCCURS DEPENDING ON. For example:
03 SAMPLE-ARRAY-CNT PIC S9(1) COMP-3.
03 SAMPLE-ARRAY OCCURS 0 TO 5 TIMES DEPENDING ON SAMPLE-ARRAY-CNT.
05 ARRAY-CD1 PIC X(5).
05 ARRAY-CD2 PIC X(7).
05 ARRAY-AMOUNT PIC S9(3)V9999 COMP-3.
5, file contains fields stored as COBOL COMPUTATIONAL and COMPUTATIONAL-3.
6. average record lengh is 1,000 bytes and each file is about 4GB
SQL*Loader/external table functionality can handle most of these requirements on one-off basis, but collectively they present a significant challenge. The file layout can't be reversed engineered as COBOL copybook into ODI.
Does ODI have complex file parsing capabilities that could be used to (pre-)process the file, in as few passes as possible?
Thanks
Petr

Hi,
there's a couple of options here, and I've included what I think is the simplest below (using TestStand 2.0.1).
It's not exactly elegant though. What I've done is to put in a step that finds out the number of steps to load (based on an earlier decision - in this case a message popup step). I read a number from the limits file, and use this in the looping options of the property loader step that's loading the values into the array. I've done it with a fixed size array target here, big enough to take any incoming data. (Otherwise, knowing how many items you're going to load from the limits file, you could start with an empty array and re-size it prior to loading).
I've cheated slightly by using the pre-expression on the property loader step to specify where th
e data is coming from and where it's going to in the sequence on each iteration of the loop based on the Runstate.Loopindex.
Another option is to go straight into the property loader step, and keep loading properties until the Step.Result.NumPropertiesRead = 0 (remember we're only doing this one at a time)
Another idea would be to load in a value, and check it isn't a "flag" value (i.e. you'd never use say 999 in your array, so set the last element in your limits file to this, and drop out of the loop when this happens.
Further still, you've got the source code for the property loader step, so you could re-write it to make a custom step that loads an array until it fails all on its own (no looping in TestStand).
Hope this gets you going
S.
// it takes almost no time to rate an answer
Attachments:
DynamicPropertyLoader.seq ‏32 KB

Mapping complexType to an equivalent COBOL Structure layout

Hello,
In the context of migrating existant web-services from CICS to Tuxedo/SALT, I have two questions :
1 - Is there a way to "automatically" map a complexType to a buffer where the data will be layed out as expected by a Cobol structure equivalent to the complexType?
The main reason is to avoid having to "parse" the FML32 buffer in order to recompose the data that will be given as input to the Cobol programs of the web-service.
2 - Since it is about migrating existent services, we have some cases where sub-elements have the same names. This was not causing an issue on CICS. When doing some preliminary tests on SALT, we get the following warning:
WSDLCVT:26:WARNING: More than one field with different fullname or schema have the same name. Please resolve the naming conflict. ...
When the duplicate names are in different elements used separately in request/answer , it worked OK.
However, we have some cases when the duplicates are on a same complexType...
Is there a workaround to this or it is planned to remove this constraint in a future release of SALT.
Thanks in advance for your help.
Edited by: user12047311 on 13 août 2012 03:20

Hi,
Tuxedo ships with a tool that can convert COBOL copybooks to Tuxedo VIEW/VIEW32 buffers. Using SALT, the migrated services can be directly accessed by SOAP/HTTP clients without any code changes to the COBOL programs as SALT supports mapping VIEW/VIEW32 buffers to SOAP and back.
The outbound calls are a bit more difficult because the buffer type used for outbound calls is FML32 as it is the only buffer type that can match the shape of the XML document required to make the outbound SOAP call. My recommendation would be to create a simple proxy service in Tuxedo that takes the VIEW/VIEW32 buffer the COBOL code is currently creating to call the external web service and map that to FML32. Depending upon the mapping requirements, it's possible the mapping could be done with a single call to the FML function that converts a VIEW/VIEW32 buffer to an FML32 buffer, but that would depend a lot on the mapping that needs to be done. In fact, if this is later option will work, it could be done right inside the COBOL program using the FVFTOS32 and FVSTOF32 COBOL APIs provided by Tuxedo.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

VSAM file with multiple record layouts (COBOL REDEFINES)

Hi. We're using Tuxedo 12c to migrate a COBOL/CICS/VSAM application from MVS to Solaris/Oracle 11gR2.
We have a few VSAM files with record layouts that start with a record-type field, and based on that, the remainder of the record layout varies based on COBOL copybooks using REDEFINES. We can't be the first to have this issue, and am wondering if there's a best-practice solution. Our initial thought is that each record type should become a separate database table, but if we need to do this manually, we'll also need to modify the post-converted code manually. I'm hoping there's a better way.
Thanks.

You are correct; you are not the first person to do this. There are a number of different strategies depending upon what you are trying to accomplish. First, is your objective to leave the COBOL/CICS/VSAM as is? If so, which COBOL compiler do you intend to use? Are you using Tuxedo ART Workbench? Are you aware that you have the option of leaving the VSAM datasets as VSAM on the target platform? If you want to convert VSAM to Oracle DB tables, you can create a separate table for each record type as you suggested or you can treat the entire record as a blob and let the copyfile sort it out once the data is returned to the program. Of course with this approach you will not realize the benefits Oracle DB as an RDBMS. Please provide me some additional context and I will make some best practices suggestions.
You can get some insight on Tuxedo ART Workbench at http://docs.oracle.com/cd/E18050_01/artwb/docs11gr1/wbuser/FileToOracle.html

Need a example about calling cobol by java?

hi all,
who can post a exampe about call cobol by java, thanks a lot.

I have found it.
CobolProgramCIPFFTBN cobolCIPFFTBN = (CobolProgramCIPFFTBN) getDynamicComponent(CobolProgramCIPFFTBN.class);
CobolCopybookCICFFTBN fftbn = cobolCIPFFTBN.getCobolCopybookCICFFTBN();
//Set the input values of the COBOL Copybook.
fftbn.get_INPUT_WRK().set_CREDIT_DT( businessDate );
fftbn.get_INPUT_WRK().set_DEBIT_DT( businessDate );
fftbn.get_INPUT_WRK().set_INCLUDE_BACKDATED_FT_SW(Bool.TRUE);
fftbn.get_INPUT_WRK().set_SA_ID(pSa.getId().getIdValue());
// Call cobol program
cobolCIPFFTBN.callCobol();

[Patch 정보] TRACKING BUG FOR CUMULATIVE MLR#6 ON TOP OF BPEL PM 10.1.3.3.1

최근에 출시된 BPEL PM 10.1.3.3.1의 통합패치입니다.
아래는 readme.txt에 포함된 patch list입니다.
# WARNING: Failure to carefully read and understand these requirements may
# result in your applying a patch that can cause your Oracle Server to
# malfunction, including interruption of service and/or loss of data.
# If you do not meet all of the following requirements, please log an
# iTAR, so that an Oracle Support Analyst may review your situation. The
# Oracle analyst will help you determine if this patch is suitable for you
# to apply to your system. We recommend that you avoid applying any
# temporary patch unless directed by an Oracle Support Analyst who has
# reviewed your system and determined that it is applicable.
# Requirements:
# - You must have located this patch via a Bug Database entry
# and have the exact symptoms described in the bug entry.
# - Your system configuration (Oracle Server version and patch
# level, OS Version) must exactly match those in the bug
# database entry - You must have NO OTHER PATCHES installed on
# your Oracle Server since the latest patch set (or base release
# x.y.z if you have no patch sets installed).
# - [Oracle 9.0.4.1 & above] You must have Perl 5.00503 (or later)
# installed under the ORACLE_HOME, or elsewhere within the host
# environment.
# Refer to the following link for details on Perl and OPatch:
# http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=189489.1
# If you do NOT meet these requirements, or are not certain that you meet
# these requirements, please log an iTAR requesting assistance with this
# patch and Support will make a determination about whether you should
# apply this patch.
# 10.1.3.3.1 Bundle Patch 6823628
# DATE: March 14, 2008
# Platform Patch for : Generic
# Product Version # : 10.1.3.3.1
# Product Patched : Oracle(R) SOA
# Bugs Fixed by 10.1.3.3.1 Initial patch 6492514 :
# Bug 5473225 - PATCH01GENESIS HOT UNABLE TO CATCH AN EXCEPTION DURING A
# TRANSFORM
# Bug 5699423 - PARTNERLINK PROPERTY THAT SET BPELXPROPERTY FUNCTION DOESN'T
# WORK
# Bug 5848272 - STATEFUL WEBSERVICES DEMO ON OTN DOES NOT WORK 10.1.3.1
# Bug 5872799 - ANT DEPLOY BPEL TEST FAILS/RUNS ON DEFAULT DOMAIN NOT
# SPECIFIED TARGET DOMAIN
# Bug 5883401 - ALLOW A WAY TO CREATE EMPTY NODES - AND USE FOR REQUIRED
# NODES
# Bug 5919412 - SAMPLE DEMO BPEL PROCESSES MIMESERVICE MIMEREQUESTER AXIS
# JAVA EXAMPLE ERROR
# Bug 5924483 - ESB SHOULD SUPPORT SOAP EDNPOINT LOCATION DYNAMIC UDDI LOOKUP
# Bug 5926809 - ORAPARSEESCAPEDXML XPATH EXPRESSION FAILED TO EXECUTE
# FOTY0001 TYPE ERROR
# Bug 5937320 - STRANGE BEHAVIOUR CALLING FROM BPEL TO BPEL GETTING
# NULLPOINTEREXCEPTION.
# Bug 5944641 - BPA BLUEPRINT NOT AVAIALBLE IN JDEVELOPER
# Bug 5945059 - JAVA.LANG.NULLPOINTEREXCEPTION SENDING EMAILS WITH PAYLOADS
# LARGER THAT 1MB
# Bug 5962677 - WS RESPONSE IS EMPTY SOAP BODY IN ONE-WAY CALL
# Bug 5963425 - WHEN THE OUTCOMES FOR A HT CHANGED & IMPORTED - UPDATE
# CONNECTION ROLES IN BPEL
# Bug 5964097 - AQ ADAPTER DEPLOYMENT CAUSES OPMN TO PERFORM A FORCEFUL
# SHUTDOWN IN SOA
# Bug 5971534 - CANNOT GRANT USER TASK VIEWS TO GROUPS, ONLY TO USERS.
# Bug 5989367 - REFER TO SR 6252219.993 BPEL 10.1.3 ONLY COPIES IN ASSIGN,
# IN 10.1.2 IT CREATES
# Bug 5989527 - ENHANCEMENT WARNING SHOULD BE GIVEN UPON UPLOAD IF BPEL
# PROCESS IS OPEN IN ARIS
# Bug 5997936 - ESB FAULT DOES NOT GET PROPAGATED TO BPEL
# Bug 6000575 - PERF NEED ESB PURGE SCRIPT TO PURGE BY DATE AND PROCESS
# Bug 6001796 - POSTING OF DATE RECEIVED FROM XML GATEWAY TO BPEL FAILED IN
# ESB
# Bug 6005407 - BPEL PROCESS DOESN'T PROPOGATE FAULT THROWN BY BPEL
# SUB-PROCESS
# Bug 6017846 - MIMETYPE OF EMAIL NOTIFICATION IS NOT SET THROUGH HUMAN TASK
# Bug 6027734 - DECISION SERVICE IMPORT - LOCATING DECISION SERVICE IN .DECS
# FILE IMPROPER
# Bug 6028985 - EXCEEDED MAXIMUM NUMBER OF SUBSCRIBERS FOR QUEUE
# ORAESB.ESB_CONTROL
# Bug 6041508 - CREATING/UPDATING DVM CAUSE EXCEPTION
# Bug 6053708 - FTP ADAPTER DOES NOT SUPPORT ENCRYPTED PASSWORD IN
# OC4J-RA.XML
# Bug 6054034 - INDEX4,INDEX5 AND INDEX6 CANNOT BE USED IN BPEL CONSOLE
# Bug 6068801 - BACKPORT OF BPEL ON WEBLOGIC - VERSION 10.1.3.3
# Bug 6070991 - HT EXPORT DOES NOT EXPORT PARAMETERS, ALLOW PARTICIPANTS TO
# INVITE OTHERS
# Bug 6071001 - WSIF HTTP BINDING NOT WORKING FROM ESB
# Bug 6073311 - STRESS SCOPE NOT FOUND ON CALLBACK - WRONG (DUPE)
# SUBSCRIPTION IN TABLE
# Bug 6081070 - JMS ADAPTER REJECTION HANDLER CREATE 0 BYTE FILES
# Bug 6083419 - DECISION SERVICE SCOPE NEED TO HAVE A SPECIAL INDICATOR
# Bug 6085799 - HUMAN TASK ADDED IN SCOPE IN JDEV IS NOT UPDATED TO BPA
# SERVER
# Bug 6085933 - EXPORT AND EXPLORE SHOULD USE USER LANGUAGE AND NOT ENGLISH
# ALWAYS
# Bug 6086281 - STRING INDEX OUT OF RANGE ERROR FOR COBOL COPYBOOK WITH PIC
# CLAUSE HAVING S
# Bug 6086453 - DOMAINS CREATED IN A CLUSTER GETS NOT PROPAGATED TO NEW OR
# EXISTING NODES
# Bug 6087484 - MULTIPLE HEADER SETTING CAUSES ESB EXCEPTION
# Bug 6087645 - ESB SHOULD ALLOW USER PICK RUNTIME PROTOCOL (HTTP/HTTPS)
# Bug 6110231 - TRANSLATION NOT BASED ON MQ CCSID CHARSET
# Bug 6120226 - BPEL IS NOT SETTING THE APPS CONTEXT CORRECTLY
# Bug 6120323 - COMPLETIONPERSISTPOLICY ON DOMAIN LEVEL HAS DISAPPEARED
# Bug 6125184 - ESB JMS SESSION ROLLBACK ORACLE.JMS.AQJMSEXCEPTION
# Bug 6127824 - [AIA2.0] CURRENT XREF IMPLEMENTATION IS MISSING REQUIRED
# INDEXES ON XREF SCHEMA
# Bug 6128247 - HTTPCONNECTOR POST() METHOD SHOULD RAISE EXCEPTION FOR ALL
# STATUS CODES EXCEPT 2
# Bug 6131159 - ENABLE USERS TO CHOOSE XSD WHEN CREATING A BPEL PROCESS FROM
# BLUE PRINT
# Bug 6132141 - PROCESS_DEFAULT TABLE STILL CONTAINS INFORMATION FROM
# UNDEPLOYED PROCESSES
# Bug 6133190 - ENABLING ESB CONSOLE HTTP/S IS MAKING THE CONSOLE TO COME UP
# BLANK.
# Bug 6139681 - BPEL WSDL LINK IN CLUSTERED RUNTIME POINTS TO A SINGLE NODE
# Bug 6141259 - BASICHEADERS NOT PUTTING WWW-AUTHENTICATE HEADERS FOR HTTP
# BINDING IN BPEL
# Bug 6148021 - BPEL NATIVE SCHEMA FOR COBOL COPYBOOK WITH IMPLIED DECIMAL
# LOSES DIGIT IN OUTPUT
# Bug 6149672 - XOR DATA - CONDITION EXPRESSION SPECIFICATION IS NOT
# INTUITIVE IN BPMN MODELS
# Bug 6152830 - LOSING CONDITIONAL EXPRESSIONS CREATED IN JDEV UPON MERGE
# Bug 6158128 - BASICHEADERS NOT PUTTING WWW-AUTHENTICATE HEADERS FOR HTTP
# BINDING
# Bug 6166991 - WHEN STARTING SOA SUITE,, PROCESSES FAIL DUE TO UNDEFINED
# WSDL
# Bug 6168226 - LOCATION-RESOLVER EXCEPTION THROWN IN OPMN LOGS
# Bug 6187883 - CHANGES FOR BPEL RELEASE ON JBOSS- VERSION 10.1.3.3
# Bug 6206148 - [AIA2.0] NEW FUNCTION REQUEST, XREFLOOKUPPOPULATEDCOLUMNS()
# Bug 6210481 - BPEL PROCESS WORKS INCORRECTLY WHEN AN ACTIVITY HAS MULTIPLE
# TRANSITIONCONDITION
# Bug 6240028 - WEBSERVICE THAT DOES NOT CHALLENGE FOR BASIC CREDENTIALS
# CANNOT BE INVOKED
# Bug 6257116 - MULTIPLE HEADER SETTING CAUSES ESB EXCEPTION
# Bug 6258925 - MESSAGE RECEIVED BY THE TARGET ENDPOINT VIA HTTP POST IS
# MISSING THE XML HEADER
# Bug 6259686 - TOO MANY UNNECESSARY WORKFLOW E-MAIL NOTIFICATIONS GENERATED
# Bug 6267726 - 10.1.3.3 ORACLE APPLICATIONS ADAPTER - NOT ABLE TO CAPTURE
# BUSINESS EVENT
# Bug 6272427 - WEBSPHERE BPEL FAILS FOR DATA RETRIEVAL OF SIZE 500+ KB
# Bug 6276995 - MERGE SCOPE NAME IS NOT UPDATED WHEN CHANGED IN THE SERVER
# Bug 6280570 - XPATH EXPRESSION ERROR IN MEDIATOR FOR ASSIGNING USER-DEFINED
# CONTEXT VALUES
# Bug 6282339 - RETRYCOUNT DOES NOT WORK PROPERLY
# Bug 6311039 - ONE RECORD IS INSERTED TO SYNC_STORE IF
# COMPLETIONPERSISTPOLICY SET TO FAULTED
# Bug 6311809 - [AIA2.0] NON-RETRYABLE ERRORS ARE NOT POSTED ON ESB_ERROR
# TOPIC
# Bug 6314784 - THE PRIORITY DEFINED IN THE BPA SUITE IS NOT TRANSFERRED TO
# THE JDEV CORRECTLY
# Bug 6314982 - THREADPOOL RACE CONDITION IN ADAPTER INITIALIZATION MESSAGES
# NOT PROCESSED
# Bug 6315104 - (SET)CLASSNAME MISSING IN TSENSOR JAXB OBJECTS
# Bug 6316554 - CONSUME FUNCTIONALITY OF JMS ADAPTER FOR BEA WEBLOGIC DOES
# NOT WORK
# Bug 6316950 - FILEADAPTER HARPER ENHANCEMENTS SYNC WRITE AND CHUNKED
# INTERACTION SPEC
# Bug 6317398 - THE ICON FOR COMPUTING DIFFERENCE IS MISSING IN JDEV REFRESH
# FROM SERVER DIALOG
# Bug 6320506 - IMPORT FAILS WHEN THERE IS AN UNNAMED CASE
# Bug 6321011 - CANNOT PROCESS 0 BYTE FILE USING FTP ADAPTER
# Bug 6325749 - TRACKING BUG FOR TRACKING ADDITIONAL CHANGES TO BUG #6032044
# Bug 6328584 - NEED A NEW XPATH EXPRESSION TO GET ATTACHMENT CONTENT VIA
# SOAP INVOKATION
# Bug 6333788 - COLLAPSING OF CONSECUTIVE ASSIGN TASKS BREAKS BAM SENSOR
# Bug 6335773 - BUILD.XML CONTAINS DO NOT EDIT .. - WHILE <CUSTOMIZE> TASK
# MUST BE IN <BPELC>
# Bug 6335805 - AQ ADAPTER OUTBOUND DOESN'T RECONNECT AFTER FAILURE
# Bug 6335822 - [AIA2.0] PSRPERFESB - RUNTIME DVM PERFORMANCE OVERHEAD IN ABS
# USE CASE
# Bug 6339126 - CHECKPOINT BPEL JAVA METHOD DOESN'T WORK IN BPEL 10.1.3.3
# Bug 6342899 - OUTLINECHANGE.XML NOT UPDATE WITH ACTIVITY FROM NEW BRANCH
# Bug 6343299 - ESB CONCRETE WSDL NAMESPACE SHOULD BE DIFFERENT FROM IMPORTED
# WSDL NAMESPACE
# Bug 6372741 - DEHYDRATION DATABASE KEEPS GROWING IN 10.1.3.3
# Bug 6401295 - NXSD SHOULD SUPPORT ESCAPING THE TERMINATED/QUOTED/SURROUNDED
# DELIMITERS
# Bug 6458691 - DIST DIRECTORY FOR 10.1.3.3.1 NEEDS UPDATE
# Bug 6461516 - BPEL CONSOLE CHANGES FOR DISPLAYING RELEASE 10.1.3.3.1
# Bug 6470742 - CHANGE THE VERSION NUMBER AND BUILD INFO IN ABOUT DIALOG IN
# ESB
# BUG ADDED IN MLR#1, 6671813 :
# Bug 6494921 - ORABPEL-02154 IF LONG DOMAIN AND SUITECASE NAMES IN USE
# BUGS ADDED IN MLR#2, 6671831 :
# Bug 6456519 - ERROR IN BPEL CONSOLE THREADS TAB:SERVLETEXCEPTION CANNOT GET
# DISPATCHER TRACE
# Bug 6354719 - WHICH JGROUP CONFIGURATION PARAMETER IMPACTS BPEL CLUSTER
# ACTIVITY
# Bug 6216169 - SCOPE NOT FOUND ERROR WHILE DELIVERING EXPIRATION MESSAGE OF
# ONALARM
# Bug 6395060 - ORA-01704 ON INSERTING A FAULTED INVOKE ACTIVITY_SENSOR
# Bug 6501312 - DEHYDRATION DATABASE KEEPS GROWING IN 10.1.3.3 #2
# Bug 6601020 - SEARCHBASE WHICH INCLUDES PARENTHESIS IN THE NAMES DOES NOT
# WORK
# Bug 6182023 - WAIT ACTIVITY FAILS TO CONTINUE IN CLUSTER WHEN PROCESSING
# NODE GOES DOWN
# BUGS ADDED IN MLR#3, 6723162 :
# Bug 6725374 - INSTANCE NOT FOUND IN DATASOURCE
# Bug 4964824 - TIMED OUT IF SET CORRELATIONSET INITIATE YES IN REPLY
# ACTIVITY
# Bug 6443218 - [AIA2.0]BPEL PROCESS THAT REPLIES A CAUGHT FAULT AND THEN
# RETHROWS IT IS STUCK
# Bug 6235180 - BPPEL XPATH FUNCTION XP20 CURRENT-DATETIME() IS RETURNING AN
# INCORRET TIME
# Bug 6011665 - BPEL RESTART CAUSES ORABPEL-08003 FAILED TO READ WSDL
# Bug 6731179 - INCREASED REQUESTS CAUSE OUTOFMEMORY ERRORS IN OC4J_SOA WHICH
# REQUIRES A RESTART
# Bug 6745591 - SYNC PROCESS <REPLY> FOLLOWED BY <THROW> CASE CAUSING
# OUTOFMEMORY ERRORS
# Bug 6396308 - UNABLE TO SEARCH FOR HUMAN TASK THAT INCLUDES TASK HISTORY
# FROM PREVIOUS TASK
# Bug 6455812 - DIRECT INVOCATION FROM ESB ROUTING SERVICE FAILS WHEN CALLED
# BPEL PROCESS
# Bug 6273370 - ESBLISTENERIMPL.ONFATALERROR GENERATING NPE ON CUSTOM ADAPTER
# Bug 6030243 - WORKFLOW NOTIFICATIONS FAILING WITHOUT BPELADMIN USER
# Bug 6473280 - INVOKING A .NET 3.0 SOAP SERVICE EXPOSED BY A ESB ENDPOINT
# GIVES A NPE
# BUGS ADDED IN MLR#4, 6748706 :
# Bug 6336442 - RESETTING ESB REPOSITORY DOES NOT CLEAR DB SLIDE REPOSITORY
# Bug 6316613 - MIDPROCESS ACTIVATION AGENT DOES NOT ACTIVATED FOR RETIRED
# BPEL PROCESS
# Bug 6368420 - SYSTEM IS NOT ASSIGNING TASK FOR REAPPROVAL AFTER REQUEST
# MORE INFO SUBMITTED
# Bug 6133670 - JDEV: UNABLE TO CREATE AN INTEGRATION SERVER CONNETION WHEN
# ESB IS ON HTTPS
# Bug 6681055 - TEXT ATTACHMENT CONTENT IS CORRUPTED
# Bug 6638648 - REQUEST HEADERS ARE NOT PASSED THROUGH TO THE OUTBOUND HEADER
# Bug 5521385 - [HA]PATCH01:ESB WILL LOSE TRACKING DATA WHEN JMS PROVIDER IS
# DOWN
# Bug 6759068 - WORKLIST APPLICATION PERFORMANCE DEGRADATION W/ SSL ENABLED
# FOR BPEL TO OVD
# BUGS ADDED IN MLR#5, 6782254 :
# Bug 6502310 - AUTOMATED RETRY ON FAILED INVOKE WITH CORRELATIONSET INIT
# FAILS
# Bug 6454795 - FAULT POLICY CHANGE NEEDS RESTART OF BPEL SERVER
# Bug 6732064 - FAILED TO READ WSDL ERROR ON THE CALLBACK ON RESTARTING BPEL
# OC4J CONTAINER
# Bug 6694313 - ZERO BYTE FILE WHEN REJECTEDMESSAGEHANDLERS FAILS
# Bug 6686528 - LINK IN APPLICATION.XML FILES CHANGED TO HARD LINKS WHEN MORE
# THAN 1 HT PRESENT
# Bug 6083024 - TEXT AND HTML DOC THAT RECEIVED AS ATTACHMENTS WERE EITHER
# BLANK OR GARBLED
# Bug 6638648 - REQUEST HEADERS ARE NOT PASSED THROUGH TO THE OUTBOUND HEADER
# Bug 6267726 - 10.1.3.3 ORACLE APPLICATIONS ADAPTER - NOT ABLE TO CAPTURE
# BUSINESS EVENT
# Bug 6774981 - NON-RETRYABLE ERRORS ARE NOT POSTED ON ESB_ERROR TOPIC
# Bug 6789177 - SFTP ADAPTER DOES NOT SUPPORT RENAMING FILES
# Bug 6809593 - BPEL UPGRADE TO 10.1.3.3.1 WITH ESB CALLS FAILS DUE TO
# CACHING OF PLNK - SERVICE
# BUGS ADDED IN MLR#6, 6823628 :
# Bug 6412909 - <BPELX:RENAME> DOES NOT ADD XMLNS DECLARATION AUTOMATICALLY
# Bug 6753116 - OUTPUT FROM HUMAN TASK IS NOT IS NOT CONSISTENT WITH
# SCHEMA
# ORDERING
# Bug 6832205 - BAD VERIFICATIONSERVICE PERFORMANCE IF LDAP SERVICE HAS HUGE
# DATA
# Bug 6189268 - CALLING BPEL PROCESS VIA SOAP FROM ESB FAILS WITH
# NAMENOTFOUNDEXCEPTION
# Bug 6834402 - JMS ADAPTER IMPROPERLY CASTS XAQUEUESESSION TO QUEUESESSION
# Bug 6073117 - TASK SERVICE DOESN'T RENDER THE TASK ACTIONS
# Bug 6054263 - REUSING SOAP WSDL IN RS CAUSES SOAP ACTION'S NS TO BE
# STRIPPED
# AWAY
# Bug 6489703 - ESB: NUMBER OF LISTENERS > 1 GIVES JMS EXCEPTION UNDER STRESS
# Bug 5679542 - FTP ADAPTER: COULD NOT PARSE TIME:
# JAVA.LANG.STRINGINDEXOUTOFBOUNDSEXCEPTION
# Bug 6770198 - AQ ACTIVATIONINSTANCES >1 DOESN'T WORK IN ESB
# Bug 6798779 - ESB ROUTING RULES CORRUPTED ON RE-REGISTERING WITH ROUTING
# ORDER
# IN WSDL CHANGED
# Bug 6617974 - BACKPORT REQUEST FOR MOVING FILES FUNCTION OF FTP ADAPTER
# Bug 6705707 - VALIDATION ON ESB CAN'T HANDLE NESTED SCHEMAS
# Bug 6414848 - FTP ADAPTER ARCHIVE FILENAME FOR BPEL IS BEING SCRAMBLED
# AFTER
# THE 10.1.3.3 UPGR
# Bug 5990764 - INFORMATION ARE LOST WHEN BPEL PROCESS IS POLLING FOR MAILS
# WITH
# ATTACHEMENTS
# Bug 6802070 - ORA-12899 SUBSCRIBER_ID/RES_SUBSCRIBER COLUMN SMALL FOR LONG
# DOMAIN AND PROCESS
# Bug 6753524 - WRONG SERVICE ENDPOINT OPEN WHEN TEST WEB SERVICE OF ESB
# Bug 6086434 - PROBLEM IN BPEL FILE ADAPTER WHILE READING A FIXED LENGTH
# FILE
# Bug 6823374 - BPEL 10.1.3.3.1 BAM SENSOR ACTION FAILS WITH BAM 11
# Bug 6819677 - HTTS STATUS 202 RETURNED INSTEAD OF SOAP FAULT
# Bug 6853301 - MQ ADAPTER REJECTED MESSAGES IS NOT REMOVED FROM THE RECOVERY
# QUEUE
# Bug 6847200 - 10.1.3.3.1 PATCH (#6748706) HAS STOPPED FTP ADAPTER POLLING
# IN
# SFTP MODE
# Bug 6895795 - AQ OUTBOUND DOESN'T WORK WITH MLR#6
업무에 참고하시기 바랍니다.

David,
You are right, theer are some changes incorporated in the latest MLR # 16 on the configurations files and on the dehydration store metrics(such as performance, fields,..).
However, I would not suggest to continue working on olite, even for Development/Test purposes as you might get stuck with strange errors...and the only solution would be to re-install SOA Suite if your olite gets corrupted. There might be ways to gets your olite back to position, but trust me..its not so simple.
Also, when you develop and stress test all your testcase scenarios in an TEST Adv installation, its simple to mimic the same in actual production box, as you exactly know its behavior.
So, go for a brand new SOA 10.1.3.4 MLR # 5 (or) 10.1.3.3.1 MLR # 16 SOA Suite Advanced installation with Oracle DB 10.2.0.3 as its dehydration store.
Hope this helps!
Cheers
Anirudh Pucha

Importing cobol copybook

Similar Messages

Maybe you are looking for