As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
We used XDSReg service object in our processes. It basically allows you to register a special register while in the middle of process. All processes are working in production.
The problem is I wanted to create a new process and use XDSReg in a new configuration. But when I open service object's Type combo button, I cannot see XDSReg in available list. Interestingly I looked my old processes in both DEV and PRD, and the same thing there too. It seems weird! Because it's already used, but if we want to create new one, we can't!
Does anybody knows how I can see it in available list again?
Posts: 2 | Location: Madison, WI | Registered: March 09, 2007
Hi Tuncay, Have you tried clicking 'Class Name' radio button in the service object definition, service type screen? You can then type 'XDSREGAgent' in there. If you don't get an error when you click Next, it should be fine.
Instead of specifing the classname each time, it would be of great timesaver if you can define agents. That way you will have the agent in all interfaces to work with.
Hi Nan, Yes I agree, adding an agent is probably a better long term solution. Tuncay, to do this, you need to add an agent: From the blue screen, 'go' to your config, then navigate to Configuration -> Defines -> Agent. For 'Alias' use 'XGSreg' (or whatever you want to call it), for Procedure use 'com.ibi.agents.XDSREGAgent' and for 'description' use whatever you want. Click 'Add'. This takes you to a screen where you define the 'Type', 'Scope', etc. Fill these and click save. This should make 'XDSreg' available in the drop down list in your Service Objects in Designer. Remember that your Project in Designer must be based on the Configuration Id that you just added the Agent to for it to become available as a drop down.