Creating Repository Services advice!
Hi All
I am currently looking into creating and developing Repository Services and I am have a little difficulty understanding basic code and structure. I have managed to alter examples which various people have helped me with but that is now not enough as my requirements grow!
So if anybody has any ideas, documents, tutorials, examples that will help I will be most grateful.
Cheers
Phil
Hi Phil,
There are many examples around the forum.
One, with links to some other examples is:
Looking for way to count a specific document hits(Not with Activity Report)
Apart from that (AFAIK),
There is no published documentation/tutorial for creating a Repository Service.
Hope that helps,
Yoav.
Similar Messages
-
Error while creating Repository Service in informatica
Hi Guys,
When i try to create repository service informatica8.1.1.I'm getting the below error
driverconnect.exe has encountered a problem and needs to close.We are sorry for the inconvenience.since your error message is not completely represented over here,my guess is you are not providing the exact repository name as what you mentioned during the installation.please chek the repository name that you provided
for example : during installation the defualt repository name might been 'PowerCenter' and you might be entering some other repository name while connecting i.e 'Oracle_BI_DW_Base' .
check this and let me known. -
I can't create repository service in Informatica
Hi All
Informatica Powercenter 8.6.1
I has try creating Repository Service in Informatica Powercenter Adminstration Console, but have error
The Service Manager could not start the service due to the following error:
Error - [PCSF_10342] Exception occurred: [Unable to start service [DB] on any node specified for the service.].
please help
best regards
saranporn Phutta
Edited by: user1108635 on 8 ก.ค. 2553, 19:36 น.hii all
i have Informatica 8.6.1 and oracle 10g
I has try creating Repository Service in Informatica Powercenter Adminstration Console, but have error
The Service Manager could not start the service due to the following error:
Error - [PCSF_10342] Exception occurred: [Unable to start service [DB] on any node specified for the service.].
I restarted my system and tried again the repository service..and also i turned off the firewall in my system....
but i have the same error...
so please help to my solve this problem.
thanks in advance..
shankar -
Creating repository service in informatica 8.6 takes too long
hi i have installed informatica server on windows vista and now loginto admin console and trying to create repository service using
configuration assistant .
i gave all the details database user/pwd /codepage/rep service name
it says
creating repository service (it may take few minutes)
its 40 minutes now and still not created
what might be the issue? the database user that i have specified is the same user for domain database. is that the problem ?
how long it will take to create the repository service?
regards
rajVista is not officially supported, there are some docs on workaround for Vista in Metalink3.
See some of these
http://technet.informatica.com/forum/installation-upgrades/topic/powercenter-install-error-vista
or for 8.6 see
http://technet.informatica.com/forum/general-discussions/topic/informatica-86-repository-service-configuration -
Informatica Admin Console hangs on Creating repository service......
Hello Gurus,
For some time now I have been trying to create a repository service using the Informatica admin console after I have installed Informatica PowerCenter 8.6.1 server and applied the server HotFix 11. I do provide all the correct credentials for the connection to the DB, this is inferred from the process initiation of the creation. It is just now that the creation process gets initiated but doesn’t end. It keeps running with no end. The following are the account privileges granted to the repository user on which the Informatica repository should be created:
grant dba,connect,resource,select any table, create table,create view,insert any table,delete any table,update any table to infadb_rep;
Note that I have granted a dba privilege to the user as a precautionary measure. Yet, the creation process doesn’t conclude. I have also noticed that no tables, views, procedures not even any objects whatsoever were created on this user. But I have noticed that the user could not be dropped (i.e locked) if the Informatica service is up (that is being discovered after losing hope with the creation process and closing the admin console window).
I just wanted to also note that the whole system is a Virtual machine having Windows Server 2003 SP2, having Oracle 11gDB installed with two Network Adapters ( loopback adapter with static IP 192.168.100.100 and an additional Network adapter with DHCP IP assignment attribute set). Therefore, it is to be noted that addressing the machine usually is done by using the machine name “WIN2K3”. I hope any of these details does not introduce conflicts as a setting.
Would most definitely appreciate the help.
Thanks you very much in advance,
HossamI was able to get it working when I gave the following grants:
resource
connect
create session
create any table
drop any table
update any table
select on v_$parameter
create any directory
dba -
Repository Service - Checking a custom property!
Hi All
I am trying to create repository that will check a custom property 'RepGroup' and then act on it if the the property contains a certan value. However I am not sure how to do this - does anyone have an example I could see?
Many Thanks
PhilHi Phil,
I understand that the information from:
Creating Repository Services advice!
wasn't enough.
What exactly are you missing?
Yoav. -
Error while creating Informatica Repository Service
I am installing OBIApps - Have done it previously so I know it is a complex installation.
This time my server is a Linux RH 64bit... Informatica server installed ok. Using the administrator panel, I am now trying to create the repository service.
I am getting error: Database driver event…Error occurred loading library [libclntsh.so.10.1: wrong ELF class: ELFCLASS32] Database driver event…Error occurred loading library [libpmora8.so]
I know the infra structure guys installed Oracle client 32bit... Maybe this is the trouble ?
I have LD_LIBRARY_PATH blank... if I point the LD_LIBRARY_PATH to the oracle client bin... it seems that informatica startup has trouble since administrator panel doesn´t start. went back to LD_LIBRARY_PATH blank and startup is ok and administrator is ok... but error in creating repository service persists...
I appreciate any hints.
Txs.
AntonioTry with by execute relink all libraries:
$relink all
or else go with 64bit -
I installed Informatica on Linux Cent OS Successfully, but when I am trying to create repository service its giving error of code page incompatibility.
My database code page is AL32UTF8.
So what code page should i select for repository service,it should be subset I don't know which one.
Please help
thanksI found the solution online,
it is ISO 8859-1 Western European -
How to develop a Repository Service to trigger a workflow automatically??
Hi All,
I have configured a approval workflow on the folder <b>/documents/test</b> in <b>KM Content</b>.
<b>I want to trigger this workflow automatically whenever a new document is created in this folder.</b>
How can i do it? Should i create a Repository Service? or is there any other way??
I can't find a lot of info about creating Repository Service. I have seen other threads in this forum too.
Can any1 plz help me in this regard?? <b>Any code samples???</b>
Would appreciate any kind of help. It's kinda urgent.
Thanks in advance.
<b>Regards,
Sai Krishna.</b>Hello Praveen,
thank you for answer and the link to the sap help.
sorry for my beginner questions, but in sap help in chapter "Setting up the J2EE Engine for Debugging" under number one "Start the Config tool and connect to the J2EE Engine database.".
Where will I find this config tool?
Regards,
Markus -
KM Repository Service for creating a folder structure
Hi All,
We have a requirement in KM. Whenever a folder is created inside a folder (say '/documents/testFolder') ... .. a couple of subFolders need to be created inside this new folder.
For example, if the new folder's name being created is <i>parentFolder1</i> then, the following structure shud be created inside this folder.
parentFolder1
|--> subFolder1
|--> subFolder11
|--> subFolder12
|--> subFolder2
|--> subFolder21
I tried to implement a KM repository service::
My Rep Service code::
package com.test;
import java.util.Collection;
import java.util.Iterator;
import com.sap.tc.logging.Location;
import com.sapportals.config.fwk.CannotAccessConfigException;
import com.sapportals.config.fwk.Configuration;
import com.sapportals.config.fwk.IConfigClientContext;
import com.sapportals.config.fwk.IConfigManager;
import com.sapportals.config.fwk.IConfigPlugin;
import com.sapportals.config.fwk.IMutableConfigurable;
import com.sapportals.config.fwk.InitialConfigException;
import com.sapportals.portal.security.usermanagement.UserManagementException;
import com.sapportals.wcm.WcmException;
import com.sapportals.wcm.crt.component.IReconfigurable;
import com.sapportals.wcm.crt.component.StartupException;
import com.sapportals.wcm.crt.configuration.ConfigurationException;
import com.sapportals.wcm.crt.configuration.IConfiguration;
import com.sapportals.wcm.repository.AccessDeniedException;
import com.sapportals.wcm.repository.ICollection;
import com.sapportals.wcm.repository.IResource;
import com.sapportals.wcm.repository.NotSupportedException;
import com.sapportals.wcm.repository.Property;
import com.sapportals.wcm.repository.ResourceException;
import com.sapportals.wcm.repository.manager.IRepositoryManager;
import com.sapportals.wcm.repository.manager.IResourceEvent;
import com.sapportals.wcm.repository.manager.IResourceEventReceiver;
import com.sapportals.wcm.repository.manager.ResourceEvent;
import com.sapportals.wcm.repository.service.AbstractRepositoryService;
import com.sapportals.wcm.repository.service.ServiceNotAvailableException;
import com.sapportals.wcm.util.config.ConfigCrutch;
import com.sapportals.wcm.util.events.IEvent;
// implements IMyNewRepositoryService interface
Note: IReconfigurable and IResourceEventReceiver interfaces are optional
public class MytestRepositoryService extends AbstractRepositoryService implements IReconfigurable, IResourceEventReceiver {
private static final String TYPE = "com.test.MytestRepositoryService";
private Collection repositoryManagers;
private static final Location log = Location.getLocation(MytestRepositoryService.class);
//variables
private static final String PLUGIN_FOLDERCREATION_SERVICE = "/cm/repository_services";
private static final String CONFIGCLASS_FOLDERCREATION_SERVICE = "com.test.MytestRepositoryService";
private static final String readPlugins[] = { PLUGIN_FOLDERCREATION_SERVICE };
public static final String PROP_MYFOLDER = "myFolder";
public MytestRepositoryService() {
super();
// Do not add code here. Add it to startUpImpl() instead
public String getServiceType() {
return MytestRepositoryService.TYPE;
protected void startUpImpl(Collection repositoryManagers) throws ConfigurationException, StartupException {
// implement this method as follows:
// - Verify configuration data
// - Get references to other needed (global) services
// - Check whether other repository services (this service depends on) are also assigned to the repository managers
// - Usually the service registers itself for certain events at all repository managers
try {
catch (Exception e) {
throw new StartupException(e.getMessage(), e);
this.repositoryManagers = repositoryManagers;
Iterator it = repositoryManagers.iterator();
while (it.hasNext()){
try {
addRepositoryAssignment((IRepositoryManager) it.next());
} catch (ServiceNotAvailableException e) {
e.printStackTrace();
protected void shutDownImpl() {
Iterator it = repositoryManagers.iterator();
while (it.hasNext()){
try {
removeRepositoryAssignment((IRepositoryManager) it.next());
} catch (WcmException e) {
e.printStackTrace();
protected void addRepositoryAssignment(IRepositoryManager mgr) throws ServiceNotAvailableException {
// Implement this method: Usually the service registers itself for certain events at the repository manager.
try {
// mgr.getEventBroker().register(this, ResourceEvent.ALL_TEMPLATE);
mgr.getEventBroker().register(this, new ResourceEvent(ResourceEvent.CREATE_COLLECTION, null));
} catch (WcmException e) {
e.printStackTrace();
protected void removeRepositoryAssignment(IRepositoryManager mgr) throws WcmException {
// Implement this method: Usually the service must unregister itself as an event handler.
// mgr.getEventBroker().unregister(this, ResourceEvent.ALL_TEMPLATE);
mgr.getEventBroker().unregister(this, new ResourceEvent(ResourceEvent.CREATE_COLLECTION, null));
public void reconfigure(IConfiguration config) throws ConfigurationException {
this.stateHandler.preReconfigure();
// check the new configuration data
try {
catch (ConfigurationException ex) {
this.stateHandler.postReconfigure(ex);
throw ex;
this.config = config;
this.stateHandler.postReconfigure();
public void received(IEvent event) {
IResourceEvent myEvent = (IResourceEvent) event;
IResource resource = (IResource) myEvent.getParameter();
String repositoryPath = "";
String parentPath = "";
//get the configuration...
try {
IConfigClientContext context = IConfigClientContext.createContext(ConfigCrutch.getConfigServiceUser());
IConfigManager cfg = Configuration.getInstance().getConfigManager(context);
IConfigPlugin configPlugin = cfg.getConfigPlugin(PLUGIN_FOLDERCREATION_SERVICE);
if (configPlugin != null) {
IMutableConfigurable[] configurables = configPlugin.getConfigurables(CONFIGCLASS_FOLDERCREATION_SERVICE, false);
for (int i = 0; i < configurables.length; i++) {
IMutableConfigurable configurable = configurables<i>;
if (configurable.getConfigClass().getName().equals(CONFIGCLASS_FOLDERCREATION_SERVICE)) {
// now get the attribute value...
repositoryPath = configurable.getPropertyValue(PROP_MYFOLDER); //// "documents/parentFolder1"
} catch (InitialConfigException e2) {
e2.printStackTrace();
} catch (CannotAccessConfigException e2) {
e2.printStackTrace();
} catch (UserManagementException e2) {
e2.printStackTrace();
try {
parentPath = resource.getParentCollection().getRID().toString();
} catch (AccessDeniedException e1) {
e1.printStackTrace();
} catch (ResourceException e1) {
e1.printStackTrace();
if(repositoryPath.equals(parentPath))
//write my code here
if (resource != null && (resource.isCollection()) )
ICollection parentFolder = (ICollection) resource;
try {
<b>parentFolder.createCollection("subFolder1",null);</b>
} catch (NotSupportedException e) {
e.printStackTrace();
} catch (AccessDeniedException e) {
e.printStackTrace();
} catch (ResourceException e) {
e.printStackTrace();
<b>...MytestRepositoryService.co.xml:</b>
- <Configurable configclass="com.test.MytestRepositoryService">
<property name="name" value="com.test.MytestRepositoryService" />
<property name="active" value="true" />
<i> <property name="myFolder" value="/documents/parentFolder1" /></i>
<property name="description" />
</Configurable>
<b>...MytestRepositoryService.cc.xml:</b>
- <ConfigClass name="com.test.MytestRepositoryService" extends="RepositoryService">
<attribute name="class" type="class" constant="com.test.MytestRepositoryService" />
</ConfigClass>
Have i done it right?? Where am i going wrong??? Plz advice.
I need to 'myFolder' as a configurable property in KM's <i>Content Management --> Repository Services</i> section.
Thanks!
Regards,
SK.Hi,
I haven't check your code but you know that you can archive the same without writing a portal componente by using the template feature. It is a simple customizing. See http://help.sap.com/saphelp_nw70/helpdata/en/55/83bd402b8d8031e10000000a1550b0/frameset.htm
Best Regards
Frank -
Advice on How to Create Web Services.....
Hi Guys,
We're contempating the purchase of Xcelsius - but the version without FlyNet - as it has no user restrictions. We've done some experimentation with the use of XML Data Sources, but prefer the idea of using a Web Servcies Data Source.
The problem being that we have little experience with this sort of thing.
So, does anyone have advice for us on the best way to create Web Services that will source data from an Oracle DB?
Does anyone have any example scripting to go along with it?
Any help is appreciated.
Regards
MickWe found the same issue while experimenting with .Net web services. It seems Xcelcius cannot consume a Dataset.
However it can consume an array of strings. It interprets this as a table of information.
Below is an snippet of the C# .Net code to create the array. (It has two values: a company ID and a count of employees.) I did not write this code (a developer on our team did.)
EmployeeCount[] Counts = null;
int i = 0;
Counts = new EmployeeCount[dtOutput.Rows.Count];
foreach (DataRow row in dtOutput.Rows)
Counts<i>.Company = row["COMPANY"].ToString();
Counts<i>.eCount = row["EmpCount"].ToString();
i++;
return Counts;
Below is an example of how we structured our webservice output
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<ArrayOfEmployeeCount xmlns="http://tempuri.org/">
<EmployeeCount>
<Company>string</Company>
<eCount>string</eCount>
</EmployeeCount>
<EmployeeCount>
<Company>string</Company>
<eCount>string</eCount>
</EmployeeCount>
</ArrayOfEmployeeCount> -
Exceptions at log file while creating a repository service
Hello,
I have implemented a repository service and set it to respond to all events. The service is writing itself at the correct repositories but doesn't respond to any event. By going over the log files I found the following logs. Can someone please tell me if he sees something that can cause this?
Devtlev: If you are reading this post (and I'm sure you will at some point... ), it is a continuation to our long long repository service post, but I thought it would be better to open new one
// Log when deployingThe Repository Service
#1.5#000BCDFB696800620000004100001A200003FAA9C0F55D3A#1120031924082#com.sapportals.portal.prt.service.config.ConfigDeploymentService#sap.com/irj#com.sapportals.portal.prt.service.config.ConfigDeploymentService#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Info##Plain###An upload sequence will start now. Please do not stop the server or serious deployment issues may arise.#
#1.5#000BCDFB696800620000004400001A200003FAA9C0F749B6#1120031924207#com.sapportals.portal.prt.service.config.ConfigDeploymentService#sap.com/irj#com.sapportals.portal.prt.service.config.ConfigDeploymentService#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Info##Plain###The upgrades of the upload sequence will start now, there are 1 upgrade(s) to perform#
#1.5#000BCDFB696800620000004500001A200003FAA9C0F74A6B#1120031924207#com.sapportals.portal.prt.service.config.ConfigDeploymentService#sap.com/irj#com.sapportals.portal.prt.service.config.ConfigDeploymentService#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Info##Plain###Processing upgrade: 1 out of 1. Config archive: RepositoryServices.prjconfig#
#1.5#000BCDFB696800620000004600001A200003FAA9C1050406#1120031925114#com.sapportals.config.fwk.util.BasicConfigurable#sap.com/irj#com.sapportals.config.fwk.util.BasicConfigurable#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Warning##Plain###configurable [counter.CounterService] instance of [configclass_config://install/cm/repository_services/counter.CounterService] has a property without corresponding attribute: active#
#1.5#000BCDFB696800620000004700001A200003FAA9C105055B#1120031925114#com.sapportals.config.fwk.util.BasicConfigurable#sap.com/irj#com.sapportals.config.fwk.util.BasicConfigurable#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Warning##Plain###configurable [counter.CounterService] instance of [configclass_config://install/cm/repository_services/counter.CounterService] has a property without corresponding attribute: description#
#1.5#000BCDFB696800620000004B00001A200003FAA9C22E421E#1120031944597#com.sapportals.portal.prt.service.config.UpgraderBridge#sap.com/irj#com.sapportals.portal.prt.service.config.UpgraderBridge#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Info##Plain###Time to import the configuration of RepositoryServices.prjconfig: 19796#
#1.5#000BCDFB696800620000004D00001A200003FAA9C22E5257#1120031944597#com.sapportals.portal.prt.service.config.ConfigDeploymentService#sap.com/irj#com.sapportals.portal.prt.service.config.ConfigDeploymentService#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Info##Plain###The upload sequence is now complete, all the upgrades have been performed.#
#1.5#000BCDFB696800620000005300001A200003FAA9C230142B#1120031944706#com.sapportals.wcm.crt.CrtClassLoaderRegistry#sap.com/irj#com.sapportals.wcm.crt.CrtClassLoaderRegistry#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Warning#1#/Applications/KMC/CRT#Plain###register new classloader with id = null#
// Log when entering the KM under Content Administration -> KM Content
#1.5#000BCDFB6968003E0000008400001A200003FAA9CD1A7029#1120032127601#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#RoyC#6677####16881e10e87411d9ce5b000bcdfb6968#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##
#1.5#000BCDFB696800600000004F00001A200003FAA9CD2343A8#1120032128179#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#RoyC#6677####16e05030e87411d9ae07000bcdfb6968#SAPEngine_Application_Thread[impl:3]_33##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##
#1.5#000BCDFB696800510000002A00001A200003FAA9CD237B8D#1120032128195#com.sapportals.wcm.repository.runtime.CmSystem#sap.com/irj#com.sapportals.wcm.repository.runtime.CmSystem#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#/Applications/KMC/RF#Plain###CM system is starting ...
#1.5#000BCDFB6968006C0000003500001A200003FAA9CD257EF1#1120032128320#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#RoyC#6677####16f5d400e87411d9b4b4000bcdfb6968#SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##
#1.5#000BCDFB6968006C0000003800001A200003FAA9CD259C9B#1120032128335#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#RoyC#6677####16f5d400e87411d9b4b4000bcdfb6968#SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##
#1.5#000BCDFB6968006C0000003B00001A200003FAA9CD25AB06#1120032128335#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#RoyC#6677####16f5d400e87411d9b4b4000bcdfb6968#SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##
#1.5#000BCDFB696800510000002B00001A200003FAA9CD405BCE#1120032130085#com.sapportals.wcm.protocol.webdav.UriMetaMap#sap.com/irj#com.sapportals.wcm.protocol.webdav.UriMetaMap#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Warning##Plain###replacing existing mapping WebUriMapper[/www/ep6sp9test <-> http://ep6sp9test.justice.gov.il/]#
#1.5#000BCDFB696800510000002C00001A200003FAA9CD6649D1#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###com.sap.security.api.NoSuchUserException: The given ID "RoyC" is not valid!#
#1.5#000BCDFB696800510000002D00001A200003FAA9CD665926#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getReadonlyUser(UserFactory.java:134)#
#1.5#000BCDFB696800510000002E00001A200003FAA9CD665A6A#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:180)#
#1.5#000BCDFB696800510000002F00001A200003FAA9CD665BBC#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:85)#
#1.5#000BCDFB696800510000003000001A200003FAA9CD665D8F#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at counter.CounterService.startUpImpl(CounterService.java:61)#
#1.5#000BCDFB696800510000003100001A200003FAA9CD665F1D#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.service.AbstractRepositoryService.start(AbstractRepositoryService.java:187)#
#1.5#000BCDFB696800510000003200001A200003FAA9CD666052#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:231)#
#1.5#000BCDFB696800510000003300001A200003FAA9CD6661CE#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:106)#
#1.5#000BCDFB696800510000003400001A200003FAA9CD666301#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:303)#
#1.5#000BCDFB696800510000003500001A200003FAA9CD666434#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:388)#
#1.5#000BCDFB696800510000003600001A200003FAA9CD666569#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)#
#1.5#000BCDFB696800510000003700001A200003FAA9CD666694#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)#
#1.5#000BCDFB696800510000003800001A200003FAA9CD6667B1#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:260)#
#1.5#000BCDFB696800510000003900001A200003FAA9CD666925#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)#
#1.5#000BCDFB696800510000003A00001A200003FAA9CD666B06#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:224)#
#1.5#000BCDFB696800510000003B00001A200003FAA9CD666C7B#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:162)#
#1.5#000BCDFB696800510000003C00001A200003FAA9CD666DB2#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:867)#
#1.5#000BCDFB696800510000003D00001A200003FAA9CD666ED3#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:167)#
#1.5#000BCDFB696800510000003E00001A200003FAA9CD666FFD#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.createResource(WdfProxy.java:1940)#
#1.5#000BCDFB696800510000003F00001A200003FAA9CD667132#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.getResource(WdfProxy.java:1514)#
#1.5#000BCDFB696800510000004000001A200003FAA9CD667271#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.prepareNestedControls(WdfProxy.java:1302)#
#1.5#000BCDFB696800510000004100001A200003FAA9CD6673C7#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.createNestedControls(WdfProxy.java:1209)#
#1.5#000BCDFB696800510000004200001A200003FAA9CD6674EA#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Control.create(Control.java:291)#
#1.5#000BCDFB696800510000004300001A200003FAA9CD6676AF#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.create(WdfProxy.java:1280)#
#1.5#000BCDFB696800510000004400001A200003FAA9CD667867#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:464)#
#1.5#000BCDFB696800510000004500001A200003FAA9CD6679B6#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000004600001A200003FAA9CD667AD3#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
#1.5#000BCDFB696800510000004700001A200003FAA9CD667BED#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000004800001A200003FAA9CD667D13#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
#1.5#000BCDFB696800510000004900001A200003FAA9CD667E40#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000004A00001A200003FAA9CD667F70#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
#1.5#000BCDFB696800510000004B00001A200003FAA9CD66809D#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000004C00001A200003FAA9CD66818D#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.WdfCompositeController.doInitialization(WdfCompositeController.java:268)#
#1.5#000BCDFB696800510000004D00001A200003FAA9CD6682AB#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.WdfCompositeController.buildComposition(WdfCompositeController.java:659)#
#1.5#000BCDFB696800510000004E00001A200003FAA9CD66838A#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:32)#
#1.5#000BCDFB696800510000004F00001A200003FAA9CD66847A#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.Container.preRender(Container.java:118)#
#1.5#000BCDFB696800510000005000001A200003FAA9CD668550#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.Container.preRender(Container.java:118)#
#1.5#000BCDFB696800510000005100001A200003FAA9CD668734#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.Container.preRender(Container.java:118)#
#1.5#000BCDFB696800510000005200001A200003FAA9CD66889C#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.rendering.PageContext.render(PageContext.java:936)#
#1.5#000BCDFB696800510000005300001A200003FAA9CD6689CF#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.DynPage.doOutput(DynPage.java:237)#
#1.5#000BCDFB696800510000005400001A200003FAA9CD668AD8#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)#
#1.5#000BCDFB696800510000005500001A200003FAA9CD668CAE#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)#
#1.5#000BCDFB696800510000005600001A200003FAA9CD668E04#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)#
#1.5#000BCDFB696800510000005700001A200003FAA9CD668F2F#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)#
#1.5#000BCDFB696800510000005800001A200003FAA9CD669041#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#000BCDFB696800510000005900001A200003FAA9CD66921D#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.app.servlet.WcmHtmlbBaseServlet.service(WcmHtmlbBaseServlet.java:100)#
#1.5#000BCDFB696800510000005A00001A200003FAA9CD6693B8#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:321)#
#1.5#000BCDFB696800510000005B00001A200003FAA9CD669503#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.ServletComponentItem$ServletWrapperComponent.doContent(ServletComponentItem.java:110)#
#1.5#000BCDFB696800510000005C00001A200003FAA9CD669638#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)#
#1.5#000BCDFB696800510000005D00001A200003FAA9CD669776#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)#
#1.5#000BCDFB696800510000005E00001A200003FAA9CD6698AE#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#
#1.5#000BCDFB696800510000005F00001A200003FAA9CD6699DF#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
#1.5#000BCDFB696800510000006000001A200003FAA9CD669B11#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
#1.5#000BCDFB696800510000006100001A200003FAA9CD669C39#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)#
#1.5#000BCDFB696800510000006200001A200003FAA9CD669D73#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)#
#1.5#000BCDFB696800510000006300001A200003FAA9CD669F50#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#
#1.5#000BCDFB696800510000006400001A200003FAA9CD66A0F4#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
#1.5#000BCDFB696800510000006500001A200003FAA9CD66A240#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
#1.5#000BCDFB696800510000006600001A200003FAA9CD66A362#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)#
#1.5#000BCDFB696800510000006700001A200003FAA9CD66A47E#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)#
#1.5#000BCDFB696800510000006800001A200003FAA9CD66A5BC#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)#
#1.5#000BCDFB696800510000006900001A200003FAA9CD66A6E2#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5#000BCDFB696800510000006A00001A200003FAA9CD66A82E#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)#
#1.5#000BCDFB696800510000006B00001A200003FAA9CD66A958#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#000BCDFB696800510000006C00001A200003FAA9CD66AA75#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)#
#1.5#000BCDFB696800510000006D00001A200003FAA9CD66AC60#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#000BCDFB696800510000006E00001A200003FAA9CD66ADF1#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)#
#1.5#000BCDFB696800510000006F00001A200003FAA9CD66AF30#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)#
#1.5#000BCDFB696800510000007000001A200003FAA9CD66B04D#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)#
#1.5#000BCDFB696800510000007100001A200003FAA9CD66B166#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)#
#1.5#000BCDFB696800510000007200001A200003FAA9CD66B29B#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)#
#1.5#000BCDFB696800510000007300001A200003FAA9CD66B3C6#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)#
#1.5#000BCDFB696800510000007400001A200003FAA9CD66B4FD#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#
#1.5#000BCDFB696800510000007500001A200003FAA9CD66B626#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#
#1.5#000BCDFB696800510000007600001A200003FAA9CD66B740#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)#
#1.5#000BCDFB696800510000007700001A200003FAA9CD66B930#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)#
#1.5#000BCDFB696800510000007800001A200003FAA9CD66BAE7#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5#000BCDFB696800510000007900001A200003FAA9CD66BC1A#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5#000BCDFB696800510000007A00001A200003FAA9CD66BD2E#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)#
#1.5#000BCDFB696800510000007B00001A200003FAA9CD66BE38#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)#
#1.5#000BCDFB696800510000007C00001A200003FAA9CD66BF5C#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###----
caused by -
#1.5#000BCDFB696800510000007D00001A200003FAA9CD66C07D#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###com.sap.security.core.persistence.datasource.PersistenceException: The given ID "RoyC" is not valid!#
#1.5#000BCDFB696800510000007E00001A200003FAA9CD66D01F#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.persistence.datasource.imp.DataSourceBaseImplementation.splitPrincipalDatabagID(DataSourceBaseImplementation.java:492)#
#1.5#000BCDFB696800510000007F00001A200003FAA9CD66D1FB#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.PrincipalFactory.getPrincipalType(PrincipalFactory.java:123)#
#1.5#000BCDFB696800510000008000001A200003FAA9CD66D3C0#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getReadonlyUser(UserFactory.java:127)#
#1.5#000BCDFB696800510000008100001A200003FAA9CD66D517#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:180)#
#1.5#000BCDFB696800510000008200001A200003FAA9CD66D633#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:85)#
#1.5#000BCDFB696800510000008300001A200003FAA9CD66D742#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at counter.CounterService.startUpImpl(CounterService.java:61)#
#1.5#000BCDFB696800510000008400001A200003FAA9CD66D86E#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.service.AbstractRepositoryService.start(AbstractRepositoryService.java:187)#
#1.5#000BCDFB696800510000008500001A200003FAA9CD66D9A1#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:231)#
#1.5#000BCDFB696800510000008600001A200003FAA9CD66DB03#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:106)#
#1.5#000BCDFB696800510000008700001A200003FAA9CD66DC3B#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:303)#
#1.5#000BCDFB696800510000008800001A200003FAA9CD66DD5A#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:388)#
#1.5#000BCDFB696800510000008900001A200003FAA9CD66DECD#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)#
#1.5#000BCDFB696800510000008A00001A200003FAA9CD66E096#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)#
#1.5#000BCDFB696800510000008B00001A200003FAA9CD66E20E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:260)#
#1.5#000BCDFB696800510000008C00001A200003FAA9CD66E33B#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)#
#1.5#000BCDFB696800510000008D00001A200003FAA9CD66E464#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:224)#
#1.5#000BCDFB696800510000008E00001A200003FAA9CD66E57D#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:162)#
#1.5#000BCDFB696800510000008F00001A200003FAA9CD66E6B8#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:867)#
#1.5#000BCDFB696800510000009000001A200003FAA9CD66E7F7#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:167)#
#1.5#000BCDFB696800510000009100001A200003FAA9CD66E92F#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.createResource(WdfProxy.java:1940)#
#1.5#000BCDFB696800510000009200001A200003FAA9CD66EA5C#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.getResource(WdfProxy.java:1514)#
#1.5#000BCDFB696800510000009300001A200003FAA9CD66EDA0#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.prepareNestedControls(WdfProxy.java:1302)#
#1.5#000BCDFB696800510000009400001A200003FAA9CD66EF2B#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.createNestedControls(WdfProxy.java:1209)#
#1.5#000BCDFB696800510000009500001A200003FAA9CD66F066#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Control.create(Control.java:291)#
#1.5#000BCDFB696800510000009600001A200003FAA9CD66F186#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.create(WdfProxy.java:1280)#
#1.5#000BCDFB696800510000009700001A200003FAA9CD66F29B#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:464)#
#1.5#000BCDFB696800510000009800001A200003FAA9CD66F3D4#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000009900001A200003FAA9CD66F4FC#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
#1.5#000BCDFB696800510000009A00001A200003FAA9CD66F62F#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000009B00001A200003FAA9CD66F72E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
#1.5#000BCDFB696800510000009C00001A200003FAA9CD66F843#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000009D00001A200003FAA9CD66F92E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
#1.5#000BCDFB696800510000009E00001A200003FAA9CD66F9F7#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000009F00001A200003FAA9CD66FABF#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.WdfCompositeController.doInitialization(WdfCompositeController.java:268)#
#1.5#000BCDFB69680051000000A000001A200003FAA9CD66FC22#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.WdfCompositeController.buildComposition(WdfCompositeController.java:659)#
#1.5#000BCDFB69680051000000A100001A200003FAA9CD66FDDF#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:32)#
#1.5#000BCDFB69680051000000A200001A200003FAA9CD66FF3C#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.Container.preRender(Container.java:118)#
#1.5#000BCDFB69680051000000A300001A200003FAA9CD670042#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.Container.preRender(Container.java:118)#
#1.5#000BCDFB69680051000000A400001A200003FAA9CD670207#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.Container.preRender(Container.java:118)#
#1.5#000BCDFB69680051000000A500001A200003FAA9CD670360#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.rendering.PageContext.render(PageContext.java:936)#
#1.5#000BCDFB69680051000000A600001A200003FAA9CD670467#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.DynPage.doOutput(DynPage.java:237)#
#1.5#000BCDFB69680051000000A700001A200003FAA9CD670558#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)#
#1.5#000BCDFB69680051000000A800001A200003FAA9CD67063E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)#
#1.5#000BCDFB69680051000000A900001A200003FAA9CD67071D#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)#
#1.5#000BCDFB69680051000000AA00001A200003FAA9CD6707FB#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)#
#1.5#000BCDFB69680051000000AB00001A200003FAA9CD6708D6#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#000BCDFB69680051000000AC00001A200003FAA9CD6709AA#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.app.servlet.WcmHtmlbBaseServlet.service(WcmHtmlbBaseServlet.java:100)#
#1.5#000BCDFB69680051000000AD00001A200003FAA9CD670AC3#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:321)#
#1.5#000BCDFB69680051000000AE00001A200003FAA9CD670BE6#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.ServletComponentItem$ServletWrapperComponent.doContent(ServletComponentItem.java:110)#
#1.5#000BCDFB69680051000000AF00001A200003FAA9CD670D10#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)#
#1.5#000BCDFB69680051000000B000001A200003FAA9CD670ED4#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)#
#1.5#000BCDFB69680051000000B100001A200003FAA9CD67109E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#
#1.5#000BCDFB69680051000000B200001A200003FAA9CD671202#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
#1.5#000BCDFB69680051000000B300001A200003FAA9CD67132E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
#1.5#000BCDFB69680051000000B400001A200003FAA9CD671447#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)#
#1.5#000BCDFB69680051000000B500001A200003FAA9CD671574#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)#
#1.5#000BCDFB69680051000000B600001A200003FAA9CD67169F#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#
#1.5#000BCDFB69680051000000B700001A200003FAA9CD6717D8#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
#1.5#000BCDFB69680051000000B800001A200003FAA9CD67190F#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
#1.5#000BCDFB69680051000000B900001A200003FAA9CD671A2E#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)#
#1.5#000BCDFB69680051000000BA00001A200003FAA9CD671BF6#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)#
#1.5#000BCDFB69680051000000BB00001A200003FAA9CD671DB4#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)#
#1.5#000BCDFB69680051000000BC00001A200003FAA9CD671EFE#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5#000BCDFB69680051000000BD00001A200003FAA9CD672044#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)#
#1.5#000BCDFB69680051000000BE00001A200003FAA9CD672159#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#000BCDFB69680051000000BF00001A200003FAA9CD67227C#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)#
#1.5#000BCDFB69680051000000C000001A200003FAA9CD6723A8#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#000BCDFB69680051000000C100001A200003FAA9CD6724D7#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)#
#1.5#000BCDFB69680051000000C200001A200003FAA9CD6725FB#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)#
#1.5#000BCDFB69680051000000C300001A200003FAA9CD672716#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)#
#1.5#000BCDFB69680051000000C400001A200003FAA9CD6728EB#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)#
#1.5#000BCDFB69680051000000C500001A200003FAA9CD672A9C#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)#
#1.5#000BCDFB69680051000000C600001A200003FAA9CD672BF0#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)#
#1.5#000BCDFB69680051000000C700001A200003FAA9CD672D0F#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#
#1.5#000BCDFB69680051000000C800001A200003FAA9CD672E22#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#
#1.5#000BCDFB69680051000000C900001A200003FAA9CD672F4E#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)#
#1.5#000BCDFB69680051000000CA00001A200003FAA9CD67309C#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)#
#1.5#000BCDFB69680051000000CB00001A200003FAA9CD6731D4#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5#000BCDFB69680051000000CC00001A200003FAA9CD6732E5#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5#000BCDFB69680051000000CD00001A200003FAA9CD6733F2#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)#
#1.5#000BCDFB69680051000000CE00001A200003FAA9CD6735DA#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)#
#1.5#000BCDFB69680051000000CF00001A200003FAA9CD673771#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###----
caused by -
#1.5#000BCDFB69680051000000D000001A200003FAA9CD6738B2#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###com.sap.security.core.persistence.datasource.PersistenceException: The given ID "RoyC" is not valid!#
#1.5#000BCDFB69680051000000D100001A200003FAA9CD6739D8#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.persistence.datasource.imp.DataSourceBaseImplementation.splitPrincipalDatabagID(DataSourceBaseImplementation.java:492)#
#1.5#000BCDFB69680051000000D200001A200003FAA9CD673AFF#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.PrincipalFactory.getPrincipalType(PrincipalFactory.java:123)#
#1.5#000BCDFB69680051000000D300001A200003FAA9CD673C2F#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getReadonlyUser(UserFactory.java:127)#
#1.5#000BCDFB69680051000000D400001A200003FAA9CD673D53#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:180)#
#1.5#000BCDFB69680051000000D500001A200003FAA9CD673E8A#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:85)#
#1.5#000BCDFB69680051000000D600001A200003FAA9CD673FB4#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at counter.CounterService.startUpImpl(CounterService.java:61)#
#1.5#000BCDFB69680051000000D700001A200003FAA9CD6740CE#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.service.AbstractRepositoryService.start(AbstractRepositoryService.java:187)#
#1.5#000BCDFB69680051000000D800001A200003FAA9CD6742E2#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:231)#
#1.5#000BCDFB69680051000000D900001A200003FAA9CD67447D#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:106)#
#1.5#000BCDFB69680051000000DA00001A200003FAA9CD6745BE#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:303)#
#1.5#000BCDFB69680051000000DB00001A200003FAA9CD6746D6#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:388)#
#1.5#000BCDFB69680051000000DC00001A200003FAA9CD6747F1#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)#
#1.5#000BCDFB69680051000000DD00001A200003FAA9CD674927#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)#
#1.5#000BCDFB69680051000000DE00001A200003FAA9CD674A53#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:260)#
#1.5#000BCDFB69680051000000DF00001A200003FAA9CD674B83#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)#
#1.5#000BCDFB69680051000000E000001A200003FAA9CD674CB0#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:224)#
#1.5#000BCDFB69680051000000E100001A200003FAA9CD674DCE#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:162)#
#1.5#000BCDFB69680051000000E200001A200003FAA9CD674FB4#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:867)#
#1.5#000BCDFB69680051000000E300001A200003FAA9CD67514B#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:167)#
#1.5#000BCDFB69680051000000E400001A200003FAA9CD675293#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.createResource(WdfProxy.java:1940)#
#1.5#000BCDFB69680051000000E500001A200003FAA9CD6753BD#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.getResource(WdfProxy.java:1514)#
#1.5#000BCDFB69680051000000E600001A200003FAA9CD6754FD#1120032132647#System.err#sap.com/irj#SysteHi Roy,
for the first log entry, see this posting: /thread/41655 [original link is broken]
Search for "property without corresponding attribute" in it and have a look at my answer.
The second error is, to be short:
com.sap.security.api.NoSuchUserException: The given ID "RoyC" is not valid!#
... at counter.CounterService.startUpImpl(CounterService.java:61)#
Have a look at your own code what's wrong with it (seems that you pass your user ID instead of uniqueID). Use getUserByLogonID(...) instead.
Hope it helps
Detlev -
Error while creating the service entry sheet in PRD
Hi All,
We are in SAP R/3 4.7 Version. OF39 settings are 58 & 61 Statistical update only ! Now my case is i assigned Rs.100 Budget agaisnt one FC & Comitmetn item & created one service Purchase order Rs.80 & Make down payment against same PO Rs.80.
Now as per above mentioned scenario ,system should allow new Purchase order creation for Rs. 20. But my system is allowing to create up to Rs.100. I am very much sure system not allowed the same and also allow for service entry creation for first PO. But system given error message while doing the Service sheet.
Kindly advice. OF39 settings are OK .Both are statistical only
Rgds
ManiSumaHi Manisuma, statistical update is recommended to be used only at the begining of a document chain (i.e.purchase requisition or funds reservation) cause if you set it in intermediate documents as you did the budget is set as available, in your example the downpayment reduces the purchase order commitment, and as the downpayment is statistical it does not affect the Availability Control, so the amount (80 in your example) becomes available again so new commitments/actual can be created.
Regards
Cesar -
I'm trying to create a Service User in the portal. I've come across this link:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cfdc9e90-0201-0010-6780-cc30206dd319
On page 7, it says that "Service Users reside only in the database. This can be achieved by settings in the configuration file."
It then goes on to say that several service users such as cmadmin_service are added by KM. My question is, how do I add my own service users? My portal is not using LDAP as a user repository, just the portal DB.
Thanks,
MattFirst, thanks for the reponse -
Yes - I believe the namespace is $serviceUser$. Since our portal is not integrated with a user repository like AD, how would I create a service user with appropriate namespace? Creating users via the User Administration role, I cannot assign the new users to the $serviceUser$ namespace. Do I have to write some SQL to insert into the user database table?
Thanks again. -
How to create Web Service based on PI WSDL message
Hi all,
we have following scenario:
Within PI (version 7.1) we set up a message type and inbound service interface. This service interface should send the PI message to a web service running on a SAP J2EE (version 7.01). As the PI message is sent as WSDL I thought it should be easy to build a web service on the SAP J2EE based on this WSDL from PI.
Unfortunately, I have problems creating the Web Service.
For my current project we integrated the NWDI to the SAP NetWeaver Developer Studio and I'm required to add the Web Service to an existing DC (Development Component) within the NWDI.
What I tried so far is:
- I created a Deployable Proxy Project and within this I created a Client Proxy Definition based on the WSDL from the PI. But I can't add this Proxy to the DCs of the NWDI and I don't know how to implement my own coding here in order execute specific functions.
- I created a new class within the NWDI DC and a public method. Based on this I created a Virtual Interface and a Web Service Definition (WSD). Then I added this to a Web Service Deployment Descriptor. I uploaded this to the SAP J2EE. But I'm not able to access this and I don't know hoe to assign the WSDL here.
I also tried here to create a client proxy based on this WSD as I thought I might assign the WSDL here. But I don't see the WSD in the list of Web Services uploaded to the SAP J2EE...
Can you please advice me how to create a Web Service in such an environment?
regards
René JurmannHi Tahir,
sorry that you needed to wait this long - but this is how I created the web service:
The steps on how to create the web service in NetWeaver Developer studio are nearly the same as described in the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5838. [original link is broken] [original link is broken] [original link is broken]
Some steps I just skipped and some others I added. Some of the steps I did the way I described it as I needed to connect the web service with the SAP PI.
Prerequisites:
Add Java Perspective and J2EE Development Perspective to the open perspectives.
Within "Window - Preferences - Web Services" check "Soap extensions visible in the virtual interface editor"
The SDM of the corresponding SAP J2EE is configured within "Window - Preferences"
Create a Development Component (DC) with type "J2EE -> EJB Module"
The business logic of the web service will be implemented in an Enterprise Java Bean (EJB). So first the EJB component must be created:
Choose "File -> New -> Other"
In opening PopUp choose "Development Component -> Development Component Project"
Select the Software Component for which you want to add the DC (e.g. "Local Development -> MyComponents")
Choose now vendor, name and type:
vendor is an alpha-numeric string of 20 characters starting with a letter - all in lower case
name is an alpha-numeric string starting with a letter - all in lower case
vendor and name concatenated must not be longer then 40 characters
the name can be separated into different part using "/" as separator
each part of the name must not be longer than 8 characters
the type is "J2EE - EJB Module"
you can specify a Caption as general description for the web service
Create new EJB
To create the EJB itself:
In J2EE DC Explorer of J2EE Development Perspective expand new DC and right-click on folder "ejbModule"
Choose "New - EJB" with following details:
EJB Name: <name as for PI service Interface to be created - starting in upper case>
EJB Project: <pre selected>
Bean Type: Stateless Session Bean
Default EJB Package: <corresponds to namespace in PI>
generate default interfaces: Checked
Regarding the "Default EJB Package" this should be created according the namespace in PI for which all PI objects will be created. This only applies if you have some naming conventions here.
Example:
Namespace in PI is: http://company.net/pi/SOFTWARE_COMP/Application
The corresponding package then is: net.company.pi.software_comp.application
Implement coding for web service
As the web service will be called via PI some transfer variables will be submitted. Most likely, those variables will not be standard type (e.g. String) but a complex type. Those types must be generated as Java classes. Below an example of a complex type I needed:
Data Type
net.company.pi.software_comp.application.types.MessageProcessingInformation
Structure:
Element name Element type
sendingSystemID String
interfaceID String
businessProcessVariantCode String
testIndicator Boolean
For every element described a public "get", "set" and "has" method must be created in the corresponding Java class:
package net.company.pi.software_comp.application.types;
import java.io.Serializable;
public class MessageProcessingInformation implements Serializable {
protected String sendingSystemID;
protected String interfaceID;
protected String businessProcessVariantCode;
protected Boolean testIndicator;
public String getSendingSystemID() {
return sendingSystemID;
public void setSendingSystemID(String value) {
this.sendingSystemID = value;
public boolean hasSendingSystemID() {
if(sendingSystemID != null && !sendingSystemID.equals("")){
return true;
return false;
All Java classes representing complex types and all classes referenced here (used for sub-types) must implement java.io.Serializable. Java standard types which do not implement this class must not be used as sub-types.
As soon as all data types are declared the real business logic can be implemented:
In J2EE DC Explorer of J2EE Development Perspective expand DC - "ejb-jar.xml" - <Name> and double click on "ejbCreate"
In detail view select folder "Business Methods" and click "Add"
choose name of business method - this should be the same as the PI message type used for the service interface - starting lower case
return type should be "void"
add needed parameters fully qualified - including package (as specified in PI and created previously in DC)
you can mark certain parameters as array if necessary
Remark:
It might be that after saving you get an error. This might be as the package name of one component is copied to the corresponding Java class at the very beginning (before the package declaration within the Java class). Simply delete the string here.
It also might be, that the new business method is only defined in the remote interface class but not in the bean class. Just create an according method in the bean class.
Within the newly created business method within the bean class you can now implement the business logic.
Create a DC with type "J2EE -> Enterprise Application"
In order to create the "real" web service and deploy it to the J2EE an Enterprise Application project has to be created. So create a new DC as for the EJB Module but choose as type "J2EE -> Enterprise Application".
After the DC is created right click on the EJB DC and choose "Add to EAR Project". Choose the new DC.
Create web service for EJB
As soon as you implemented the business logic you can create the "real" web service. Therefore:
Right click on the EJB name below "ejb-jar.xml"
Choose "New - Web Service"
Choose proper "Web Service Name" and "Configuration Name" (probably oriented at the EJB name)
Copy the URL of the web service - you'll need it later for PI configuration
on the second next screen use the same name for "Virtual Interface" and "Web Service Definition" (the name should be the name of the "Endpoint")
the "EAR Project" should be preselected
Unfortunately, the web service can't be used in its current configuration to be accessed by PI. Therefore the Virtual Interface must be changed. To do so, expand folder "Virtual Interfaces" and double click the virtual interface created.
Within the detail view expand in tabs "Mapping" and "Types" the complete folder structure. For any "SOAP Extension" where a namespace can be defined use as namespace the corresponding namespace in PI (e.g. http://corpintra.net/pi/CBFC_GLOBAL_SAP_APPL/BillerDirect) but do not change any "Soap Extension" of a standard Java type. (if you don't have any naming convetions for namespaces in PI you can leave the SOAP Extension here. But then the namespace in PI should be set accordingly.)
Probably it can be necessary on top level "Soap Extensions" in tab "Mapping" to leave "Use Namespaces for Parameters" unchecked. For some of my web services this parameter must be checked for others not - just try.
If you can define a "New Name", "Local Name" or "Item Label" for a Soap Extension then use a name with starting upper case letter. (For Java Naming conventions most of the data type names will start with lower case letters.) Especially the method name must be renamed this way in order to stick to the PI namings.
As a last point to change here check in tab "Mapping" all "Incoming Parameters" which you specified as array. Use for those as "New Name" a different name - do not just simply change from lower case to upper case. This is necessary as on PI we need to create two levels although here only one is specified.
For any own sub-type declared as array the name within the coding should also differ from the corresponding Java Class name the type refers to.
If all this is done you can deploy the web service to the J2EE:
right click on "Enterprise Application" DC and choose "Development Component - Build..." and build all corresponding components
right click on "Enterprise Application" DC and choose "Development Component - Deploy"
Test the new web service via <J2EE URL>/wsnavigator/enterwsdl.html
Create PI interface
After the web service is created successfully the PI integration can be started.
Therefore, within the Enterprise Services Builder create a data type according to the web service definition. All components defined on top-level for this data type should be declared as incoming parameter for the web service business method. Therefore it could be necessary to create some sub data types on PI first and add those to the "master" data type.
Ensure that the names of the components correspond to the names defined in the web service (see virtual interface here). Those names must exactly be the same - including lower/upper case. Also take care for the ordering of the components.
In case you need to include arrays following applies:
The upper level is of occurrence "1:1". This has only one sub-entry with occurrence "1:n". The names for upper and sub-level must not equal.
Based on the data type a message type is created. The name of the message type must be exactly the same as the name of the web service business method. (Hint: the name of the web service business method was most likely changed in the virtual interface. Then this name must correspond to the message type name.) Based on the message type an asynchronous inbound interface is to be created (which will be referred in the Integration Directory). The operation name for this interface (left panel) should be the same as the name for the web service business method.
Create PI mappings and routings
How to map (message mapping and operation mapping) from source to the web service message I wont explain here as this depends on the source message. The only important things here are:
When creating the SOAP communication channel within the Integration Builder the "Target URL" is:
<J2EE URL>/<Access URL as specified in web service creation>?wsdl&style=document
The soap action is the name of the web service business method.
Most likely the web service needs authentication to be executed.
Maybe you are looking for
-
User account passwords no longer working
I recently erased and did clean installs on all of our client macs and changed the server's IP address. The new address is entered in Directory Access on all of the clients. The log-in screen appears as the server software has directed it to, with a
-
Repeat Purchase Order Output Type - Auto Repeat
Hi, Currently, when we create the Purchase Order the output type will be automatically generated in the message tab once the Purcahse Order is saved. In our Purchase Order process, we have using the function Purchase Order Online Approval and Purch
-
How to change the delay for a specific message
Hi, I need to change the delay for an specific message, So how can I consume message by JMSCorrelationID which is enqueued with delay? I am using Java and Oracle.JMS classes. This a sample code of the deque method public BasicAQData dequeue(int insId
-
Form with multiple signatures, each with sigDate, only one date fills
I have a form with two signature fields, Sig1 and Sig2. Each sig field has an associated date field Sig1Date and Sig2Date. I have a Topaz signature pad, so the form users physically sign the document. When the first signature is entered (in either S
-
Trouble updating InDesign CC 2014 so I can use DPS tools.
I am trying to update InDesign CC 2014 so I can use DPS tools. But "updates" is grayed out. I noticed that CC desktop says InDesign is up to date. Any suggestions?