Problem in Connectors in GRC AC 5.3

Hello all,
While we are creating the connector in RAR the JCo destinations are not visible. In the drop down list of JCo destinations we are able to see the Value as <Host Name>_<null>_<Client Number>   For Eg: GRRDEV_NULL_200 i am not able to see the JCo destinations which we activated in Java content administration
We have installed the latest patch SP18 and using the HR Module also.
What could be the cause?
Activated: JCo Destinations
VIRSAHR_MODEL & VIRSAHR_METADATA
VIRSAHR_01_MODEL & VIRSAHR_01_METADATA
*VIRSAHR_02_MODEL & VIRSAHR_02_METADATA *
Thanks in Advance.
Regards,
Kumar Rayudu

Hello Kumar,
Yes, you can use "VIRSAXSR3_01_METADATA" and "VIRSAXSR3_01_MODEL JCo destinations for HR backend. As mentioned by our friends in this thread it doesn't matter what kind of backend you use. You can still use these JC0 destinations.
With these JCo(Adaptive RFC connection) destinations, maximum number of system one can connect are 15. If you have more than 15 systems it is recomended to use SAP JCO connector type for RAR.
SAP JCo connector doesn't have any limitation like JCo(Adaptive RFC).
Hope this answers your question.
Best Regards,
Sirish Gullapalli.
Edited by: Sirish Gullapalli on Jul 28, 2009 12:03 AM

Similar Messages

  • Connector from GRC 5.3 to IDM failed

    Hi,
    In our landscape, we had a requirement to connect GRC 5.3 (RAR) and our IDM UI (NW 7.0 EHP1). The connector type is defined as 'Web Service' connector. But the connection fails with the following error
    WARNING: Cannot get data extractor forD2H.  Reason:D2H/D2H
    com.virsa.cc.dataextractor.dao.DataExtractorException: D2H/D2H
            at com.virsa.cc.dataextractor.bo.DataExtractorSAPPORTAL.init(DataExtractorSAPPORTAL.java:98)
    There was no EP component installed on our IDM UI (SID : D2H). Hence i had installed EP components and the VIRPERTA (RTA of Enterprise Portal) in our IDM system.
    Now when i create a connector in GRC system with the following webservice
    http://<IDMhost>:<port>/CCRTAWS/Config1?wsdl&style=document the connector fails. But the Web service URL works fine returning an XML page.
    Can anyone please help here???
    Regards,
    Ragav

    Hi,
      The migration utility is very simple. You install it on GRC 5.3 box and then select the items you want to migrate. It will generate tab limited text files and you can use those files to import data into 10.0 box.
    Regards,
    Alpesh

  • Problem with connector for ABAP Webdynpro

    Hello,
    I have a problem with a new Business Package :
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/com.sap.pct/specialist/com.sap.pct.erp.instructor.bp_folder/com.sap.pct.erp.instructor.roles/com.sap.pct.erp.instructor.instructor/com.sap.pct.erp.instructor.instructor/overview/com.sap.pct.erp.instructor.work_overview/com.sap.pct.erp.instructor.work_overview/com.sap.pct.erp.instructor.instructor_worklist
    Component Name : com.sap.portal.appintegrator.sap.WebDynpro
    I think the problem is coming that I have no customized the connector with good values. Do you know a good blog or document to create a system alias dedicated to abap wedynpro or its bsp ?
    Regards,

    Yes, the UserId is the same in the portal and the BackEnd.
    Previously we used the ITS for our ESS and now we are using the Portal, so all have an UserId and all personal have the same Id as before.
    The first month it worked fine but when the password went out, in Back End, after 30 days, the question for login information appeared.
    Regards
    Ingvar

  • Problem deploying connector: META-INF/ejb-jar.xml not found in jar file

              Has anyone seen this problem:
              I built Sun's Blackbox implementation and packaged
              it identical to the BlackBoxNoTx.rar included with
              Weblogic's 'jconnector' sample (even using the same
              ra.xml and weblogic-ra.xml). When I try to deploy
              it, the server reports:
              java.io.FileNotFoundException:
              META-INF/ejb-jar.xml not found in jar file
              I have no idea why the server thinks my connector
              is an EJB. If I deploy the BlackBoxNoTx.rar included
              with the sample, everything works without a hitch.
              The only variable that I'm changing in my BlackBoxNoTx.rar
              is that I build the Blackbox classes myself--otherwise,
              the RAR packagings are identical. Any assistance is
              greatly appreciated since I'm banging my head against
              a wall...
              Thanks,
              -jason
              

              I was finally able to resolve this one. On the odd chance that someone else encounters
              the same problem, here's what went wrong:
              My RAR file had two directories: 'META-INF' and 'meta-inf'. The first was created
              by the jar tool and contained the manifest.mf file. The second I created manually
              and it contained my ra.xml and weblogic-ra.xml. When I examined the RAR using
              any tools or I extracted the contents, it looked like it only contained one directory:
              META-INF (because NT is case-insensitive).
              "Jason L" <[email protected]> wrote:
              >
              >Has anyone seen this problem:
              >
              >I built Sun's Blackbox implementation and packaged
              >it identical to the BlackBoxNoTx.rar included with
              >Weblogic's 'jconnector' sample (even using the same
              >ra.xml and weblogic-ra.xml). When I try to deploy
              >it, the server reports:
              >
              >java.io.FileNotFoundException:
              >META-INF/ejb-jar.xml not found in jar file
              >
              >I have no idea why the server thinks my connector
              >is an EJB. If I deploy the BlackBoxNoTx.rar included
              >with the sample, everything works without a hitch.
              >The only variable that I'm changing in my BlackBoxNoTx.rar
              >is that I build the Blackbox classes myself--otherwise,
              >the RAR packagings are identical. Any assistance is
              >greatly appreciated since I'm banging my head against
              >a wall...
              >
              >Thanks,
              >
              >-jason
              

  • Error while creating new connector in GRC CUP 5.3

    Hi,
    I am  trying to create a new SAP Connector in CUP 5.3, when i fill in all the fields in the new connection and select  "Test Connection" it says Connection successful and when i save it and look at the Available connectors, i am unable to see my new connector there.
    Does anyone know why is this happening.
    a quick response is appriciated.
    Thanks.
    Edited by: Chaitanya Pallapotu on Jul 14, 2009 9:17 PM

    Hi Chetan,
    I have the same issue when configuring connectors in CUP. I solved it in this way:
    1- Go to RAR(Risk, Analysis and Remediation) --> Configuration --> Connector --> Search
    2- Select one of the connectors and write down the values in the list box of the field JCO Destination.
    3 - Now, go to CUP, and create the connector using the names writed down in step 2.
    CUP will warn you with an error, ignore it,  and then save the connector.
    Note: when creating the connector in CUP, fill the fields, then save/create(here you will have the error msg), then Test Connection, and then save again.
    That works for me!!!
    PD: Always log in to GRC with the same language configured in CUP.
    Hope this works for you!!!

  • Problem with Connector Pins??

    Since Wednesday, I've had this issue with either the cable or the connector pins. If the wire is connected to the iPhone and and I push the plug slightly, the phone will cease to charge and sync with the computer until I've stopped touching it.
    If I hold the phone at a certain angle, it again loses connection to the computer. Lose connection enough times and a pop up appears on my laptop saying something like "this device can perform faster on USB 2.0."
    So, is it a problem with the connector pins? I tested out the cables on a different comp in case it was a problem with the USB port and it did the same thing.
    Any opinion and/or help would be grateful.
    Thanks.
    P.S. I'll try to post a video of the problem.

    You can utilize any iPod cable. All the way back to iPod Nano's first model or maybe a few iPod classic models earlier than that. As long as the cable is USB 2.0 to iPod, it will work with connect and sync. You can't use FireWire to iPod however. FireWire doesn't have enough juice to sync devices except the first gen iPod era.
    If other iPod cables don't work with your iPhone syncing there may be a problem with the connector pins which you can have an Apple employee inspect or visit an AT&T store for a probable swapout.
    You can also purchase a battery case and utilize them for syncing. This replaces the iPod connector with Micro USB or Mini USB. You would connect your Mac/PC to the Micro/Mini USB and after it recognizes the new method, it'll know your iPhone and sync as well as charge your battery case.

  • Steps for replacing a connector in GRC CUP and RAR

    Hi All,  We have GRC 5.3 CUP and RAR installed and I would like to replace an existing connector PRD with one called PRD010.  Does anyone have the necessary steps to follow to perform this?  Your input is appreciated.

    Hi Sudip,
    Sorry I didn't clarify and thanks for responding.  This will be the same backend.  I want to change the connector name within the RAR and CUP config, etc.  I'm concerned about all the "tags" in the database tables pertaining to this connector name if you know what I mean.  It seems that when you make a change like this you end up with data in the database tagged with the old connector names which makes it difficult to clean out the old stuff unless maybe there is a proper sequence of steps to go thru.  Can it be just as simple as creating the new connector and then exporting and importing the rules with the new connector name?  Maybe I'm making this more difficult than it really is.
    Regards,
    Gary

  • Log Category problems deploying connector

    I am trying to use an andapter. But when WLI starts up, when it tries to
    initialize the connection pool it fails with the message:
    Error loading class com.connector.spi.ManagedConnectionFactoryImpl. Reason:
    log category hierarchy not found for context COM_CONNECTOR_1_0 with locale
    en_US
    I've verified that that Log context exists in the descriptor file,and that
    CountryCode is set to US in the ra.xml and weblogic-ra.xml files, and that
    the default Java locale is US.
    Any ideas appreciated.
    SB

    Yes, this is included in the classpath. I actually found out what the
    problem was - I was making a call to the logger after the
    ManagedConnectionImpl had been instantiated, but (I guess) before the super
    class had initialised the logging framework stuff. I made a call in one of
    the property setter methods. Removing this and it deploys, and I can make
    calls such as logger.debug(...).
    Problem I now have is that, even though the Log level is set to DEBUG, the
    debug statements do not produce any output.
    SB
    "Amit" <[email protected]> wrote in message
    news:[email protected]..
    Do you have your adapter jar file in the classpath ?
    Thanks
    Amit
    Dave Smith <[email protected]> wrote in message
    news:3c14da99$[email protected]..
    Did you ever get any resolution to this problem? I'm experiencing the
    same
    problem
    and can't seem find any information on it. Thanks.
    "Stanley Beamish" <[email protected]> wrote:
    I am trying to use an andapter. But when WLI starts up, when it tries
    to
    initialize the connection pool it fails with the message:
    Error loading class com.connector.spi.ManagedConnectionFactoryImpl.
    Reason:
    log category hierarchy not found for context COM_CONNECTOR_1_0 withlocale
    en_US
    I've verified that that Log context exists in the descriptor file,and
    that
    CountryCode is set to US in the ra.xml and weblogic-ra.xml files, and
    that
    the default Java locale is US.
    Any ideas appreciated.
    SB

  • Never met problem with connector

    Hi,
    I have the source and target on the same oracle instance but in different schema.
    Owb automatically creates the connector but when I try to validate it, I found this warning:
    VLD-3064: Owning and referenced locations of this connector are on the same database instance. Unless explicitly referenced in configuration settings, no generated code will use the database link resulting from deployment of this connector.
    What should I change to make it work?
    Please help me!
    Vieruzzo.

    Hi AP,
    thanks for help me.
    I have registered the location but when I try to deploy the mapping I found these warning:
    TIPO_MISURATORE_MAP Create Warning
    ORA-06550: line 26, column 3:
    PL/SQL: SQL Statement ignored
    TIPO_MISURATORE_MAP Create Warning
    ORA-06550: line 37, column 8:
    PL/SQL: ORA-00942: tabella o vista inesistente
    I don't understand why it don't found the table that are in a different schema but in the same database instance.

  • Problems Navigation Connector

    Hi,
    we have upgraded EP form NW04 SP14 to NW2004s SP10. We have an customer specific navigation connector which worked fine in the old portal, but the connector won't work in the upgraded version. The behavior is more than strange: we get the toplevel entries of the menu items from the navigation connector but not the according subitems. I have extended the navigation connector in a way that every time when get initial nodes is called I write the complete structure to the log file. The structure delivered by our navigation connector seems to be ok, all subitems are available. But the portal framework only displays the top level items.
    Have anyone had an issue like this before and an idea how to get the connector working as in the old enviroment?
    Thx and regards
    Lars

    Hi Hermes,
    when you upgraded from NW04 SPS14 to NW04S SP10 you will definetly have a change within the NavigationService esp. for the Caching machanism.
    You could try to call /irj/go/portal/prtroot/com.sap.portal.navigation.service.CacheAdministrator and check if caching is turned on for your own Connector.
    If it is turned on just turned it off. This affects you when your "listBinding" implementation returns different nodes for e.g. for different users and you have not implemented a CacheDiscriminator in your Connector, because the children list is cached for every navigation node  (key by default == nodeName. so one cache entry per node).
    Here is a link to the Navigation Cache in NW04s
    <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/43/015f0f8f726f70e10000000a11466f/frameset.htm">http://help.sap.com/saphelp_nw04s/helpdata/en/43/015f0f8f726f70e10000000a11466f/frameset.htm</a>
    Hope it helps,
    Frank

  • GRC AC Connectors

    Hello Experts,
    Is the following process correct for creating connectors for GRC AC 5.3:
    1. JCO connector (Meta & Model) is created for a system say P6E and client 100
    2. Using this, a system connector P6E100 is created in RAR
    3. A JCO destination is created with this name i.e., P6E100
    4. Now the system connectors are created for all other three components CUP, SPM, ERM with same JCO destination.i.e., P6E100.
    Is this process correct?
    Thanks
    Ram

    Hi Ram,
    Yeah this is exactly what we've done and it works.
    Best regards.

  • GRC 10 - Risk Analysis in legacy system

    Hi everybody,
    I have a problem with legacy connectors in GRC 10. I implemented the note 1594963. So, I created the legacy files and storage it in GRC server.
    When I run the user synch, the legacy connector only synch the first record.
    Someone can help me? Someone did implement a risk analysis for legacy systems?
    Regards,

    Hi  Claudio Ekel
    Can you share some inputs on the Legacy Risk Analysis.
    We have configured the Legacy Connector as per the note 1594963 ; Placed the files on the server & tried running Synchronization Jobs. But the data is not getting uploaded to GRC10 .
    We made sure that text files are in UTF-8 format
    Is it mandatory to load all the 11 files that are provided in the note 1594963? We have excluded the Profile related files
    Can you share a sample of Legacy file formats that you have used for the sync.
    Can you throw some light on what could be the possible issues for data not getting uplaoded to GRC10?
    Regards,
    Pavan Muthyala

  • Multiple rule sets - impacts in GRC modules

    Hi,
    We are currently running CC 5.2 on our European perimeter.  We would like to extend in the near future to our US perimeter.  For that, we have to take into consideration a complete new set of rules.
    I presume there will be no issue to handle multiple sets of rules in CC but I was wondering what could be the potential impacts/problems for the other GRC modules?
    i.e.: in Role Expert, for the US roles we would like to avoid getting potential risks from European rule sets,...
    Has anybody some attention points or good practice to share on that ?  It would be a great help for us.
    Thanks & Regards

    Different installation of GRC Solutions for different regions is certainly not recommended and not even required.  It is important to design your cross system landscape efficiently considering different regions in mind and create different rule sets for different regions. In a cross system landscape you can have multiple systems from different regions with entirely a different set of modules and data. Obviously the risk will be different, for that purpose you have to create different rule sets for sure.
    Now when you are performing risk analysis for a particular region you have to select the considered system/connector and a rule set respectively so that you get the risks on targeted system only.
    Bill-
    as you asked, if there are chances of potential impacts/problems for the other GRC modules or not,
    The answer is, There will be no impact at all because you are considering them as separate entities within a landscape. It is the beauty of GRC Access Controls to have multiple system connectors, logical systems and cross system landscape that provides almost every feature to cover all regional perimeters.
    Regards,
    Amol Bharti

  • GRC NFe 2.0 20 - Serviço de assinatura digital não acessível

    Senhores,
    Encontrei diversos post sobre esse problema, porem nenhum específico para o meu problema.
    Meu landscape é ECC 6.0 700 SP 22 (SAP_APPL 603 - SP 6 - SAPKH60306) -> GRC/PI SAP NetWeaver 7.0 (SLL-NFE - Release 100 - SP 0015/SAP_ABA - 700 SP 22).
    Apliquei inumeras notas no ECC e a princípio não aparece nenhum erro na j1bnfe nem na sxi_monitor do PI. Porem no monitor web GRC aparece a mensagem: 20 - Serviço de assinatura digital não acessível.
    Realizei testes na SM59 e todas as RFC comunicam sem problemas e na db97 estão apontados corretamente.
    Gostaria de saber se pode ser problemas de SP do GRC ou alguma outra coisa.
    Obrigado!

    Henrique, muito obrigado pela atenção.
    Acabei de aplicar a nota "0001498700 Problem on signing NF-e" e o problema mudou. Agora ja temos a mensagem no sxi_monitor e o erro no Monitor GRC ja é outro. Passa a ser "Problemas de processamento PI" e na mensagem do sxmb_moni conta a mensagem:
    SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Message interface is not used by this process</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Para a interface: SIGNN_SignNFe_OB. Vou tentar apagar e criar o cenário novamente, porem se souberes de alguma nota ou correção para isso, seria muito bom.
    Sobre a atualização de SP, devido ao curtíssimo prazo do projeto (7 dias para atualizar 1.0 para 2.0) estamos tendando buscar outras soluções, como por exemplo aplicação de notas em separado, se tiveres uma lista das que eu vou precisar seria muito bom... Obrigado!

  • GRC-NFe - Erro de assinatura de notas

    Amigos,
    Estou com o seguinte problema.
    A nota fiscal sai do ERP e chega no GRC, ficando com o seguinte status:
    status de erro = 20 Serviço de assinatura digital não acessível.
    Ao reinicializar a nota pelo o GRC está aparecendo a mensagem Erro na chamada RFC (NF-e 3509076119009600019255.
    Já verifiquei as conexões rfc e estão todos ok. O PI e o GRC estão instalados na mesma máquina, PI = 001 e GRC = 500.
    client 001
    SM59 rfc do tipo H -> XI_INTEGRATION_SERVER
    host euroXX porta 8001
    pref/caminh /sap/xi/engine?type=entry
    mandante 001
    user piappluser
    SXMB_ADM ->Configure Integration Server-> HUB servidor de integração
    dest://XI_INTEGRATION_SERVER
    client 500
    SXMB_ADM -> Configure Integration Server-> LOC sistema de aplicação
    dest://XI_INTEGRATION_SERVER
    SM59 rfc do tipo H ->NW1CLNT500
    host euroXX porta 8001
    pref/caminh /sap/xi/engine?type=entry
    mandante 500
    user pisuperr
    Esta rfc é utilizada dentro do Cenário SIGNN_WebAS_Outbound_SignNFe, para o communication channel WAS_XI_RCV
    do tipo XI, com Addressing Type HTTP Destination e HTTP Destionation = NW1CLNT500
    Alguém tem alguma dica do que pode estar errado?
    Abraços,
    Cláudio Argolo

    Bom dia Claudio,
    status de erro = 20 Serviço de assinatura digital não acessível.
    Veja estas duas threads:
    Status error 20 - Signature Service Unreachable
    'Signature Service Unreachable' error in the NFE system
    Ao reinicializar a nota pelo o GRC está aparecendo a mensagem Erro na chamada RFC (NF-e 3509076119009600019255.
    Este chamada de RFC é ao R/3 e não internamente, quando acontece um problema de assinatura, o GRC não tem como reiniciar, pois não tem todos os dados para enviar para o assinador, então é necessário pedir ao R/3 para reenviar.
    - Talvez esteja faltando uma nota no R/3. Veja se a SAP Note 1234054 foi aplicada (passos manuais para tornar a função J_1B_NFE_MS_REQUESTS_DATA RFC)
    - Se for nota em paralelo esquece. O R/3 também não tem mais estes dados.
    Atenciosamente,
    Fernando Da Rós
    Edited by: Fernando Ros on Jul 28, 2009 8:52 PM

Maybe you are looking for