Topic
  • 1 reply
  • Latest Post - ‏2016-09-07T18:23:00Z by KaranBal
Venkat Podatharapu
Venkat Podatharapu
75 Posts

Pinned topic security configuration error to connect to mdm server with Context

‏2016-09-01T21:43:54Z | data management master mdm-migration

Folks,

We have developed Java API to resolve tasks, when we run this in lower (Dev, QA) works fien with out any security error, but when we run in higher (prod) enviroemnt we are running into security issues and error message is below, 

 

Could you advise me what i am missing to call this java program from shell script with four parameters  $MDMUSER  $MDMPASSWORD $MDMHOST $MDMFILE

MDMFILE  has the data like MEMIDNUM, SROUCECODE, Shell script works fine in lower environments and not in prod,  below is the error

Context ctx = new Context(Host, 9080, MDMUSER, MDMPASSWORD);

 

 

 

Error :   ************************************

Sep 1, 2016 2:59:47 PM null null
SEVERE: com.ibm.websphere.management.exception.ConnectorException: com.ibm.websphere.management.exception.AdminException: Neither was.repository.root nor was.install.root are set
Sep 1, 2016 2:59:47 PM null null
SEVERE: JSAS1480I: Security is not enabled because the ConfigURL property file is not set.
Sep 1, 2016 2:59:47 PM null null
INFO: Client code attempting to load security configuration
Sep 1, 2016 2:59:48 PM null null
AUDIT: CHFW0019I: The Transport Channel Service has started chain HttpOutboundChain:localhost:9080.

 

******************************

http://www.errbay.com/?r=IBM-WAS-08.5&c=JSAS1480I , suggesting to set the 

 

AIX: -Dcom.ibm.CORBA.ConfigURL="file:/usr/IBM/WebSphere/AppClient/properties/sas.client.props"

 

Where i have to set this variable in properties file or in my Java Program.

 

thank you very much for your response.
 

  • KaranBal
    KaranBal
    227 Posts

    Re: security configuration error to connect to mdm server with Context

    ‏2016-09-07T18:23:00Z  

    The call says port 9080 which is http port but the post is in on security. That seems a little inconsistent. I would recommend checking the MDM logs to see why the incoming request was rejected. Maybe you have a setup where you can only do secure https communication and so http is rejected. Most of the security features are built in WAS, not MDM, and the logging may give additional information.