XPAth function for divide
Hi ,
Can any one explain xpath funtion for divide.
I am using this but it is showing error message unresolved xpath function.
divide(bpws:getVariableData('Invoke_1_ReadFromFTable_OutputVariable','ReadFromFTableOutputCollection','/ns13:ReadFromFTableOutputCollection/ns13:ReadFromFTableOutput/ns13:sduprc'),100)
this is the one i am using
Please help me
Regards
jj
Edited by: user10374148 on Oct 15, 2008 7:28 AM
The correct way to use the divide function is :-
bpws:getVariableData('Invoke_1_ReadFromFTable_OutputVariable','ReadFromFTableOutputCollection','/ns13:ReadFromFTableOutputCollection/ns13:ReadFromFTableOutput/ns13:sduprc') div 100
--Sandeep
Similar Messages
-
Error using custom xpath function with XSL transformations in BPM
Hi,
We have created a custom xpath function for use with SOA Suite and BPM. This has been built as per specified within the http://docs.oracle.com/cd/E29597_01/dev.1111/e10224/bp_appx_functs.htm#SOASE11100. We have also reviewed the Oracle Sample for mapper-107-ExtensionFunctions (sample demonstrates the use of user-defined extension functions). This has been registered with jDeveloper and SOA within the oracle.soa.ext_11.1.1 (run ant to include in oracle.soa.ext.jar)
We ideally want to use this is BPM within an xsl. However when consuming this function is either BPEL or BPM using an xsl, the xsl fails with an error such as:
XPath expression failed to execute. An error occurs while processing the XPath expression; the expression is ora:doXSLTransformForDoc("xsl/Transformation_1.xsl", $inputVariable.payload). The XPath expression failed to execute; the reason was: javax.xml.transform.TransformerException: oramds:/deployed-composites/default/gwCustomXpathUtil_rev1.0/xsl/Transformation_1.xsl<Line 9, Column 113>: XML-22043: (Error) Extension function error: Method not found 'getWeekDayDate'. Check the detailed root cause described in the exception message text and verify that the XPath query is correct.
In an Assign it operates fine and returns the expected result. We have included a combination of both of the Config files (ext-mapper-xpath-functions-config.xml and ext-soa-xpath-functions-config.xml) in the META-INF folder, however neither allow the use of this function in the XSL.
I believe there may be an issue getting the custom xpath functions within XSL files. Hence I have also raised an SR. Has anyone experiences of this?
Our SOA / BPM suite environment is using 11.1.1.6.4 and has the following patches applied:
13801175
14406487 (11.1.1.6.4 SOA Bundle)
13896993
13088538
Regards Dave
Edited by: DavidGaskell on Mar 14, 2013 10:08 PMHi All,
I am also facing the same issue...Experts can you please help us.
hi DavidGaskell, did you find any resolution, if so can you share it with me.....
Thanks,
RR -
Is it possible to throw a BPELFault from a custom xpath function?
I'm probably revealing my lack of java chops here, but I'd like to know if there's a way to throw a BPELFault from the "call" method within a custom xpath function.
The interface for IXPathFunction seems to dictate that "call" throws only an XPathFunctionException and the bpel server doesn't handle this exception properly. It records the exception in the logs but then the process just dies.
Right now I have this (simplified code):
public Object call(IXPathContext context,
List args) throws XPathFunctionException
if (args.size() == 1)
// do some stuff and return a value
throw new XPathFunctionException( "hexToInt() requires one string argument." );
What I want to have is something like this:
public Object call(IXPathContext context,
List args) throws BPELFault
if (args.size() == 1)
// do some stuff and return a value
BPELFault fault = new BPELFault(
new javax.xml.namespace.QName("http://schemas.xmlsoap.org/ws/2003/03/business-process/",
"selectionFailure"));
fault.setPart("code", "intToHex");
fault.setPart("summary", "hexToInt() requires one string argument.");
throw fault;
If I do this, the compiler rejects it saying that "call" must throw XPathFunctionException. Is there a way to extend the IXPathFunction interface to allow it to throw a useful fault?
Thanks!
SeanYeah, I'm using that patch (otherwise the process just crashes and you don't have a chance to catch the fault, even in a catchAll). Within the catchAll you can get the details from the error with something like this:
<copy>
<from expression="concat(ora:getFaultName(),'')"/>
<to variable="processFault" part="payload" query="/ns4:summary"/>
</copy>
<copy>
<from expression="concat(ora:getFaultAsString(),'')"/>
<to variable="processFault" part="payload" query="/ns4:detail"/>
</copy> -
Bpel Server Does Not Catch Exceptions Thrown By Custom Xpath Functions
Hi.
I am using some custom xpath functions in a bpel process and whenever they fail I get an XPathExecutionError with summary:
XPath expression failed to execute.
Error while processing xpath expression, the expression is "<my function>", the reason is FOTY0001: type error.
Please verify the xpath query.
I am forcing my function to fail by giving a wrong input, which should result in an XPathFunctionException("Input does not respect format").
There is a note on Metalink with ID 458434.1 on this subject which says that patch 5926809 should fix my problem.
Patch 5926809 fixes Bug 5926809 - ORA:PARSEESCAPEDXML XPATH EXPRESSION FAILED TO EXECUTE FOTY0001: TYPE ERROR.
I am using it, but it does not work :(
I am using version 10.1.3.3.0 of App Server with various patch sets, including fix for bug 5926809.
Has anyone suggestions on how to overcome this problem?
ThanksHello,
I am trying to add a custom xpath function to the BPEL server, and I see that you made it work. I am using Oracle SOA Suite 10.1.3.3 and jDeveloper 10.1.3.4. I am using this function inside an xsl mapping file, although I am able to compile and deploy the Bpel Process to the server, it stops mapping where I placed the function and I have not seen any meaningful message from the domain/log/ files.
Can you tell me how you did it?
I think you will tell me faster than Oracle support, I already placed an SR but they just give me superficial advice.
I appretiate your time and advice,
Guillermo -
Issue with AIA XPath Functions while compiling in JDeveloper 11.1.1.2.0
Hi,
BPEL flow contains Assign activity as below :
<assign name="Assign_1"><copy><from expression='aia.getServiceProperty("{http://xmlns.oracle.com/ABCSImpl/SAP/Core/UpdateItemListSAPReqABCSImpl/V1}UpdateItemListSAPReqABCSImpl","Default.SystemID",true())'/>
<to variable="temp"/></copy> </assign>
When I try to compile this flow, it gives me below errors :
SOALog:
Buildfile: D:\Oracle\Middleware\jdeveloper\bin\ant-sca-compile.xml
scac:
[scac] Validating composite : 'D:\test\TestAIAFunc\composite.xml'
[scac] FATAL_ERROR: in TestAIABPELProcess.bpel(81): unresolved xpath function
[scac] could not resolve xpath function "aia.getServiceProperty", because function "aia.getServiceProperty" not registered.
[scac] Make sure this function is either in the system xpath function configuration file or in the custom xpath function configuration file. Refer to the user guide regarding how to register xpath functions in your compiler environment.
BUILD FAILED
D:\Oracle\Middleware\jdeveloper\bin\ant-sca-compile.xml:264: Java returned: 1 Check log file : D:\test\TestAIAFunc\SCA-INF\classes\scac.log for errors
Total time: 9 seconds
CompilerLog:
Project: D:\test\TestAIAFunc\TestAIAFunc.jpr
D:\test\TestAIAFunc\TestAIABPELProcess.bpel
Error(81): unresolved xpath function
could not resolve xpath function "aia.getServiceProperty", because function "aia.getServiceProperty" not registered.
Make sure this function is either in the system xpath function configuration file or in the custom xpath function configuration file. Refer to the user guide regarding how to register xpath functions in your compiler environment.
I got latest aia.jar from server(SOA11.1.1.2, weblogic 10.3.2, AIA11gR1) and added aia.jar @ JDeveloper 11.1.1.2--> Tools--> Preferences--> SOA
I also added it in jdeveloper/lib, jdeveloper/jdev/lib
aia namespace is there in .bpel as : xmlns:aia="http://www.oracle.com/XSL/Transform/java/oracle.apps.aia.core.xpath.AIAFunctions"
Thanks,
HemaYou have to include the aia.jar file. I had same issue .. I had aia.jar included in the project but the file was not ther ein the path . so i updated the correct path .. it worked
-
XPath function failed in XSLT (OSB 10.3.1)
Platform : OSB 10.3.1 in Windows XP
Error : Test following XSLT scripts in OSB Console by getting error
Error executing the XSLT transformation: java.lang.NoSuchMethodException: For extension function, could not find method weblogic.apache.xpath.axes.WalkingIteratorSorted.upper-case([ExpressionContext,] ).
XSLT :
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:fn="http://www.w3.org/2004/07/xpath-functions"
xmlns:imp1="http://www.example.org/FaultMessage">
<xsl:template match="/">
<imp1:FaultMessage>
<imp1:code>
<xsl:text disable-output-escaping="no">Hard-Coding-Error-Code</xsl:text>
</imp1:code>
<imp1:summary>
<xsl:value-of select="/imp1:FaultMessage/imp1:summary" />
</imp1:summary>
<imp1:detail>
<xsl:value-of select="fn:upper-case(/imp1:FaultMessage/imp1:detail)" />
</imp1:detail>
</imp1:FaultMessage>
</xsl:template>
</xsl:stylesheet>
Any ideas?
Thank you
-Simon
Edited by: user10981433 on Jun 11, 2009 9:05 PMexporting and importing your osb projects to the new environment won't migrate the webservice you were calling from within the Oracle Service Bus.
if these were created in Eclipse too you can just regenerate an ear-file from them or use the build-scripts to deploy them to you new Weblogic Server.
don't mix up 2 things
the osb is only intermediar in here, so you can export/impot the resources from your osb workspace for these.
but if your process call any external webservice, the webservice itself will also need to get redeployed to the new enviroment, and this is something which has nothing to do with your osb projects.
it could be these webservice are also build in Eclipse, but they won't be part of the export/import of OSB.
so check if you have some build.xml script in these webservice projects so you can regenerate the ear archive, or try importing the project in your workspace (if not already done) and rightmouseclick on it > export > ear file
and use this ear file to deploy the webservice again in the Weblogic Console ( see : http://docs.oracle.com/cd/E13218_01/wlp/docs81/prodOps/deployment.html ) -
Why don't standard XPath functions work in XSLT?
I'm having a lot of trouble trying to do some simple string processing in XSLT. What I would like to do is make selection using the standard xpath functions defined by the w3c. I'm using this as my cheat sheet:
http://w3schools.com/xpath/xpath_functions.asp
I've tried the default XSLT parser that comes with Java, the latest distro of Xalan and the latest distro of Saxon. Nothing seems to recognize the fn namespace:
xmlns:fn="http://www.w3.org/2005/02/xpath-functions"
In particular, I'm trying to use the tokenize(string, regex) function. Only Xalan seems to support this at all, only recognizes {http://xml.apache.org/xalan}tokenize, and it is treating the regex as a literal.
This is very frustrating. Is it possible to get the standard Xpath functions to work for XSLT?How did you get it to work with Saxon? I have saxon9he.jar on my classpath. When I try to transform this:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:src="http://xml.kitfox.com/schema/game/tileWorld/textTable"
xmlns:xalan="http://xml.apache.org/xalan"
xmlns:fn="http://www.w3.org/2005/02/xpath-functions"
version="1.0">
<xsl:output method="text"/>
<xsl:template match="/">
<xsl:for-each select="fn:tokenize('a b c', '\s+')">
"<xsl:value-of select="."/>"
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>I get the error
Error on line 100
Cannot find a matching 2-argument function named
{http://www.w3.org/2005/02/xpath-functions}tokenize()Is there some other jar you need to include to get http://www.w3.org/2005/02/xpath-functions to resolve? -
Ora:processXSLT xpath function and absolute paths
It looks like ora:processXSLT xpath function does not honor absolute paths when specifying the location of the xslt to use in the first parameter. For example, if I call it like this:
<copy>
<from expression="ora:processXSLT('/u01/transforms/mytransform.xsl',bpws:getVariableData('xslInput','payload'))"/>
<to variable="xslOutput"/>
</copy>
I get the following error in the bpel logs:
Error while processing xpath expression, the expression is "ora:processXSLT('/u01/transforms/mytransform.xsl', bpws:getVariableData("xslInput", "payload"))", the reason is javax.xml.transform.TransformerException: java.io.FileNotFoundException: /u01/oracle/bpel/integration/orabpel/domains/test/tmp/.bpel_transformTest_1.0.jar/u01/transforms/mytransform.xsl (No such file or directory).
Please verify the xpath query.
It is assuming that the xsl will be relative to the bpel suitcase and just appending the supplied path to the relative path for the bpel process. Why would I want to do this? Well, I have hundreds of these maps and I want to be able to select one at runtime. I'm also adding new ones every day and I don't want to have to redeploy the process that uses them each time I add a new map. Is there any way to force this process to recognize the absolute path? I can work around it for now by using a bunch of ../../../../ stuff but that's a kludge and I'd like to find a better way to do it.
I get the same error with xdk:processXSLT.
Any suggestions?
Thanks!
SeanHi Sean,
Did you try to the file path with the file:// prefix and not just the path?
~ronen -
Ebi:getConvertedDateWithTZ XPATH function in AIA 11g?
Hi all,
There was an XPATH function available with PIP module to convert the datetime into a particular format.
xmlns:ebi="http://www.oracle.com/XSL/Transform/java/oracle.apps.ebi.core.xpath.EBIXPathFunctions" ebi:getConvertedDateWithTZ .
Can anybody point me which jar contains the 'oracle.apps.ebi.core.xpath.EBIXPathFunctions' class? Is this jar available with AIA 11g?
Rgds.I understand your reply and we are already doing that.
the osb installation is common across the domains .but i need these custom xpath function reflected only for my domain.
so my query is "whether we can set/overwrite any -D property at server startup or any server/domain level settings rather than updating the installation path?"
I am just trying to understand whether we can avoid conflicts with multiple domains sharing the same installation. -
i am creating custom xpath function in jdeveloper(10g).i hav followed every step given in http://prsync.com/oracle/custom-xpath-function-in-bpel--7718.even after configuring jdeveloper,the custom function is nt there in the list of functions.also if anyone can explain the functionality of the mapping(what each element is doing) given in PreBuiltExtensionFunctions.xml file.thanx.
.When I remove entry from $ORACLE_HOME/bpel/system/config/xpath-functions.xml . (
<function id="getTimeDifference" arity="2">
<classname>ajr.TimeDifference</classname>
<comment>
<![CDATA[The signature of this function is <i>ajr:getTimeDifference(time1, time2)</i>.
The arguments to the function:
<ol type="1">
<li>time1 - String or element containing the datetime of the start of the interval</li>
<li>time2 - String or element containing the datetime of the end of the interval</li>
</ol>
Returns: an XML duration formatted string]]>
</comment>
<property id="namespace-uri">
<value>http://ajr/utilities/xpath</value>
<comment>Namespace URI for this function</comment>
</property>
<property id="namespace-prefix">
<value>ajr</value>
<comment>Namespace prefix for this function</comment>
</property>
</function>)
Everything works fine!
Deploying to http://localhost:8888 domain: default. Please wait....
[10:37:58 AM] Please check Ant log to determine whether the project deployed successfully. -
XPath function orcl:query-database usage
According to the limited documentation I can find for this XPath function, I should be able to return a nodeset enclosed in xml elements -
"Returns a node-set by executing the sql-query against the specified database. The second parameter rowset indicates if the rows should be enclosed in a element. The third parameter row indicates if each row should be enclosed in a element."
However, whatever second and third parameters I pass in to this function, it always returns a single string consisting of the selected fields and rows concatenated together.
Does anyone know how (or if) I can use this function to return a resultset as an XML nodeset? (All the examples I've been able to find for this function set the second & third parameters = false())Try this example (it uses internal orabpel table):
orcl:get-content-as-string(orcl:query-database('select id, process_instance from bpel_variable_sensor_values where id < 30',true(),true(),'jdbc/BPELServerDataSourceWorkflow'))
it generates something like this (string):
<ROWSET> <ROW num="1"> <ID>23.0</ID> <PROCESS_INSTANCE>21.0</PROCESS_INSTANCE> </ROW> <ROW num="2"> <ID>25.0</ID> <PROCESS_INSTANCE>21.0</PROCESS_INSTANCE> </ROW> <ROW num="3"> <ID>27.0</ID> <PROCESS_INSTANCE>21.0</PROCESS_INSTANCE> </ROW> <ROW num="4"> <ID>29.0</ID> <PROCESS_INSTANCE>21.0</PROCESS_INSTANCE> </ROW> </ROWSET>
or define this element type in your wsdl file (or your xsd):
<element name="ROWSET">
<complexType>
<sequence>
<element name="ROW">
<complexType>
<sequence>
<element name="ID" type="string"/>
<element name="PROCESS_INSTANCE" type="string"/>
</sequence>
<attribute name="num"/>
</complexType>
</element>
</sequence>
</complexType>
</element>
and try to assign the output to variable of that type(without orcl:get-content-as-string). It should work. -
Suggest book on SAP HR Functional for beginners
Dear All,
Request you to suggest me a book for SAP HR Functional
for beginners.
Thanks in advance for the help.
Regards,
TaranjitBenefit Administration:
This section of the Implementation Guide (IMG) is where you set the SAP Benefits Administration component.
Here you enter in the system all the details of the benefit plans offered by your company.
Benefit Area:
Benefit areas allow you to have separate administration of different benefit plan pools. This division is primarily for administrational purposes and would not normally be used for eligibility
IMG Path: Personnel Management  Benefits  Basic Settings  Define Benefit Area
Assign Currency to Benefit Area:
In this step, you specify the currency for the benefit area
IMG Path: Personnel Management  Benefits  Basic Settings  Assign Currency
this step, you enter the providers of the benefit plans you offer.
This could be the Insurance company, or Health Maintenance Organization that receives the benefit plan costs
IMG Path: Personnel Management  Benefits  Basic Settings  Define Benefit Providers
In this step, you set relevant benefit area for your Customizing activities
If you have more than one benefit area to set up, you must set up each independently. After you have set up all the plans in one area, you must return to this view, set the next current benefit area and work through the IMG again, setting up the new benefit area.
IMG Path: Personnel Management  Benefits  Basic Settings  Set Current Benefit Area
Benefit Plan Types:
In this step, you enter the benefit plan types that you require for the plan categories predefined in the system.
The following plan categories are provided by MSD:
Health Plans
o Medical
o Dental
o Vision
Insurance Plans
o Basic Life
o Supplemental Life
o Accidental Death & Dismember
Savings Plans
o 403B
o 457
o PERS (Public Employees retirement Scheme for CP Benefit Plan) & TRS
(Teachers Retirement Scheme for TP Benefit Plan)
Flexible Spending Accounts
o Health care
o Dependent care
IMG Path: Personnel Management  Benefits  Basic Settings  Plan Attributes  Define Benefit Plan Types
Define Benefit Plan Status:
It is important that you assigning statuses in order to be able to control the availability of plans with a minimum of effort. For example, you can control whether or not employees can enroll in a plan simply by changing its status
IMG Path: Personnel Management  Benefits  Basic Settings  Plan Attributes  Define Benefit Plan Status
Benefit Plan Status:
In this step, you define parameter groups. You decide which groups you require in two stages:
1. You consider which costs, credits, coverage and employee and employer contributions for your plans vary according to the age, salary and/or seniority of employees (or possibly the age of the employee's spouse).
2. You determine the different ways in which you need to divide your employees according to different value ranges for these criteria.
It is not possible to define overlaps of ranges for a criterion within a single parameter group. Therefore, if you require different employee groupings for different plans, you need to create a separate parameter group.
For each unique combination of criteria and their values, you need to define a parameter group.
In this step, you simply create the parameter groups to which you assign groups for the individual criteria in the following steps. You later refer to the parameter groups, where applicable, in the individual rule variants for plans. Since one parameter group can be referenced by multiple plans, Customizing effort is kept to a minimum. In the plan variant, you also have the flexibility of being able to specify that you only want to use certain criteria values belonging to a parameter group, for example, age ranges
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employee Criteria Groups  Define Parameter Groups
Age Groups:
In this step, you define the age groups for the parameter groups that you defined in a previous step.
Depending on your needs, you may find for some parameter groups, you can leave out this step, if for example there is no requirement to differentiate between employees based on age
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employee Criteria Groups  Define Age Groups
Age Groups under Parameter grouping PAR1
Cost Groupings:
In the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, job classification, marital status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying costs for different groups of employees
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Cost Groupings
Coverage Groupings:
In the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, employment contract, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying coverage for different groups of employees
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Coverage Groupings
Employee Contribution Groupings:
In the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employee Contribution Groupings
the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employer Contribution Groupings
the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Employer Contribution Groupings
the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Options for Health Plans
Dependent Coverage Options:
In this step, you define the dependent coverage that are used in health plans.
Define all possible variations that you need, because this view is not specific to any plan or plan option
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Dependent Coverage Options
Number of Dependents:
In this step, you can restrict participation in a health plan under a dependent coverage option to certain types of dependent, as determined by the subtypes of the Family/Related Persons infotype (0021). You can also define a minimum and maximum number of persons of a particular type that can be covered. During enrollment, the system only includes those dependent coverage options in the benefit offer for which the appropriate dependents are available
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Minimum and Maximum Number of Dependents
Define Cost Variants:
In this step you define cost variants to determine which factors influence the cost of a health plan for an employee. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual costs in this step. You simply define how costs vary according to:
Plan
Option
Dependent coverage
Employee data
Before you start to define cost variants, you need to do the following:
1. Determine how often costs vary for all the combinations of option and dependent coverage that you have defined in each plan.
This indicates how many cost variants you need. You can use the same cost variant more than once, for example, if costs are always identical for the dependent coverages 'employee only' and 'employee plus family' within a plan, regardless of the plan option
2. Determine how costs vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Cost Variants
Cost Rules:
You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Cost Rule
Health Plan Attributes:
In this step, you bring together all the definitions relevant to the health plan that you have made in the previous steps.
You assign to each health plan:
Its options
Relevant dependent coverages
The cost variants for the combination of options and dependent coverages
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Assign Health Plan Attributes
Insurance Plans:
In this step, you define general data for insurance plans
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Insurance Plan General Data
Coverage Variants:
In this step, you define coverage variants to determined which factors influence the coverage an employee is entitled to in a plan. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual coverage in this step. You simply define how coverage varies according to:
Plan
Coverage option
Employee data
Before you start to define coverage variants, you need to do the following:
1. Determine how often coverage varies for different coverage options.
This indicates how many coverage variants you need. Note the following:
If a plan has set coverages (including salary multiples), you need a
coverage variant for each.
If a plan allows employees to choose any amount of coverage within a
range, you need only one coverage variant.
If a plan has options, you will need a coverage variant for each option.
2. Determine how coverage varies according to employee data.
This determines how you need to set up your variants using employee groupings. For each variant, you can specify a parameter group and coverage grouping to determine coverage
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans 
Coverage Rules:
In this step, you define the actual coverages for a plan.
You need to define coverage for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
Coverage can be defined as a flat amount or as a factor of salary
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Coverage Rules
Cost Variants:
In this step you define cost variants to determine which factors influence the cost of an insurance plan for an employee. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual costs in this step. You simply define how costs vary according to:
Plan
Coverage option
Employee data
Before you start to define cost variants, you need to do the following:
1. Determine how often cost varies for different coverage options:
If an insurance plan has set flat coverage options and flat costs, you need
to define a cost variant for each flat cost.
If you have set flat coverage options and the flat costs are directly
proportional to the coverage stated in the flat cost, you need only one
cost variant.
If an employee can choose any amount of coverage within a range and the
cost of the coverage is directly proportional to the coverage, you need
only one cost variant.
2. Determine how costs vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Cost Variants
Cost Rules:
You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Cost Rules
Insurance Plan Attributes:
In this step, you bring together all those parts of an insurance plan, that you have already defined in the previous few steps.
You define the insurance plan options, then associate to each insurance plan:
Cost variant
Coverage variant
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Assign Insurance Plan Attributes
Combined Coverage Limits:
When you define coverages for plans such as insurance, you can set limits on the coverage amount. This is often used when the coverage is an amount dynamically calculated when the employee chooses her coverage.
However these limits apply only to one plan and yet you might need to define limits which combine the coverages of more than one plan.
In this chapter, you define these combined limits as follows:
1. The limit that might span 2 or more plans is reduced to a mathematical equation, where there is an amount on one side and plan coverages on the other side. The two sides of this equation are then DIVIDED BETWEEN the two views in this chapter.
2. The first view defines the limit in monetary terms which is one side of the equation. It also defines the operator (equals, is greater than, and so on).
3. The second view defines the other side of the equation in terms of the plan coverages
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Combined Coverage
Combined Coverage Limit Expressions:
In this step, you enter the second half of the equation, as discussed in combined coverage
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Define Combined Coverage Limit Expressions
Imputed Income for Selected Benefits:
In this section of the IMG, you define the criteria needed to calculate Imputed Income.
Imputed Income is based upon benefits paid for by the employer and calculated using rates set by the Internal Revenue Service (IRS). This value is then treated as taxable income for the employee
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Review Age Groups for Imputed Income
Review Calculation Factors for Imputed Income:
In this step, you check that the Imputed Income Rate Table entries are correct.
The imputed income age groups are associated with the rates/factors set by the IRS
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Review Calculation Factors for Imputed Income
Savings Plans:
In this step, you define general data for savings plans.
You have defined the relevant type, status, and provider for each plan in the Basic Settings section of the Benefits IMG
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Savings Plan General Data
Employee Contribution Variants:
In this step you define employee contribution variants to determine which factors influence the permitted employee contribution to a plan. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual contributions in this step. You simply define how contributions vary according to:
Plan
Option (only for plans in the plan category Miscellaneous)
Employee data
Before you start to define variants, you need to do the following:
1. Determine how often employee contributions vary for plans and any plan options.
This indicates how many contribution variants you need.
2. Determine how employee contributions vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and employee contribution grouping to determine employee contribution
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employee Contribution Variants
Employee Contribution Rules:
In this step, you define the employee contribution limits for each plan.
You need to define employee contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
You can define minimum and maximum employee contribution in the following ways:
As a fixed amount
As a percentage of salary
As a contribution unit
In Payroll, the total employee contribution is the sum of these amounts
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employee Contribution Rules
Employer Contribution Variants:
In this step you define employer contribution variants to determine which factors influence the contribution the employer makes to a plan. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual contribution in this step. You only define how contributions vary according to:
Plan
Option (only for plans in the plan category Miscellaneous)
Employee data
Before you start to define variants, you need to do the following:
1. Determine how often employee contributions vary for plans and any plan options.
This indicates how many contribution variants you need.
2. Determine how employee contributions vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and employer contribution grouping to determine employer contribution
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employer Contribution Variants
Employer Contribution Rules:
In this step, you define limits for the contributions made by the employer to employee plans. You so this for each employer contribution variant for each plan.
You need to define employer contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
You can define the employer contribution and the contribution limit in either of the following ways:
As a fixed amount / as an amount per unit contributed by the employee
As a percentage of employee base salary or employee contribution
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employer Contribution Rules
Assign Savings Plan Attributes:
In this step, you complete the definition of savings plans by bringing together the relevant elements that you have already defined:
EE contribution variant
ER contribution variant
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Assign Savings Plan Attributes
Flexible Spending Accounts (FSAs):
In this step, you define general data for flexible spending accounts (FSAs).
Requirements
You have created the appropriate plan type , plan status, and benefit provider in the preceding steps
IMG Path: Personnel Management  Benefits  Plans  Flexible Spending Accounts (FSAs)  Define Spending Account General Data
Assign Spending Account Attributes:
In this step, you enter the details of your flexible spending accounts including contribution limits, an employer contribution variant (if required), and rules for the reimbursement of claims
IMG Path: Personnel Management  Benefits  Plans  Flexible Spending Accounts (FSAs)  Assign Spending Account Attributes
Flexible Administration:
In this chapter, you define the flexible aspects of your Benefits administration. You define the availability of plans to your employees, in terms of the plans themselves. You also define aspects of the enrollment process.
you enter parameters that apply to processing within an entire benefits area, including:
Open enrollment period dates
Default validity dates for adjustment/standard plan records
Advance availability of future plans
Dependent age limits
IMG Path: Personnel Management  Benefits  Flexible Administration  Define Administrative Parameters
Benefit Adjustment Groupings:
In this step, you define adjustment groupings. These groupings allow you to specify different adjustment permissions for different groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Benefit Adjustment Groupings
Benefit Adjustment Reasons:
In this step, you define adjustment reasons to control changes to employee enrollments according to company policy.
The adjustment reason types that you define here are assigned as subtypes of Adjustment Reasons records (infotype 0378) in HR Master Data. Since a record can only have one subtype, a new record must be created for every adjustment reason an employee experiences.
According to the adjustment concept, an employee can only make changes to her enrollments if she has an Adjustment Reasons record (infotype 0378) with the required adjustment reason as a subtype. The only exceptions to this are if changes are made during an open enrollment period or if an anytime adjustment reason is assigned to the plan type.
In addition to defining adjustment reasons for certain events that can trigger changes, you may also want to define a special adjustment reason to allow changes to plans at any time
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Benefit Adjustment Reasons
Adjustment Permissions:
In this section, you assign adjustment permissions to each benefit plan type for an adjustment reason and any adjustment grouping that you have defined.
Note that the elements for which you can define permissions are automatically determined by the system, dependent on the plan category
Health Plans:
In this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Health Plans
this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Insurance Plans
Savings Plans:
In this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Savings Plans
Spending Accounts:
In this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Spending Account
Programs:
In this section of the IMG, you define benefit programs and the eligibility restrictions and termination conditions for the plans within these programs.
Within a program, eligibility for plans can be determined on two levels:
Program groupings control eligibility on a high level (macro-eligibility) by allocating an employee a defined program, depending on his/her organizational and employment data.
Eligibility rules are optional and control eligibility on a low level (micro-eligibility) by determining whether an employee can participate in a plan within the relevant program. An employee must fulfill the conditions defined in the rule in order to be able to enroll. Eligibility rules are assigned to plans in programs by means of an eligibility variant.
First Program Grouping:
In this step, you define first program groupings. Later, you define programs for a combination of first and second program groupings.
Identical attributes are available for the setup of both the first and second program groupings, and they are therefore interchangeable. The fact that you determine macro-eligibility for a program using two dimensions means that you are able to make finer distinctions between groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Define First Program Grouping
Second Program Grouping:
In this step, you define second program groupings. Later, you define programs for a combination of first and second program groupings.
Identical attributes are available for the setup of both the first and second program groupings, and they are therefore interchangeable. The fact that you determine macro-eligibility for a program using two dimensions means that you are able to make finer distinctions between groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Define Second Program Grouping
Employee Eligibility:
In this section of the IMG, you define the criteria according to which you control eligibility for individual benefit plans within a benefits program (definition of micro-eligibility). You perform the following steps to set up eligiblity requirements:
You define eligibility grouping to identify groups of employees for whom
certain eligibility criteria apply.
You create eligibility variants, which you later use to link eligibility
rules to programs.
If necessary, you define dynamic eligibility conditions relating
specifically to actual hours worked/length of service, or zip codes.
You bring your definitions together in the eligibility rule, where you
can also specify further conditions for enrollment.
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Employee Eligibility  Define Eligibility Groupings
Eligibility Variants:
In this step, you define eligibility variants. These consist simply of an identifier and a description
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Employee Eligibility  Define Eligibility Variants
Eligibility Rules:
In this step, you define eligibility rules for the benefit plans offered by your organization. You define these rules for combinations of eligibility grouping and eligibility variant, thereby determining the eligibility conditions that will apply for different groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Employee Eligibility  Define Eligibility Rules
Participation Termination:
In this section of the implementation guide you define criteria for the termination of benefit plans
Termination Groupings:
In this section of the implementation guide you define criteria for the termination of benefit plans
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Participation Termination  Define Termination Groupings
Termination Variants:
In this step, you define termination variants. These consist simply of an identifier and a description
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Participation Termination  Define Termination Variants
Termination Rules:
In this step, you define termination rules. You define these rules for every combination of termination grouping and termination variant, thereby determining the coverage continuation periods and termination day that will apply for different groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Participation Termination  Define Termination Rules
Define Benefit Programs:
In this step, you define termination rules. You define these rules for every combination of termination grouping and termination variant, thereby determining the coverage continuation periods and termination day that will apply for different groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Define Benefit Programs
Dependent/Beneficiary Eligibility:
In this step, you define family member groupings and determine how family members are allocated to these groupings
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Family Member Groupings
Dependent Eligibility Rule Variants:
In this step, you define the dependent eligibility variants to which you want to assign dependent eligibility rules. You also specify whether you wish to use a family member grouping in the associated eligibility rule to restrict eligibility to types of family members with certain characteristics
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Dependent Eligibility Rule Variants
Dependent Eligibility Rules:
In this step, you define dependent eligibility rules to determine which types of family member are eligible as dependents. You then assign your rules to the appropriate plans by means of a rule variant in the step Assign Eligibility Rule Variant to Plan
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Dependent Eligibility Rules
Beneficiary Eligibility Rule Variants:
In this step, you define the beneficiary eligibility variants to which you assign beneficiary eligibility rules in the next step. You also specify the following:
Whether you want to use a family member grouping in the associated eligibility rule to restrict eligibility to types of family members with certain characteristics
Whether the following apply for plans to which the variant is assigned:
 The employee can be a beneficiary
 Contingency beneficiaries can be named
 Spouse approval is required if beneficiaries other than the spouse are to be amed (the system only takes this setting into consideration for plans of the category avings)
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Beneficiary Eligibility Rule Variants
Beneficiary Eligibility Rules:
In this step, you define beneficiary eligibility rules to determine which types of family member are eligible as beneficiaries. You then assign your rules to the appropriate plans by means of a rule variant in the step Assign Eligibility Rule Variant to Plan
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Beneficiary Eligibility Rules
Assign Eligibility Rule Variant to Plan:
In this step, you assign dependent eligibility variants and beneficiary eligibility variants to plans, thereby assigning the eligibility rules associated with these variants
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Assign Eligibility Rule Variant to Plan
COBRA Plans:
In this step, you specify which health plans that you have already defined in the system are COBRA-relevant.
When a clerk collects COBRA-qualified beneficiaries, the system only considers employee enrollments in the plans you select here as legitimate cases where COBRA must be offered to the employee
IMG Path: Personnel Management  Benefits  COBRA  Choose COBRA Plans
this step, you determine for which flexible spending accounts (FSAs) you will offer continuation of coverage under COBRA. You need to do this for each benefit area separately
IMG Path: Personnel Management  Benefits  COBRA  Choose COBRA Spending Accounts
Qualifying Event Coverage Periods:
In this step, you define the events that qualify individuals for COBRA coverage, and the periods of permitted coverage continuation for each qualifying event type. COBRA legislation states the following regarding coverage continuation periods:
In the case of Termination of employment and Reduction in working hours, only 18 months coverage must be provided. If qualified beneficiaries are determined to be disabled within 60 days of the COBRA event, they are entitled to a further 11 months of coverage, as are the other qualified beneficiaries who experienced the original event.
For all other qualifying events except Bankruptcy of employer, a qualified beneficiary is entitled to 36 months continuation coverage, and there is no extension provision for disability.
In the case of the event Bankruptcy of employer, the coverage continuation period is the life of the retired employee or retired employee's widow/widower. You therefore do not need to define a continuation period in this case.
IMG Path: Personnel Management  Benefits  COBRA  Define Qualifying Event Coverage Periods
Assign COBRA Events to Personnel Actions:
In this step, you define how the system recognizes COBRA-qualifying events from employee personnel actions (infotype 0000) records. You do this by creating a link between the two.
The only COBRA-qualifying event types that you assign to personnel actions are:
Termination
Death of employee
Reduction in hours
You need to assign these COBRA-qualifying event types since they are based on customizable entries in your HR master data and therefore cannot be delivered as standard.
When the system collects COBRA-qualified beneficiaries, it considers employee records within the date range you specify in two stages as follows:
1. The system searches for employee personnel action (infotype 0000) records. The COBRA qualifying events assigned to any personnel actions found are collected.
2. The system checks other employee infotype records for specific information which corresponds to COBRA-qualifying event types
IMG Path: Personnel Management  Benefits  COBRA  Assign COBRA Events to Personnel Actions
Notification and Payment Intervals:
In this step, you define details of COBRA administration for those states where state law concerning COBRA differs from federal law.
Federal regulations are reflected in the state settings for the District of Columbia, which is also the system default.
If you must comply with state regulations that differ from the federal regulations, you should create a new state entry. Otherwise, you can use the DC version for all employees, regardless of which state they reside in
IMG Path: Personnel Management  Benefits  COBRA  Define Notification and Payment Intervals
heck this one and let me know if there is anything else even arun has also given nice response so if u have any query pls revert back
6 -
Xpath function and XSLT reusability in OSB
Hi Experts,
I have xslt which using custome xpath functions and working fine in bpel layer.Can I reuse the same jar,xslt and with some configuration(http://eelzinga.wordpress.com/2010/05/10/oracle-service-bus-11g-using-custom-xpath-functions/) in the OSB layer? its urgent,please respond asap.
Thanx in advance.-AswiniI would think so... after all custom XPath is just Java static functions called from OSB... as long as you stick to the guidelines for method signature exposed here http://docs.oracle.com/cd/E21764_01/doc.1111/e15866/custom_xpath.htm#CBAFHDIJ you should be fine
-
Xpath expression for a custom SearchBoxEx WebPart to a DataFormWebPart
Hi all,
I have a custom search webpart that has asp controls that are used in my dataview (DataFormWebPart) for retreiving data. This data view has the xslt variable "Rows" with the following xpath expression:
<xsl:variable name="Rows" select="/dsQueryResponse/Rows/Row[
(contains(translate(@Title,'ABCDEFGHIJKLMNOPQRSTUVWXYZ','abcdefghijklmnopqrstuvwxyz'), translate($FilterName,'ABCDEFGHIJKLMNOPQRSTUVWXYZ','abcdefghijklmnopqrstuvwxyz')) or $FilterName = '')]"/>
*<ParameterBinding Name="FilterName" Location="Control(txtName)" DefaultValue=""/>
This webpart searchs for people by their name. For example:
search for:
jose
results:
jose luis escudero
jorge jose torres
Ok, it works fine there, but what if I want to search for: jose escudero. There won't be any results because the search xpath expressions has a contains function for what you write in the textbox control.
So I think it should be splited by " " and searchs for the each word in the @Title column of the data source.
I don't master xpath expressions so I don't know how to code a correct xpath expression for that, any idea? I would greatly appreciate any help. Thanks.Hi betozg31,
According to your description, the point is that your Xpath code put the “jose escudero” search keyword as a unitary string. So your search would not return any results. I think
if you want to search result using two or more keywords ,you need to deal with the keywords firstly. Separating from the “jose escudero” search keyword , getting “jose” search keyword and “escudero” search keyword. Here is a simple code you
can have a look:
<xsl:if test="$FilterName =' ' ">
<xsl:variable name="Rows" select="/dsQueryResponse/Rows/Row[ $FilterName=' ']"/>
</xsl:if>
<xsl:variable name="FormatFN" select="lower-case(normalize-space($FilterName))"/>
<xsl:variable name="FormatT" select="lower-case(@Title)" />
<xsl:if test="matches($FormatFN,' ')">
<xsl:variable name="FilterNameBefore" select="substring-before($FormatFN,' ')"/>
<xsl:variable name="FilterNameAfter" select="substring-after($FormatFN,' ')"/>
<xsl:variable name="Rows" select="/dsQueryResponse/Rows/Row[ contains(contains($FormatT, $FilterNameBefore),$FilterNameAfter )]"/>
</xsl:if>
<xsl:if test="not(matches($FormatFN,' '))">
<xsl:variable name="Rows" select="/dsQueryResponse/Rows/Row[ contains($FormatT,$FormatFN)]"/>
</xsl:if>
Hope this helps!
Best Regards,
Eric
Eric Tao
TechNet Community Support -
OSB: class not found in custom xpath function
Hi,
This week I was struggling with custom xpath functions in OSB. First I created a jar file that contained the class and the complete functionality including logging. It contains a class that does a DVM Lookup from the database. As a standalone function, called from JUnit test cases it functions perfectly. I use Apache commons logging with the libraries from the Weblogic installation.
But when I put this OSB Util Services jar in the osb-home/config/xpath-function, it turns out that somehow the Weblogic Console gets a conflict with the commons-logging libraries. So I deployed it just as an application library in weblogic console, to solve this breakage.
Then I created a simple separate class that only calls the method in the deployed library. I packaged that as a custom-osb-functions.jar for the osb-home/config/xpath-function. I managed to get if visible in OEPE. But when I test the xquery transformation resource on the server, I get:
Error executing the XQuery transformation: {http://www.bea.com/wli/common/xquery}XQueryException: Error invoking custom xquery java function: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.wli.sb.stages.functions.XQueryExternalFunction.execute(XQueryExternalFunction.java:111)
at com.bea.wli.sb.stages.functions.XQueryExternalFunction.init(XQueryExternalFunction.java:61)
at weblogic.xml.query.iterators.FirstOrderIterator.open(FirstOrderIterator.java:169)
at weblogic.xml.query.runtime.typing.SeqTypeMatching.open(SeqTypeMatching.java:129)
at weblogic.xml.query.iterators.FirstOrderIterator.open(FirstOrderIterator.java:167)
at weblogic.xml.query.runtime.core.ExecutionWrapper.open(ExecutionWrapper.java:58)
at com.bea.wli.common.xquery.iterators.XQueryVariableMapper.getObjects(XQueryVariableMapper.java:459)
at com.bea.wli.common.xquery.iterators.XQueryVariableMapper.getObjects(XQueryVariableMapper.java:447)
at com.bea.wli.sb.test.transform.XQueryProcessor.invoke(XQueryProcessor.java:165)
at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(Unknown Source)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:252)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: java.lang.NoClassDefFoundError: nl/darwin-it/osb/dvm/DomainValueMap
at nl.darwin-it.osb.xpath.DomainValueMapLookup.lookupDVM(DomainValueMapLookup.java:35)
... 28 more
Caused by: java.lang.ClassNotFoundException: nl.darwin-it.osb.dvm.DomainValueMap
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
... 29 more
Can any one explain to me how I can get the OSB Util Services jar library in the same classpath as the custom-xpath-functions jar, without having it put along the custom-xpath-functions jar in the osb-home/config/xpath-functions folder (since that somehow breaks the weblogic console)?
How does the OSB classpath/classloading mechanisms work in this?
Thanks in advance,
Regards,
MartienI am running the plugin registration utility but it generates the error mentioned below. I have verified the structure of my zip file and the structure of zip file is:
-> SelfRegisterUserCustomValidator.zip
->Plugin.xml
->/lib/SelfRegisterUserCustomValidator.jar
->/resources/
Following our contents of plugin.xml:
<?xml version="1.0" encoding="UTF-8"?>
<oimplugins>
<plugins pluginpoint="oracle.iam.request.plugins.RequestDataValidator">
<plugin pluginclass= "com.infotech.tra.CustomValidator.SelfRegisterUserCustomValidator" version="1.0.0" name="SelfRegisterUserCustomValidator">
</plugin>
</plugins>
</oimplugins>
Following is the error being generated:
Enter name (complete file name with path) of the plugin file:
/u01/oracle/Middleware/Oracle_IDM1/server/plugin_utility/SelfRegisterUserCustomValidator.zip
[java] Java Result: 1
[echo] Exception in thread "main" java.lang.NoClassDefFoundError: oracle/iam/platformservice/utils/PluginUtility
[echo] Caused by: java.lang.ClassNotFoundException: oracle.iam.platformservice.utils.PluginUtility
[echo] at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
[echo] at java.security.AccessController.doPrivileged(Native Method)
[echo] at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
[echo] at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
[echo] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
[echo] at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
[echo] Could not find the main class: oracle.iam.platformservice.utils.PluginUtility. Program will exit.
Maybe you are looking for
-
Error in installing TREX 7.0 (NW 2004s SR1 Stack)
Hi Experts, Here the error i am getting in the last step of instillation: INFO 2006-12-13 15:25:27 Output of C:\DOCUME1\ADMINI1.BTI\LOCALS~1\Temp\sapinst_exe.1028.1166003304\SAPCAR.exe -x -v -g -i -R D:\usr\sap\NRX\SYS\exe\nuc\NTI386\Python -f "F:\NW
-
Cannot use "convert to PDF" even though I'm subscribed
I am subscribed to Adobe PDF pack (I am correctly signed in using the right profile, and the subscription is showing in my account in the Adobe app). When I click on the convert to PDF button in order to convert a Word file to PDF a query box appear
-
serial cable working well but when i connected serial cable to my circuit board it can not take data from my my microcontroller in which i burn a program and that program should display on the lab view example basics serial read and write but it is n
-
Error Activating DTP - error stack versioning
Hello Gurus, I am trying to activate a DTP, which has gone inactive , not sure of what reason. When I try activating it, message pops up saying the Error Stack needs to be cleared. I tried to display the error stack, but no options to delete data in
-
VoiceOver user needs help with reminders
I am using VoiceOver and I need help setting up a reminder. I type the name and then go into the details to have it remind me on a day and I can't seem to control what day and time it reminds me on. It always defaults to the top of the next hour. How