Conver the xslt element to comma seperated value output

Transformation:

<xsl:template match="/">

    <tns:Input>

      <tns:STATUS>

        <xsl:variable name="set" select="/ns0:Root-Element/ns0:STATUS"/>

        <xsl:variable name="count" select="count($set)"/>

        <xsl:for-each select="/ns0:Root-Element/ns0:STATUS">

          <xsl:variable name="i" select="position()-1"/>

          <xsl:value-of select="concat(/ns0:Root-Element/ns0:STATUS[$i+1]/text(),',')"/>

        </xsl:for-each>

      </tns:STATUS>

    </tns:Input>


Input:

<Root-Element>
<STATUS>X</STATUS>
<STATUS>Y</STATUS>
<STATUS>Z</STATUS>
</Root-Element>

Output:

<Input>
<STATUS>X,Y,Z</STATUS>
</Input>

jdeveloper(unable to deploy) taking long time to deploy the projects which are migrated from older version to new ..

Problem :

When we are trying to deploy the the project which are migrated from older version of jdeveloper (1.5 to 1.6) to new version it not deploying as expected.

It shows deploying for long time but never deployed to the environment


Fix:

1)create the project with the same name as the project which not gettting deployed (example:project) from jdeveloper

2)Navigate to the local folder where new project is created, and copy JPR file (example:Project.jpr)

3) Now navigate to the local folder for the project which not getting deployed .

4)Replace the old jpr with new jpr file,note both should of same name Project.jpr

5)Now deploy the project ,issue will be resolved!!!


Cheers,
Ram.

Unable to Restart the Humantask From EM console (oracle.mds.exception.MDSExceptionList:MDS-01329)

Problem:

Recently our MDS connection moved to the new location,After that Human-task which are deployed in Dev environment were down when i tried to restart i am getting the below exception :

oracle.mds.exception.MDSExceptionList:MDS-01329: unable to load element "persistence-config"

MDS-01370: MetadataStore configuration for metadata-store-usage "mstore-usage_6" is invalid.

Reason:

This is due to the ear files which are deployed is still point to the old MDS server location(we know that recently the MSD location got changed ). We need to change that in adf-config.xml file point to new server location and redeploy the application .it will avoid the error in future.

Steps to Resolve:

1)Open the Application Resources navigator in jdeveloper.

2)expand" Descriptors ---->ADF Meta-INF" Folder

3)click on the adi-config.xml file and enter the new server name and service name with proper username and password as shown in the screenshot below

4)redeploy the application .it will solve the issue

 

BPM MDS Connection Error -BPM-80102: Error while creating the security service

Hi ,

I faced the following issue while creating the MDS connection in BPM while following the BPM cook book.

Test Failed: BPM-80102: Error while creating the security service.  Cause: access denied (oracle.security.jps.service.policystore.PolicyStoreAccessPermission Context:APPLICATION Context Name:OracleBPMComposerRolesApp Actions:getApplicationPolicy)

Solution:

When I Checked the BPM-MSD log it says that "oracle.bpm.pml.security.exception.PmlSecurityException: BPM-80102: Error while creating the security service."

Steps to resolve:

1) Go to the Middleware Home location, for my case it’s under Following location

2) C:\Oracle\Middleware-->user_projects-->domain-->SOAdomain(Domain name specific to your Domain)-->config-->fmwconfig

2) Open the system-jazn-data.xml file under fmwconfig folder

3) Edit "system-jazn-data.xml" file, add the following grant. 

 <grant>
            <grantee>
                <codesource>
                    <url>file:${soa.oracle.home}/soa/modules/oracle.bpm.runtime_11.1.1/oracle.bpm.pml.security.jar</url>
                </codesource>
            </grantee>
            <permissions>
                <permission>
                    <class>oracle.security.jps.service.policystore.PolicyStoreAccessPermission</class>
                    <name>context=APPLICATION, name=*</name>
                    <actions>createAppRole,removeAppRole,addPrincipalToAppRole,removePrincipalFromAppRole,grant,revoke,getApplicationPolicy</actions>
                </permission>
                <permission>
                    <class>oracle.security.jps.service.policystore.PolicyStoreAccessPermission</class>
                    <name>context=APPLICATION, name=OracleBPMProcessRolesApp</name>
                    <actions>createAppRole,removeAppRole,addPrincipalToAppRole,removePrincipalFromAppRole,grant,revoke,getApplicationPolicy</actions>
                </permission>
                <permission>
                    <class>oracle.security.jps.service.policystore.PolicyStoreAccessPermission</class>
                    <name>context=APPLICATION, name=OracleBPMComposerRolesApp</name>
                    <actions>createAppRole,removeAppRole,addPrincipalToAppRole,removePrincipalFromAppRole,grant,revoke,getApplicationPolicy</actions>
                </permission>
                <permission>
                    <class>oracle.security.jps.JpsPermission</class>
                    <name>VerificationService.createInternalWorkflowContext</name>
                </permission>
                <permission>
                    <class>oracle.security.jps.service.credstore.CredentialAccessPermission</class>
                    <name>credstoressp.credstore.WF-ADMIN-USER.WF-ADMIN-CREDENTIAL</name>
                    <actions>read,write</actions>
                </permission>
            </permissions>
        </grant>

4)Restart the server it will solve your issue 

Unable to Login BPM Workspace

Hi ,

Problem:

I was facing the issue in logging to BPM work space,I was able to logging in to EM and Console with same Password but I faced issue with BPM Workspace .

I have BPM and SOA both are running on the same server,still i am unable to log in its says invalid user name password

Solution :

1.     1)Login to console as an Administrator

2.     2)Click on the server under environment in Domain Structure Panel on the left hand side.

3.     Then choose the Server where the BPM is hosted (For my case it admin server)

4.     In the listen address, type your complete machine name then restart your server it will solve the issue.(Note :even I faced the issue if mention here as localhost )