b2b commandline publishandimport overrides b2b keystore location and password in b2bconsole

(Doc ID 2389292.1)

Last updated on APRIL 20, 2018

Applies to:

Oracle SOA Suite - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.1.2.0 version, B2B Engine

ACTUAL BEHAVIOR
---------------
B2B wallet location getting changed while migrating one or more agreements from test to production.

The following command line is used for import:

ant -f $ORACLE_HOME/bin/ant-b2b-util.xml b2bconfig -Dmode=publishandimport
-Dexportfile=/refresh/home/Desktop/Agreements/SingleAgreement.zip
-Dconfigplan=/refresh/home/Desktop/Agreements/SingleAgreement.xml
-Dgeneratedexportfile=/refresh/home/Desktop/Agreements/SingleAgreementNEW.zip
-Ddebug=true -Djava.naming.provider.url=t3://xxxxxxx:7003
-Djava.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
-Djava.naming.security.principal=weblogic
-Djava.naming.security.credentials=xxxxxx -Dexitonerror=true


Reference of such commandline is here:

https://docs.oracle.com/middleware/1221/b2b/b2b-ug/GUID-85F9C458-FC91-44D3-95E9-5741DCE03388.htm#XBBUG-GUID-7B640C4A-720E-4414-A573-8412ED4B9E2A

EXPECTED BEHAVIOR
-----------------------
Importing single agreements from commandline should not change the keystore locations.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users had to manually intervene and change the keystore location back to previous one after each commandline import.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms