If you installed the non-virtual appliance version, a user's default login module should be the "Service Catalog" module. An instance with no services or content defined will look "empty", but you should be in the Service Catalog module upon logging in. If you have not defined or imported any service definition, you would not have anything to order/request.
Can you share a screenshot of what the user sees (make sure the module menu is visible)?
You have performed a vanilla install of Prime Service Catalog, and this is the expected behavior. I have uploaded a content package in this community that you can import into this instance with Catalog Deployer.
If you are not familiar with the Prime Service Catalog, then you probably want to start with the Virtual Appliance (downloadable from Cisco.com), wich already has the content included, and attend training offered by Cisco or partners.
This document explains the logic to develop Tidal Enterprise
Orchestrator workflow to automate the process of creating vCenter
Resource Pool* vSphere Power CLI must be installed either on the TEO
server or vCenter* vMA can also be used to achieve the same...
IntorductionCisco Process Orcehstrator (CPO) ships with the webservices
adapter that can be used to make Web Service API call to REST or SOAP
based applications. Before a sample workflow to make SOAP API calls
using CPO, lets understand some of the fundam...