Fusion Middleware

Terminating a specific application instance using it's index number in Pivotal Cloud Foundry

Pas Apicella - Tue, 2017-12-19 03:54
I was recently asked how to terminate a specific application instance rather then terminate all instances using "cf delete".

We can easily using the CF REST API or even easier the CF CLI "cf curl" command which makes it straight forward to make REST based calls into cloud foundry as shown below.

CF REST API Docs

https://apidocs.cloudfoundry.org/280/

Below assumes you already logged into PCF using the CF CLI

1. First find an application that has multiple instances

pasapicella@pas-macbook:~$ cf app pas-cf-manifest
Showing health and status for app pas-cf-manifest in org apples-pivotal-org / space development as papicella@pivotal.io...

name:              pas-cf-manifest
requested state:   started
instances:         2/2
usage:             756M x 2 instances
routes:            pas-cf-manifest.cfapps.io
last uploaded:     Sun 19 Nov 21:26:26 AEDT 2017
stack:             cflinuxfs2
buildpack:         client-certificate-mapper=1.2.0_RELEASE container-security-provider=1.8.0_RELEASE java-buildpack=v4.5-offline-https://github.com/cloudfoundry/java-buildpack.git#ffeefb9 java-main
                   java-opts jvmkill-agent=1.10.0_RELEASE open-jdk-like-jre=1.8.0_1...

     state     since                  cpu    memory           disk           details
#0   running   2017-12-16T00:11:27Z   0.0%   241.5M of 756M   139.9M of 1G
#1   running   2017-12-17T10:39:09Z   0.3%   221.3M of 756M   139.9M of 1G

2. Use a "cf curl" curl which uses the application GUID to determine which application to check all application instances and their current state

pasapicella@pas-macbook:~$ cf curl /v2/apps/`cf app pas-cf-manifest --guid`/instances
{
   "0": {
      "state": "RUNNING",
      "uptime": 293653,
      "since": 1513383087
   },
   "1": {
      "state": "RUNNING",
      "uptime": 169591,
      "since": 1513507149
   }
}

3. Now let's delete instance with index "1". Don't forget that PCF will determine the current desired state of the application is not the current state and will re-start the application instance very quickly

pasapicella@pas-macbook:~$ cf curl /v2/apps/`cf app pas-cf-manifest --guid`/instances/1 -X DELETE

Note: You won't get any output BUT you can verify it has done what you asked for by running the command at step #2 again

pasapicella@pas-macbook:~$ cf curl /v2/apps/`cf app pas-cf-manifest --guid`/instances
{
   "0": {
      "state": "RUNNING",
      "uptime": 293852,
      "since": 1513383087
   },
   "1": {
      "state": "DOWN",
      "uptime": 0
   }
}

If you run it again say 30 seconds later you should see your application instance re-started as shown below

pasapicella@pas-macbook:~$ cf curl /v2/apps/`cf app pas-cf-manifest --guid`/instances
{
   "0": {
      "state": "RUNNING",
      "uptime": 293870,
      "since": 1513383087
   },
   "1": {
      "state": "STARTING",
      "uptime": 11,
      "since": 1513676947
   }
}

pasapicella@pas-macbook:~$ cf curl /v2/apps/`cf app pas-cf-manifest --guid`/instances
{
   "0": {
      "state": "RUNNING",
      "uptime": 293924,
      "since": 1513383087
   },
   "1": {
      "state": "RUNNING",
      "uptime": 45,
      "since": 1513676965
   }
}

More Information

pasapicella@pas-macbook:~$ cf curl --help
NAME:
   curl - Executes a request to the targeted API endpoint

USAGE:
   cf curl PATH [-iv] [-X METHOD] [-H HEADER] [-d DATA] [--output FILE]

   By default 'cf curl' will perform a GET to the specified PATH. If data
   is provided via -d, a POST will be performed instead, and the Content-Type
   will be set to application/json. You may override headers with -H and the
   request method with -X.

   For API documentation, please visit http://apidocs.cloudfoundry.org.

EXAMPLES:
   cf curl "/v2/apps" -X GET -H "Content-Type: application/x-www-form-urlencoded" -d 'q=name:myapp'
   cf curl "/v2/apps" -d @/path/to/file

OPTIONS:
   -H            Custom headers to include in the request, flag can be specified multiple times
   -X            HTTP method (GET,POST,PUT,DELETE,etc)
   -d            HTTP data to include in the request body, or '@' followed by a file name to read the data from
   -i            Include response headers in the output
   --output      Write curl body to FILE instead of stdout
Categories: Fusion Middleware

Oracle Content & Experience Cloud: Document Search

If you read my first post on Oracle Content & Experience Cloud (Oracle CEC), you would have come away impressed with the capabilities and features of the product. Features for organizations to manage and share high-value content that could be used to build content-rich, omni-channel websites. However, as I’ve continued to work with Oracle CEC over the last four months, some features need improvement. Most notably in my opinion, is search. I’ll explain the reasons why in this blog post, and offer up details on how you can develop a custom component to enable a better search experience.

The Problem: Search Options are Limited for Sites and Provide Little Customization

Oracle CEC provides businesses with strong document storage, security and sharing capabilities through the managed “Content” section of the interface. However, there is often a need for content to be searched, viewed and accessed through a managed site. The out-of-the-box options to achieve this are scarce, and moreover may only fit a general use case, which is not likely to suit the needs of your business.

Luckily, Oracle allows developers to integrate custom components to Oracle CEC, and continually improves a powerful set of REST APIs which can be used to search folders and documents. Combining the two will result in an integrated search solution for the site which can be tailor-made to fit the functional and visual requirements of the business. In this post I will share my experience developing a custom search component for CEC, and provide a glimpse into future enhancements and capabilities.

The Solution: Integrate a Custom Search Interface

I began by integrating a global search bar into the header of the layout for the site. This gives users the ability to search for content on the fly regardless of where they are in the site. Once a user enters a search term, they can press enter, or click the “Search” button to initiate the search. The user and search term are then redirected to a search results page.

The search results page is like any other page of the site, except it has been hidden from display in the header navigation. I have placed my “Search-Results-Page” custom component within the page, which performs all the actions and rendering for the search.

The search term is picked up and decoded, then passed into Oracle’s API for full-text document searching. Using full-text search strengthens the search by looking for matches across multiple file and folder properties, such as:

  • The name
  • The text content of the file
  • The file extension
  • The owner’s name
  • The latest modified user’s name
  • The folder description/tags

The matching items are then returned to the component, where it applies pagination to the results, and injects that data into a template to build the results page. The template was modularly designed so that it can be easily updated or replaced to structure the response in a format that will match a specific look and feel without compromising the core search functionality behind the component.

Using several other API endpoints available, I added some additional features to the results page, such as the ability to generate thumbnail previews for the results as they are displayed to the page. I apply a thumbnail next to the info of each document returned, and display a folder icon next to the folders.

Hovering your cursor over the thumbnail will indicate the image can be enlarged. Clicking will expand the thumbnail and overlay it in the center of the page for the user to quickly inspect and verify whether it is the document they have been looking for:

For all documents returned in the results I have included actions to “View” and “Download”. Clicking the “View” icon will utilize another API endpoint to generate and open an HTML5 rendition of the full document.

Among other document attributes returned from the search are the content types (folder or file). Some users may want to view only one or the other, which can be made possible through a filter facet menu surfaced alongside the results. Logic can be included to handle a number of different sorting and filtering tasks.

Beyond a customizable display, there are also custom settings that can allow a site administrator to make near-immediate modifications to the search results component to adjust behaviors or adapt its use for multiple sites used within the organization. For example, the Results Limit and Results Per Page value can be adjusted for more results included on searches, and how many items are included in each page, respectively. Additionally, I’ve included a “Root Search Folder” selection, which allows the site admin to point searches at a specific folder (and all of its contents) as the target of the search for that site. This setting can be applied per instance, so any number of sites can target different folders of content to search upon, providing contextualization of searchable content on the basis of which site the search is being performed against.

The below settings dictate a total of at most 80 items be returned, at a max of 10 pages (8 results per page), and the search will target folders and documents that live within the “Search” folder.

The Vision: Faceted, Robust, and Dynamic Searching… Anywhere

Additional Filtering Capabilities

Filtering content by its type is a small example within a very large list of options which can provide users with the ability to reach more granular results. Adding additional attributes to filter on, and allowing site administrators to decide which filters should be available (or applied by default) can give businesses control on the relevancy of search results.

Targeting More Oracle Cloud Content

In addition to documents and folders, Oracle is continuing to improve on options to search across structured content, digital assets, content collections, and conversations. Additional functionality can be developed to include or separate searches across these various formats on the system.

Targeting Separate Existing Datastores

With API endpoints available, or other methods of JavaScript access available to existing datastores, the solution can also be repurposed to perform searches across existing data sources, and then formatted to be returned within a CEC site.

Improving the UX Out of the Box

The layout and structure of results is a crucial aspect of user experience. Several default templates can be created and bundled with the component to give business owners the opportunity to choose the interface which would best fit their vision for the site, rather than being limited to a single UI or carving out time to design and create a custom interface altogether.

In closing, the steps I outlined above to create a custom search component should illustrate another great feature of Oracle CEC. That feature is the customizable nature of the platform, giving you the ability to extend upon its inherent capabilities to provide an experience molded specifically for your organization. As a company, Fishbowl Solutions recognizes the value of search within the overall user experience, and offers Mindbreeze Inspire search solutions. We also understand the important role search plays within content management, and how effective search solutions can lead to more adoption and use of products like Oracle CEC.

The post Oracle Content & Experience Cloud: Document Search appeared first on Fishbowl Solutions.

Categories: Fusion Middleware, Other

No More ANNOYING Java Applets! WebCenter Configuration Made Easy with Fishbowl’s Admin Suite

Anyone who has used WebCenter Content’s provided administration applets will tell you that using them can be problematic. Most browsers implement measures to protect against Java security issues, and the admin applets frequently get caught in these filters. Accessing the applets often means going through several security prompts, switching to older browsers, or even manually executing the applet files from the server’s file system. Even once the applets are launched, they are slow to load. The problems with these Java-based admin applets create unnecessary frustration when trying to configure and administer an instance of WebCenter Content.

With Fishbowl’s Admin Suite 2.0, the most-used applets have been remade into web-based applets that do not rely on the problematic Java applets. Specifically, Configuration Manager, System Properties, User Admin, and Workflow Admin have received a web makeover, with Repository Manager planned to be added by the end of 2017. All the same functionality is available – updating rules and profiles, editing localization settings, configuring aliases, defining security groups and roles, running workflows, and more – in an updated UI that doesn’t require any of the annoying workarounds listed above.

These new applets are laid out the same as the provided Java applets, complete with Oracle’s included help pages – familiarity with the Java applets will directly translate to the new versions. We’ve made compatibility a priority with these new applets; they have been designed to work with WebCenter Content 10g, 11g, and 12c.

Existing Admin Suite customers can get these new web applets free of charge by upgrading to 2.0.  In addition to these applets, Admin Suite still includes Fishbowl’s most popular products:

  • Advanced User Security Mapping – simplify security mapping and reduce LDAP maintenance with our powerful rules engine
  • Enterprise Batchloader – schedule and batch load content from ERP and CRM systems into WebCenter
  • Subscription Notifier – send automatic email notifications, trigger workflows, update metadata
  • Workflow Solution Set – enhance WebCenter workflows with search capabilities, the ability to filter views, and customize the review pane

You can get an overview of the capabilities and value of Admin Suite by watching a replay of this webinar. For a quick overview of Admin Suite, please visit this page on the Fishbowl website.

If you are interested in purchasing Admin Suite or upgrading your existing copy, please contact us at 952-465-3400 or info@fishbowlsolutions.com and we’d be happy to help you.

The post No More ANNOYING Java Applets! WebCenter Configuration Made Easy with Fishbowl’s Admin Suite appeared first on Fishbowl Solutions.

Categories: Fusion Middleware, Other

Taking Pivotal Cloud Foundry Small Footprint for a test drive

Pas Apicella - Wed, 2017-11-22 21:55
Pivotal Cloud Foundry (PCF) now has a small footprint edition. It features a deployment configuration with as few as 6 VMs. Review the documentation for download and installation instructions as follows

http://docs.pivotal.io/pivotalcf/1-12/customizing/small-footprint.html

There was also a Pivotal blog post on this as follows:

https://content.pivotal.io/blog/big-things-come-in-small-packages-getting-started-with-pivotal-cloud-foundry-small-footprint

As you can see from this image it's considerably smaller control plane that's obvious.



It is important to understand what the limitations of such an install are as per the docs link below.

http://docs.pivotal.io/pivotalcf/1-12/customizing/small-footprint.html#limits

Installing the small footprint looks identical from the Operations Manager UI in fact it's still labelled ERT and from the home page of Operations Manager UI your wouldn't even know you had the small footprint



If you dig a bit further and click on the "ERT tile" and then select "Resource Config" left hand link you will then clearly know it's the Small Footprint PCF install.


I choose to use internal MySQL database and if I didn't then it could be scaled back even more then the default 7 VM's I ended up with.

Lastly I was very curious to find out what jobs are placed on which service VM's. Here is what it looked like for me when I logged into bosh director and run some bosh CLI commands
  
ubuntu@ip-10-0-0-241:~$ bosh2 -e aws vms --column=Instance --column="Process State" --column=AZ --column="VM Type"
Using environment '10.0.16.5' as user 'director' (bosh.*.read, openid, bosh.*.admin, bosh.read, bosh.admin)

Task 73. Done

Deployment 'cf-a96683b17697c86b8c90'

Instance Process State AZ VM Type
backup-prepare/16356c40-1f20-42f0-8f2e-de45549be797 running ap-southeast-2a t2.micro
blobstore/b6e22107-018b-425d-8fe4-ab47eeaf2c75 running ap-southeast-2a m4.large
compute/5439f18f-c842-40a2-b6f3-faf6b6848716 running ap-southeast-2a r4.xlarge
control/68979d93-d12b-4d87-b110-d3d41a48b261 running ap-southeast-2a r4.xlarge
database/a3efedaa-4df6-48f5-9f20-61cf3d9f3c1b running ap-southeast-2a r4.large
mysql_monitor/d40ef638-d2d0-488e-b937-99a7f5b5b334 running ap-southeast-2a t2.micro
router/f9573547-c5a1-43d4-be02-38a1d9e9c73e running ap-southeast-2a t2.micro

7 vms

Succeeded
  
ubuntu@ip-10-0-0-241:~$ bosh2 -e aws instances --ps --column=Instance --column=Process
Using environment '10.0.16.5' as user 'director' (bosh.*.read, openid, bosh.*.admin, bosh.read, bosh.admin)

Task 68. Done

Deployment 'cf-a96683b17697c86b8c90'

Instance Process
autoscaling-register-broker/9feaef45-994e-472c-8ca3-f0c39467dd6b -
autoscaling/184df31d-a64c-49e0-8b6b-27eafdb31ca0 -
backup-prepare/16356c40-1f20-42f0-8f2e-de45549be797 -
~ service-backup
blobstore/b6e22107-018b-425d-8fe4-ab47eeaf2c75 -
~ blobstore_nginx
~ blobstore_url_signer
~ consul_agent
~ metron_agent
~ route_registrar
bootstrap/0dc22a1f-a1ee-4a03-85c6-fed08f37c44a -
compute/5439f18f-c842-40a2-b6f3-faf6b6848716 -
~ consul_agent
~ garden
~ iptables-logger
~ metron_agent
~ netmon
~ nfsv3driver
~ rep
~ route_emitter
~ silk-daemon
~ vxlan-policy-agent
control/68979d93-d12b-4d87-b110-d3d41a48b261 -
~ adapter
~ auctioneer
~ bbs
~ cc_uploader
~ cloud_controller_clock
~ cloud_controller_ng
~ cloud_controller_worker_1
~ cloud_controller_worker_local_1
~ cloud_controller_worker_local_2
~ consul_agent
~ doppler
~ file_server
~ locket
~ loggregator_trafficcontroller
~ metron_agent
~ nginx_cc
~ policy-server
~ reverse_log_proxy
~ route_registrar
~ routing-api
~ scheduler
~ silk-controller
~ ssh_proxy
~ statsd_injector
~ syslog_drain_binder
~ tps_watcher
~ uaa
database/a3efedaa-4df6-48f5-9f20-61cf3d9f3c1b -
~ cluster_health_logger
~ consul_agent
~ galera-healthcheck
~ gra-log-purger-executable
~ mariadb_ctrl
~ metron_agent
~ mysql-diag-agent
~ mysql-metrics
~ nats
~ route_registrar
~ streaming-mysql-backup-tool
~ switchboard
mysql-rejoin-unsafe/01a0aec3-b103-4c09-bc69-cabc61c513cc -
mysql_monitor/d40ef638-d2d0-488e-b937-99a7f5b5b334 -
~ replication-canary
nfsbrokerpush/829f0292-59ab-4824-8b0b-c4af4bddbce0 -
notifications-ui/50972440-36cd-499d-ad7c-eef4df7e604b -
notifications/968d625e-af63-4e2f-a59c-f6b789ef1cff -
push-apps-manager/3d9760d7-6f09-453c-a052-32604b6a3235 -
push-pivotal-account/5a8782ad-82eb-4469-8242-f0873bc4a587 -
push-usage-service/9b781db1-171b-4abe-92f4-7445fd3d487f -
router/f9573547-c5a1-43d4-be02-38a1d9e9c73e -
~ consul_agent
~ gorouter
~ metron_agent
smoke-tests/a8e2ff97-bae1-4594-90fc-ec8c430fd620 -

77 instances

Succeeded

Now, with Small Footprint, you have yet another way to bring PCF to your organization!
Categories: Fusion Middleware

Using Spring Boot Actuator endpoint for Spring Boot application health check type on PCF

Pas Apicella - Sun, 2017-11-19 04:41
An application health check is a monitoring process that continually checks the status of a running Cloud Foundry application. When deploying an app, a developer can configure the health check type (port, process, or HTTP), a timeout for starting the application, and an endpoint (for HTTP only) for the application health check.

To use the HTTP option your manifest.yml would look like this

---
applications:
- name: pas-cf-manifest
  memory: 756M
  instances: 1
  hostname: pas-cf-manifest
  path: ./target/demo-0.0.1-SNAPSHOT.jar
  health-check-type: http
  health-check-http-endpoint: /health
  stack: cflinuxfs2
  timeout: 80
  env:
    JAVA_OPTS: -Djava.security.egd=file:///dev/urandom
    NAME: Apples

Using a HTTP endpoint such as "/health" is possible once you add the Spring Boot Actuator maven dependency as follows
  
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-actuator</artifactId>
</dependency>

More Information

https://docs.run.pivotal.io/devguide/deploy-apps/healthchecks.html
Categories: Fusion Middleware

Karamozov

Greg Pavlik - Fri, 2017-11-10 12:02
"Brothers, have no fear of men's sin. Love a man even in his sin, for that is the semblance of Divine Love and is the highest love on earth. Love all God's creation, the whole and every grain of sand in it. Love every leaf, every ray of God's light. Love the animals, love the plants, love everything. If you love everything, you will perceive the divine mystery in things. Once you perceive it, you will begin to comprehend it better every day. And you will come at last to love the whole world with an all-embracing love. Love the animals: God has given them the rudiments of thought and joy untroubled. Do not trouble it, don't harass them, don't deprive them of their happiness, don't work against God's intent. Man, do not pride yourself on superiority to the animals; they are without sin, and you, with your greatness, defile the earth by your appearance on it, and leave the traces of your foulness after you -- alas, it is true of almost every one of us! Love children especially, for they too are sinless like the angels; they live to soften and purify our hearts and, as it were, to guide us. Woe to him who offends a child! Father Anfim taught me to love children. The kind, silent man used often on our wanderings to spend the farthings given us on sweets and cakes for the children. He could not pass by a child without emotion. That's the nature of the man.

At some thoughts one stands perplexed, especially at the sight of men's sin, and wonders whether one should use force or humble love. Always decide to use humble love. If you resolve on that once for all, you may subdue the whole world. Loving humility is marvellously strong, the strongest of all things, and there is nothing else like it....

Brothers, love is a teacher; but one must know how to acquire it, for it is hard to acquire, it is dearly bought, it is won slowly by long labour. For we must love not only occasionally, for a moment, but for ever. Everyone can love occasionally, even the wicked can.

My brother asked the birds to forgive him; that sounds senseless, but it is right; for all is like an ocean, all is flowing and blending; a touch in one place sets up movement at the other end of the earth. It may be senseless to beg forgiveness of the birds, but birds would be happier at your side -- a little happier, anyway -- and children and all animals, if you were nobler than you are now. It's all like an ocean, I tell you. Then you would pray to the birds too, consumed by an all-embracing love, in a sort of transport, and pray that they too will forgive you your sin. Treasure this ecstasy, however senseless it may seem to men."

Why We Chose Mindbreeze for Enterprise Search: Fishbowl’s Competitive Analysis Across Search Platforms

Comparing Mindbreeze to Google Cloud Search, Coveo, Lucidworks, Yippy, Elasticsearch, and Solr

Last month we discussed replacing the Google Search Appliance (GSA) and the Top 5 Reasons We Chose Mindbreeze. In this follow-up, we’ll explore the other vendors who made our shortlist and how they all stack up. In case you missed the last post, here’s a recap of the key requirements against which we were evaluating each solution:

  • Options for searching on-premise content
  • Connectors and connector frameworks for indexing non-web data sources
  • Support for public and secure use cases
  • Tools and APIs for search interface integration
  • Minimal development efforts and ongoing administration required
Mindbreeze vs. Google Cloud Search

As a Google Premier Partner and GSA implementer, we naturally looked to Google for GSA replacement options. At the time of our evaluation, Google Cloud Search did not have any features available to address indexing on-premise content or serving that content through websites or web applications other than their own cloud search interface. In addition, the status of their security integration options and administration experience remained widely unknown. While it was always clear that Google’s new enterprise search index would be cloud-based, the options for pushing enterprise content from on-premise repositories into that index remain unclear. The initial product direction for Google Cloud Search (previously referred to as Springboard) focused on indexing Google’s G Suite data sources such as Gmail, Google Calendar, and Google Drive. Google has since changed their directional statements to reemphasize their intention to implement indexing mechanisms for on-premise content, but even at the time of this writing, that technology is yet to be released.

Our decision to pursue solutions other than Google, and ultimately partner with Mindbreeze, largely came down to the fact that we couldn’t confidently assure our customers that Google would have a replacement ready (and able to meet the aforementioned requirements) in time for the GSA’s end of life. While I continue to be impressed with Google’s cloud innovations and hope those eventually materialize into enterprise search options, Google Cloud Search remains in its infancy.

Mindbreeze vs. Coveo

As a leader in the enterprise search and knowledge management space, Coveo has ranked well for the past several years among the analyst reports for this market. They have a mature product which made our short list of possible solutions. Two primary concerns surrounded Coveo when compared to Mindbreeze and other vendors. First, their product direction is heavily cloud-focused, available only on Amazon Web Services, with a decreasing investment in on-premise search. Our customer base has a strong need to index on-premise content along with a reasonable amount of customers who prefer the search engine itself be available on premise for governance reasons.

The other concern surrounding Coveo was price. By their own admittance, it is one of the most expensive solutions on the market. Mindbreeze was able to meet our requirements as well or better than Coveo, while providing a stronger commitment to on-premise indexing at a more attractive price point.

Mindbreeze vs. Lucidworks

Lucidworks offers enterprise support for the open source search platform Apache Solr. Their flagship product, Lucidworks Fusion, builds on Solr to add enterprise search features, including connectors and administration interfaces. Our primary reasons for preferring Mindbreeze over Lucidworks concern the ease and speed of both deployment and ongoing administration. While the Fusion platform goes a long way in creating a productized layer on top of Solr, the solution still requires comparatively more work to size, provision, configure, and maintain than Mindbreeze.

Another concern during evaluation was the less-flexible security model available with Lucidworks when compared to Mindbreeze. Mindbreeze supports ACL inheritance from container objects which means if a new user is granted access to a folder containing 50,000 items, only one item (the folder container) must be reindexed to apply the new permissions. Lucidworks applies permissions to each document, so all 50,000 documents would need to be reindexed. While Lucidworks was able to meet our indexing requirements, we felt Mindbreeze offered a shorter time to value, easier ongoing administration, and more flexible security options.

Mindbreeze vs. Yippy

The Yippy Search Appliance attempts to offer close feature parity to the GSA and is available as a cloud solution or an on-premise appliance. Our biggest concern with Yippy, when compared to Mindbreeze, was its immaturity as an enterprise search product. Born out of the Yippy metasearch engine, the Yippy Search Appliance was introduced in 2016 specifically in response to the GSA’s end of life.

The solution is notably absent from consideration by both Forrester and Gartner in their respective 2017 market reports which base inclusion criteria on factors such as referenceable enterprise customer base and proven market presence. The solution also lacks interfaces for customers and partners to create custom connectors to proprietary data sources, an important requirement for many of our customers. As a search appliance, we felt Mindbreeze offered a lower risk solution with a longer history, large reference customer base, and mature feature set.

What about open source options?

Open source options were considered during our evaluation but quickly eliminated due to the vastly greater amount of development time and steeper customer learning curve associated with their implementation. For these reasons, we felt open source search solutions were not a good fit for our customers. Due to the high volume of questions we get regarding these options, I felt it worthwhile to include a few comments on the most popular open sources search tools.

Elasticsearch

Elasticsearch is a popular open source search and analytics project created by Elastic.co. Elastic itself doesn’t claim to be an enterprise search solution, but they do offer enterprise analytics solutions, and the Elasticsearch technology is often embedded into enterprise applications to provide search functionality. It’s easy to see the confusion this can create. Gartner did not include Elastic in their 2017 Magic Quadrant for Insight Engines. Elastic was included in the Forrester Wave on Cognitive Search and Knowledge Discovery as a nonparticipating vendor where Forrester stated, “Elastic says that it is not in the enterprise search market, but many enterprise customers ask Forrester about Elasticsearch, so we have included Elastic…” As a search tool, we found Elastic was better suited to log analytics than enterprise search as it lacks many enterprise search features including security, connectors, and pre-built search apps.

Solr

Apache Solr is a widely used open source search project. Many contributions to the project are made by Lucidworks (mentioned above) whose Fusion platform extends this core technology. Standalone Solr is a framework for creating a custom search engine implementation. While powerful and often used to build highly specialized search tools, it is missing out-of-the-box enterprise features including connectors, administration interfaces, and mechanisms to support secure search.

Lucene

Apache Lucene is a popular open source search engine framework. It’s a low-level library which implements indexing and search functionality and must be integrated into another application for use. Lucene provides the base search engine behind both Solr and Elasticsearch.

Finding Success with Mindbreeze

After undergoing our evaluation last winter and joining the Mindbreeze partner network, we continue to find Mindbreeze offers an excellent combination of built-in features with tools for extending capabilities when necessary. In the past year we’ve released our Oracle WebCenter Content Connector for Mindbreeze, had ten employees complete the Mindbreeze Expert Certification and helped a long-time customer migrate from GSA to Mindbreeze. If you have any questions about our experience with Mindbreeze or would like to know more, please contact us or leave a comment below.

Time running out on your GSA?

Our expert team knows both GSA and Mindbreeze. We’ll help you understand your options and design a migration plan to fit your needs.

Contact Us

The post Why We Chose Mindbreeze for Enterprise Search: Fishbowl’s Competitive Analysis Across Search Platforms appeared first on Fishbowl Solutions.

Categories: Fusion Middleware, Other

How to Configure the Top 4 GSA Features in Mindbreeze – Plus 6 New Favorites

In the past few weeks, we’ve looked at why fishbowl chose Mindbreeze as a GSA replacement and how one of our GSA customers transitioned to Mindbreeze. Today I’ll share how to set up the most-used GSA functionality within the Mindbreeze InSpire enterprise search appliance.

Dynamic Navigation

The GSA’s Dynamic navigation enables users to refine a search using metadata attributes as filters. Within Mindbreeze this functionality is called Filter Facets. A default set of filters can be defined for each Mindbreeze client service based on the metadata available from the various indexed content sources. The client service is roughly equivalent to the GSA’s client frontend parameter (as opposed to the proxystylesheet which also references a frontend but is more comparable to a search app in Mindbreeze). In addition to the filters defined for a client service, you can also define filters within custom search apps by explicitly adding the desired filters. This is true for both the GUI-based Mindbreeze Search App Designer, and for search apps built using the Mindbreeze API.

What’s New: Mindbreeze offers a multi-select interface for search facets. This was a much-requested GSA enhancement and allows you to refine your search by selecting among several facet options rather than a single option as available with GSA. Mindbreeze also allows configuration of whether multiple selections should apply AND or OR constraints across the multiple selected values.

Configuring Mindbreeze Search Filters

From the Client Services tab in the Mindbreeze Management Center expand the desired client service and navigate to the Filters heading. Check the box next to each metadata field you want to include as a filter. Any searches performed against this client service will return these filters unless overridden in an individual search app.

Document Previews

The GSA’s document preview engine creates image renditions of Word, PowerPoint, and PDF files for up to 30 pages of a document; previews or thumbnails are not available for other file types out of the box. The Mindbreeze preview engine supports preview settings for 91 different file types. For many files, the preview engine can be configured to create both a document thumbnail, for use on results pages, and a content preview which is typically displayed as a modal popup. For example, Mindbreeze can display a thumbnail of a Word document next to the result title, and a preview link which displays a full-context PDF rendition as the document preview.

What’s New: In addition supporting more files types and creating thumbnails, the Mindbreeze previews highlight all instances of your query terms in the preview rendition making it easy to see where in the document the relevant keywords occur. Mindbreeze previews are controlled by the Mindbreeze filter service which controls many aspects of how document contents are processed and extracted for indexing. The Mindbreeze SDK provides an interface for creating custom filter plugins which can alter or add to the standard preview generation capabilities.

Configuring Mindbreeze Previews

From the Filters tab in the Mindbreeze Management Center, expand the desired Filter Service. For each applicable file type, select the desired filter plugin. For example, to create PDF previews of Excel files, navigate to xlsx and select FilterPlugin.OfficeDocumentToPDFContentFilter. Like GSA, Mindbreeze previews are generated during indexing. Any existing documents will need to be reindexed for preview configuration changes to appear in search results.

Mindbreeze Preview Config

Custom Synonyms

The GSA and Mindbreeze search appliances both provide query transformation services for automatic modification of search queries. Synonym transformation allows you to find search results by looking for different synonyms of a word, therefore the query is transformed to search for every term listed in the synonyms list. For example, if a user searches for “FAQ,” the appliance could also look for documents containing “frequently asked questions”.

What’s New: Although a shared synonyms file is included with Mindbreeze out of the box, unique synonyms may optionally be defined for individual content sources. This means if you use different terms in your ERP system than on your customer extranet, you can define synonymous terms for their respective sources. Mindbreeze also offers two additional query transformation engines that address specific use cases often handled with synonyms in the GSA. The first is Replacements, which completely replace a defined term with an alternative term or terms. The second is Vocabulary, which specifies preferred and alternative versions of defined search terms. Vocabulary entries are treated as synonyms; however, the preferred label is given more weight than the alternate label when determining relevancy.

Configuring Mindbreeze Synonyms

Select Synonyms from the Search Experience menu in the Mindbreeze Management Center. In the table displayed, enter synonymous terms with one term per column and one term group per row as shown.

Mindbreeze query transformation can be applied globally or to a specific data source. To apply the Synonyms to all content, navigate to the Indices tab and locate Query Transformation Services at the bottom of the page. Add the SynonymTransformer from the picklist. Expand the configuration and add the following configuration: Property: SYNONYM_CSV_FILE_PATH and Value: /data/resources/synonyms.csv. To configure synonyms for an individual index perform these same steps within the Query Transformation Services section of an individual index. You can optionally specify a path to a different synonyms file than the default show here.

Suggestions

Both GSA and Mindbreeze can provide query suggestions within the search box that complete a user’s query as they type. The GSA used popular search queries from the past 90 days to determine the top suggestions. Mindbreeze offers a similar option called Similar Queries along with four other possible data sources from which to generate suggestions. Like Filter Facets, suggestions can be defined for each Mindbreeze client service.  Suggestion data is also available using the Mindbreeze Suggest API (api.v2.suggest). This API is useful when adding Mindbreeze suggestions to an existing search box on a website or application. The Mindbreeze Suggest API is similar to the GSA’s Query Suggestion Service /suggest Protocol.

What’s New: Unlike the GSA, Mindbreeze suggestions can be provided from a number of different data sources. Suggestions can even be displayed when a user places their cursor in the search box before entering any characters; this is called Initial Suggest. The following suggestion options are available in Mindbreeze:

  • Similar queries (this is comparable to the GSA’s suggestions feature)
  • Suggestions from a CSV file
  • Mindbreeze tabs to search for the current search term
  • Document properties from indexed metadata (e.g. Document Titles)
  • Recent queries from the last searches performed by a user

The ability to load suggestions from a CSV file provides an easy way to pre-populate suggestions and ensures they remain in the suggestion pool even if they are not frequently used. This was a common enhancement request from GSA customers.

Configuring Mindbreeze Suggestions

From the Client Services tab in the Mindbreeze Management Center expand the desired client service and navigate to the Suggest Settings and Initial Suggest Settings headings, respectively. Check the box next to each suggestion source you want to enable for this client service. Any searches performed against this client service will return these suggestions unless overridden in a direct API request. If suggestions from a CSV file are desired, the path to the CSV file must be defined under the heading Suggest Settings (Concept CSV) also located on the client service configuration page.

Beyond GSA – 6 New Things We Love About Mindbreeze

While Mindbreeze offers GSA parity in many ways, there are plenty of upgrades to be found. Here are a few of our favorites:

  • Mindbreeze lets you boost (i.e. bias) the overall weight of a metadata field enabling you to increase (or decrease) the general importance of fields like title, subject, or keywords.
  • Mindbreeze provides built-in search analytics and application performance monitoring via the integrated App Telemetry platform.
  • Mindbreeze offers a native user feedback mechanism including screenshots from the users’ search results.
  • Mindbreeze provides access to the appliance OS and filesystem. You can upload your own files to support advanced configurations or create custom interfaces. This also allows the use of standard backup techniques on the index and configuration files.
  • Mindbreeze does not require secondary servers for connectors (e.g. Tomcat); even custom connectors run directly on the appliance.
  • Mindbreeze includes a search app builder which provides drag and drop tools for creating use-case specific search apps without coding.

If you have a GSA approaching expiration, we believe Mindbreeze offers the quickest and most reliable search replacement path. As a Mindbreeze partner, we offer both resale and implementation services, and as a long-time GSA partner, we’re familiar with the functionality of both platforms. If you have questions or would like to know more, please contact us or leave a comment below.

Time running out on your GSA?

Our expert team knows both GSA and Mindbreeze. We’ll help you understand your options and design a migration plan to fit your needs.

Contact Us

The post How to Configure the Top 4 GSA Features in Mindbreeze – Plus 6 New Favorites appeared first on Fishbowl Solutions.

Categories: Fusion Middleware, Other

Testing network connectivity from Cloud Foundry Application Instances

Pas Apicella - Sat, 2017-10-28 04:43
This app below simply tests whether a host:port is accessible from a CF app instance. For example can my application instance access my Oracle Database Instance running outside of PCF given application instances need network access to the database database for example.

You can use bosh2 ssh to get to the Diego Cells if you have access to the environment or even "cf ssh" if that has been enabled.

GitHub URL:

https://github.com/papicella/cloudfoundry-socket-test

Success

pasapicella@pas-macbook:~$ http http://pas-cf-sockettest.cfapps.io/www.google.com.au/80
HTTP/1.1 200 OK
Connection: keep-alive
Content-Length: 81
Content-Type: application/json;charset=UTF-8
Date: Wed, 25 Oct 2017 08:38:33 GMT
X-Vcap-Request-Id: 8fd05c77-f680-4966-558b-c45e71825fa0

{
"errorMessage": "N/A",
"hostname": "www.google.com.au",
"port": "80",
"res": "SUCCESS"
}
Failure

pasapicella@pas-macbook:~$ http http://pas-cf-sockettest.cfapps.io/10.0.0.10/8080
HTTP/1.1 200 OK
Connection: keep-alive
Content-Length: 110
Content-Type: application/json;charset=UTF-8
Date: Wed, 25 Oct 2017 11:52:18 GMT
X-Vcap-Request-Id: 91ad2359-7d95-49c6-4538-548e480b7820

{
"errorMessage": "Connection refused (Connection refused)",
"hostname": "10.0.0.10",
"port": "8080",
"res": "FAILED"
}

Categories: Fusion Middleware

Still Stuck on SiteStudio? Move Your Intranet and Modernize with WebCenter Portal

Fishbowl’s Director of Solutions, Jerry Aber, contributed to this blog post.

Surprisingly, there are still many SiteStudio (Oracle WCM) customers out there using the product for their employee intranet. We just chatted with another one this week, in fact. I say surprisingly because even though the product is technically under support (extended lifetime) until 2019, there are so many advantages and benefits of upgrading a SiteStudio intranet to Oracle WebCenter Portal. Oracle themselves outlined a few in their statement of direction document released back in 2012.

Fishbowl has done numerous WebCenter Portal projects over the last 5 years, and some of those have been SiteStudio to Oracle WebCenter Portal upgrades. We have found for employee intranets specifically that WebCenter Portal is the obvious choice due to its flexibility and how it aggregates content, applications, and data onto a single pane of glass. No more link farms, poorly branded sub-pages, and confusing navigation. If your organization is still  using SiteStudio for its intranet, perhaps this blog post will persuade you to upgrade and modernize today.

SiteStudio Revisited

SiteStudio sites are built on the premise of Templates, Regions, Fragments and Lists with a site design overlaying the top of the structure outlined by its architecture. It did include inline contribution and editing model that helps contributors manage the site with less IT intervention. However, the contribution model wasn’t very streamlined as essentially Word documents were used to structure page content and then converted to HTML. This caused numerous page formatting issues.

Compare this to ability with WebCenter Portal – and enhanced with Fishbowl’s Portal Solution Accelerator – to edit text inline of portal pages, and you have a contribution model that is truly optimized for business user contribution. The impact of this is more frequent updates to page content, which keeps employees coming back for new information leading to better engagement.

SiteStudio to WebCenter Portal: Making the Move

As customers consider their employee intranet/portal roadmap and SiteStudio upgrade path, a big concern that comes up frequently is regarding the overall “migration” from a web page-based SiteStudio intranet site to a Portal-based site. There is no natural migration/upgrade roadmap for making this happen as the underlying technologies are considerably different. Additionally, there are two large issues to consider: The SiteStudio code used to render the content, and that the web content is stored in SiteStudio data files.

However, what we’ve found is that WebCenter Portal sites can be created to consume the SiteStudio assets and use the SiteStudio development model by the leveraging what’s called the Content Presenter task flow. This is one way to ensure a tight and clean integration with the Oracle Content Server. This model works nicely when SiteStudio designs and tools are used, but does not translate well to any portal development paradigms. Such paradigms are way more flexible, modular and use current web technology patterns, such as Oracle JET, that not only make the site look nice but keeps it performing at a high-level.

Also, keep in mind this relegates you to sticking with the SiteStudio Data File storage model for your web content which can be a challenge when it comes to managing content and sharing content around the organization.

So, given that, what are some other questions you and your organization can ask to determine if upgrading from SiteStudio to Oracle WebCenter Portal makes sense and would be beneficial to your organization. Consider:

  • Is sticking with a SiteStudio design and development model future-proofing your platform? Does that help you deliver agile-like project and quickly respond to changing needs?
  • Does your development team want to use new web technology frameworks like Oracle JET?
  • Does your content need to be shared easily and seamlessly without conversion? Do  you want to continue to use Oracle WebCenter Content as your enterprise repository?
  • Do you want to provide easier contribution tools for your end users to manage the site better?
  • Does your organization have an initiatives around enhancing employee engagement, increasing employee retention, or attracting top talent – with your employee intranet viewed as the vehicle to help drive these initiatives?

If you answered yes to any of the above, the time is right to move from SiteStudio to WebCenter Portal. Only WebCenter Portal can deliver a modern and engaging experience for employee intranets, with mobile first design capabilities and the technology foundation for future portal creation at scale – on premise or in the cloud. It also provides the tightest integration with Oracle WebCenter Content, enabling your organization to centralize its high value content assets into an industry leading enterprise content management system.

Oracle WebCenter Portal 12c Value Proposition

WebCenter Portal provides all of this and more. It is a true portal platform that satisfies requests for a better user experience with better performing page loads, and page to page navigation. Furthermore it enables:

  • The ability to store content in a manner so that it can be managed and shared easily.
  • The use of inline contribution of content features using WYSIWYG capabilities.
  • Leveraging newer web technologies such as Oracle Jet, Angular, and others.
  • Integrations with Oracle applications such as E-Business Suite, PeopleSoft, and Taleo – surfacing up content from these systems directly within the portal.

SiteStudio was a great tool for building websites, but one could argue that it was never intended to be used for building employee portals or intranets. If your organization is looking to do just that, and take its employee intranet to the next level, Oracle WebCenter Portal is the clear choice.

 

The post Still Stuck on SiteStudio? Move Your Intranet and Modernize with WebCenter Portal appeared first on Fishbowl Solutions.

Categories: Fusion Middleware, Other

Manufacturer Replaces the Google Search Appliance with Mindbreeze for Intranet and Website Search: From Racking to Go-Live in 37 Days

In today’s post I’m excited to share the story of a recent Mindbreeze deployment. One of our long-time customers, a global leader in the field of industrial automation, needed a replacement for their expiring Google Search Appliances (GSAs). They had used the GSA to power the search on their public-facing website as well as their employee intranet. When Google announced the GSA’s end of life, they were left in a need of a replacement. Due to its similar feature set and architecture, Mindbreeze offered an easy migration from GSA and allowed existing customizations to be reused.
Working with Fishbowl to implement Mindbreeze went very well. The expertise they brought enabled us to meet our aggressive timeline to remove the Google Search Appliances. Fishbowl’s knowledge allowed them to be flexible to our needs during implementation while still covering all the necessary material. We appreciated that.

Application Development and Support Manager

Google Search Appliance (GSA) Replacement, Alternatives, and Migration
GSA Migration Requirements

Google Search ApplianceIn order to provide comprehensive website search, this organization needed to index content from three different sources. First, they needed to crawl the HTML pages on the site itself. Second, they needed to index records in their parts and products database. And third, they needed to index PDFs and other supporting product documentation stored in Oracle WebCenter Content (their document management system). In order to serve their sales and distribution partners, they needed the option to restrict a subset of this content to only logged-in partners. This organization had previously integrated GSA search results into their website using a custom-built search interface which consumed the GSA’s XML response. They planned to reuse the front-end components of that integration while replacing the backend with Mindbreeze.

For the intranet search, they needed to index secure documents from Oracle WebCenter Content. WebCenter Content was also the platform through which the secure results would be served to employees. The search results on the intranet needed to include both the access-controlled internet documents, as well as the customer and partner-facing documents that would also be accessible from the website.

Mindbreeze Implementation

We began the implementation by configuring Mindbreeze to index the necessary data sources. Each of their three content sources required different indexing tools. The approach was similar to how the same data had been previously indexed using the GSA. First the Mindbreeze web crawler was configured to crawl the site. We were able to reuse the crawl patterns already defined when configuring the GSA. Next, content from their parts and products database was indexed using the Mindbreeze Data Integration connector. This connector uses the Talend ETL platform to create jobs that extract, transform, and load structured data into Mindbreeze without a custom connector. In this case the data integration job was configured to connect to the same tables they had previously indexed with the GSA Connector for Databases. Finally, indexing was configured for the documents stored in Oracle WebCenter Content. In order to index WebCenter Content, the customer purchased Fishbowl’s Oracle WebCenter Content Connector for Mindbreeze. Unlike GSA, Mindbreeze connectors can run directly on the appliance and do not require any off-board connector servers. The connector is deployed via a Mindbreeze plugin and corresponding WebCenter Content component and leverages the Mindbreeze connector framework. The indexing criteria had already been determined during the GSA integration and was able to be copied directly into Mindbreeze. Items from Oracle WebCenter Content were separated into three groups—public content, partner-only content, and secure intranet content. These content groups could then be restricted based on the various serving configurations.

The Mindbreeze application was a step up from our previous search application. We had no problems crawling multiple data sources (website, database, WebCenter) and serving that content to multiple front ends. Although there was an initial learning curve, it is easy to edit configurations and rebuild indexes with very little or no downtime. And the onboard analytics make troubleshooting issues a breeze.

Web Developer

Once indexing was configured, the results needed to be integrated into the website and intranet. Mindbreeze provides a REST API which returns results in JSON format. This integration is comparably easier than working with the GSAs XML or XSLT responses. Because this customer had already written an integration to facilitate communication between the GSA and their website, built using Adobe Experience Manager, they were able reuse their existing site’s search interface. Search requests to the GSA were replaced with calls to the Mindbreeze search API. This integration also controlled the scope of the search based whether or not a user was allowed to access partner-only content.

For the intranet, the results were embedded directly into the Oracle WebCenter Content web application. The customer leveraged the default Mindbreeze search interface, but customized the look and feel using their own style sheet. This gave them the look of a tightly integrated search page but required less than an hour of development to implement. In order to provide secure search, the Mindbreeze authentication mechanism included with the connector was configured. This mechanism passes the identity of a WebCenter user to the Mindbreeze appliance at serve time in much the same way as security search was previously configured with GSA. The Mindbreeze appliance then uses this identity to resolve the access control lists (ACLs) placed on the documents during indexing. This approach is similar to the early-binding options available with the GSA and allows granular access controls to perform well at scale.

Results

The entire project from racking the Mindbreeze appliance to releasing the solution in production took 37 days—although the total days of work effort was considerably less. This project focused on one-to-one replacement of GSA functionality to ensure completion in time for the customer’s upcoming Google Search Appliance expiration. Initial user feedback indicates improved relevancy compared to the previous GSA integration. Future enhancements include implementing rich search suggestions and document previews to further enrich search capabilities.

If you have a GSA approaching expiration, we believe Mindbreeze offers the quickest and most reliable search replacement path. As a Mindbreeze partner, we offer both resale and implementation services, and as a long-time GSA partner, we’re familiar with the functionality of both platforms. If you have questions or would like to know more, please contact us or leave a comment below.

Time running out on your GSA? Our expert team knows both GSA and Mindbreeze. We’ll help you understand your options and design a migration plan to fit your needs.
Contact Us

The post Manufacturer Replaces the Google Search Appliance with Mindbreeze for Intranet and Website Search: From Racking to Go-Live in 37 Days appeared first on Fishbowl Solutions.

Categories: Fusion Middleware, Other

Just installed Pivotal Cloud Foundry, what's next should I login to Apps Manager?

Pas Apicella - Sun, 2017-10-22 06:50
I get this question often from customers. Pivotal Cloud Foundry has just been installed and the API endpoint to target the instance is working fine. In short we want to do the following before we get developers onto the platform to ensure we no longer using the UAA server admin login details from the CLI or Apps Manager UI.

  • Create a new ADMIN user which will be used to configure Apps Manager ORGS and spaces for the developers
  • Create an ORG
  • Create at least one Quota maybe more to control memory limit and application instances within an ORG
  • Assign the quota to your ORG
Steps

--> Create a new ADMIN user which will be used to configure Apps Manager ORGS and spaces for the developers

1. Login to Ops Manager VM using SSH for example
2. Target the UAA server as shown below

Eg: $ uaac target uaa.YOUR-DOMAIN

ubuntu@opsmanager-pcf:~$ uaac target uaa.system.YYYY --skip-ssl-validation
Unknown key: Max-Age = 2592000

Target: https://uaa.system.YYYY

3. Authenticate and obtain an access token for the admin client from the UAA server

Note: Record the uaa:admin:client_secret from your deployment manifest

ubuntu@opsmanager-pcf:~$ uaac token client get admin -s PASSWD

Successfully fetched token via client credentials grant.
Target: https://uaa.system.YYYY
Context: admin, from client admin

4. Use the uaac contexts command to display the users and applications authorized by the UAA server, and the permissions granted to each user and application. Ensure in the "scope" field that "scim.write" exists

ubuntu@opsmanager-pcf:~$ uaac contexts

[0]*[https://uaa.system.YYYY]
  skip_ssl_validation: true

  [0]*[admin]
      client_id: admin
      access_token: .....
      token_type: bearer
      expires_in: 43199
      scope: clients.read password.write clients.secret clients.write uaa.admin scim.write scim.read
      jti: b1bf094a5c4640dbac4abc5f3bf15b08

5. Run the following command to create an admin user

ubuntu@opsmanager-pcf:~$ uaac user add apples -p PASSWD --emails papicella@pivotal.io
user account successfully added

6. Run uaac member add GROUP NEW-ADMIN-USERNAME to add the new admin to the groups cloud_controller.admin, uaa.admin, scim.read, and scim.write

ubuntu@opsmanager-pcf:~$ uaac member add cloud_controller.admin apples
success
ubuntu@opsmanager-pcf:~$ uaac member add uaa.admin apples
success
ubuntu@opsmanager-pcf:~$ uaac member add scim.read apples
success
ubuntu@opsmanager-pcf:~$ uaac member add scim.write apples
success

--> Create an ORG

1. Login using the new admin user "apples"

pasapicella@pas-macbook:~$ cf login -u apples -p PASSWD -o system -s system
API endpoint: https://api.system.YYYY
Authenticating...
OK

Targeted org system

Targeted space system

API endpoint:   https://api.system.YYYY (API version: 2.94.0)
User:           papicella@pivotal.io
Org:            system
Space:          system

2. Create an ORG as follows

pasapicella@pas-macbook:~$ cf create-org myfirst-org
Creating org myfirst-org as apples...
OK

Assigning role OrgManager to user apples in org myfirst-org ...
OK

TIP: Use 'cf target -o "myfirst-org"' to target new org

--> Create at least one Quota maybe more to control memory limit and application instances within an ORG

1. Here we create what I call a medium-quota which allows 20G of memory, 2 service instances, each application instance can be no more then 1G of memory and only 20 Application Instances can be created using this quota.

pasapicella@pas-macbook:~$ cf create-quota medium-quota -m 20G -i 1G -a 20 -s 2 -r 1000 --allow-paid-service-plans
Creating quota medium-quota as apples...
OK

pasapicella@pas-macbook:~$ cf quota medium-quota
Getting quota medium-quota info as apples...
OK

Total Memory           20G
Instance Memory        1G
Routes                 1000
Services               2
Paid service plans     allowed
App instance limit     20
Reserved Route Ports   0

--> Assign the quota to your ORG

1. Assign the newly created quota to the ORG we created above

pasapicella@pas-macbook:~$ cf set-quota myfirst-org medium-quota
Setting quota medium-quota to org myfirst-org as apples...
OK

pasapicella@pas-macbook:~$ cf org myfirst-org
Getting info for org myfirst-org as apples...

name:                 myfirst-org
domains:              apps.pas-apples.online
quota:                medium-quota
spaces:
isolation segments:

Finally we can add a space to the ORG and assign privileges to a user called "pas" as shown below

- Set OrgManager role to the user "pas"

pasapicella@pas-macbook:~$ cf set-org-role pas myfirst-org OrgManager
Assigning role OrgManager to user pas in org myfirst-org as apples...
OK

- Logout as "apples" admin user as "pas" can now do his own admin for the ORG " myfirst-org"

pasapicella@pas-macbook:~$ cf logout
Logging out...
OK

- Login as pas and target the ORG

pasapicella@pas-macbook:~$ cf login -u pas -p PASSWD -o myfirst-org
API endpoint: https://api.system.YYYY
Authenticating...
OK

Targeted org myfirst-org

API endpoint:   https://api.system.YYYY (API version: 2.94.0)
User:           pas
Org:            myfirst-org
Space:          No space targeted, use 'cf target -s SPACE'

- Create a space which will set space roles for the user "pas"

pasapicella@pas-macbook:~$ cf create-space dev
Creating space dev in org myfirst-org as pas...
OK
Assigning role RoleSpaceManager to user pas in org myfirst-org / space dev as pas...
OK
Assigning role RoleSpaceDeveloper to user pas in org myfirst-org / space dev as pas...
OK

TIP: Use 'cf target -o "myfirst-org" -s "dev"' to target new space

- Target the new space

pasapicella@pas-macbook:~$ cf target -o myfirst-org -s dev
api endpoint:   https://api.system.pas-apples.online
api version:    2.94.0
user:           pas
org:            myfirst-org
space:          dev

Typically we would assign other users to the spaces using "cf set-space-role .."

pasapicella@pas-macbook:~$ cf set-space-role --help
NAME:
   set-space-role - Assign a space role to a user

USAGE:
   cf set-space-role USERNAME ORG SPACE ROLE

ROLES:
   'SpaceManager' - Invite and manage users, and enable features for a given space
   'SpaceDeveloper' - Create and manage apps and services, and see logs and reports
   'SpaceAuditor' - View logs, reports, and settings on this space

SEE ALSO:
   space-users

More Information

Creating and Managing Users with the UAA CLI (UAAC)
https://docs.pivotal.io/pivotalcf/1-12/uaa/uaa-user-management.html

Creating and Managing Users with the cf CLI
https://docs.pivotal.io/pivotalcf/1-12/adminguide/cli-user-management.html

Categories: Fusion Middleware

Replacing the Google Search Appliance: 5 Reasons Fishbowl Chose Mindbreeze

Google Search Appliance (GSA) Replacement, Alternatives, and Migration
When Google said so long to the Google Search Appliance, we went to the market to find a replacement. We chose Mindbreeze. Here’s why.
If you’re reading this, you’ve likely heard the news that Google has discontinued the Google Search Appliance (GSA). As a long-time Google partner and search appliance implementer, this news left Fishbowl and all of our customers in need of a new search solution. We first looked to Google but determined Google Cloud search wouldn’t be a viable replacement in time for the GSA cut-off. We then went to the market to select the product we felt was best suited to meeting the ongoing search needs of our customers. The following key requirements ultimately drove the selection criteria that led us to Mindbreeze:
  • Options for searching on-premise content
  • Connectors and connector frameworks for indexing non-web data sources
  • Support for public and secure use cases
  • Tools and APIs for search interface integration
  • Minimal development efforts or ongoing administration required
Options for searching on-premise content

While it’s true that more content moves to the cloud each year, the majority of our GSA customers still keep most of their enterprise content on premise. Several of the search vendors in the market, including Google, have set a very cloud-heavy product direction. While there’s nothing wrong with that, the reality is that most almost all of our GSA customers need to index on-premise content. Some customers, although a smaller portion, also have requirements that the search solution itself must be on premise. Even those who are open to putting their search index in the cloud must still overcome the bandwidth challenges of indexing large volumes of content across the internet. Mindbreeze, like the GSA, is a search appliance installed on premise and is well suited to indexing both on-premise and cloud content. While Mindbreeze does offer a hosted version of their Mindbreeze InSpire search product, we typically recommend customers with mostly on-premise content run Mindbreeze on premise. A hybrid architecture is also available where customers can index on-premise content on-premise and cloud content in the cloud, then federate the results at serve time. Reason #1: Even as Mindbreeze expands to index and serve more content in the cloud, they are committed to long-term support for their on-premise search appliance.

Connectors and indexing frameworks

mindbreeze connectorsAn essential requirement for all but a few of our customers is the ability to connect to non-web-crawlable data sources using connectors. This includes SharePoint, file shares, databases, and many others. This also includes Oracle WebCenter Content and PTC Windchill, both specialized content management systems around which Fishbowl has dedicated implementation practices and which are used by many of our customers. To index these systems, Fishbowl developed highly specialized connectors tailored to these sources. We’ve also written GSA connectors for YouTube, Oracle Documents Cloud Service, and Liferay portal. As we evaluated possible GSA replacements, two things were very clear. First, we needed a solution with a strong suite of off-the-shelf connectors, and second, we needed a solid framework for building custom connectors. Mindbreeze has one of the best collections of pre-built connectors on the market, something they have been commended for by both Forrester and Gartner in their respective search vendor reports. Off-the-shelf connectors for Mindbreeze include SharePoint, file shares, LDAP, databases, Salesforce, Confluence, and dozens more. The Mindbreeze Data Integration connector leverages the Talend ETL platform to create integration jobs that extract, transform, and load data from proprietary sources into Mindbreeze without requiring a source-specific connector. Mindbreeze also has a mature SDK available for developing custom connectors to any data source. Fishbowl has already released a connector for Oracle WebCenter Content built on this framework. Last but not least, Mindbreeze supports existing GSA version 4.0 adapters and GSA feeds allowing customers to reuse existing integrations leveraging these frameworks. Reason #2: Mindbreeze has one of the best collections of pre-built connectors on the market plus a mature SDK for custom connector development and support for ingesting GSA feeds.

Strong support for public and secure use cases

Some of our customers use GSA for only public content, but for most customers, at least some of the content is secured. In certain cases, specifically when dealing with SharePoint, Oracle WebCenter, or PTC Windchill, complex security models with layers of inheritance must be enforced. Mindbreeze offers multiple options for implementing secure search. Their internal principal cache and authorization mechanisms allow for fast, document-level authorization checks at serve time using access control lists (ACLs). Mindbreeze also supports ACL inheritance from container objects to further improve performance. For example, if permissions change on a Windchill folder containing 50,000 items, only one item, the folder container, must be reindexed for the new permissions to be reflected within Mindbreeze. This was also possible with GSA, but is not possible with many of the search products on the market because permissions can only be assigned to individual content items. Mindbreeze also supports multiple user authentication mechanisms including Kerberos, Trusted Peer, SAML, and cookie cracking. Existing cookie-based GSA authentication mechanisms can be re-used with Mindbreeze making that transition even easier. Several of our customers use a single GSA to serve both internal (secure) and external (public) use cases. This is also common with Mindbreeze due to their client service architecture which allows configuration of both authentication requirements and data sources for each client service. Reason #3: The Mindbreeze architecture provides one of the most flexible, well-performing secure search implementations we’ve seen, while also allowing segmentation to serve public and secure results on a single deployment.

Tools and APIs for search interface integration

Once data is indexed, it is also necessary that the search technology offer both a built-in search interface and options for integrating search functionality into other websites and applications. Mindbreeze provides a nice combination of pre-built search apps and APIs for creating your own. Customers looking for the easiest path to value can leverage the default Mindbreeze search client which offers a feature rich, mobile friendly, search interface out of the box. You can add your own CSS file for a customized feel with very little development required. Mindbreeze also includes a Search App Designer which provides drag and drop tools for creating use-case specific search apps without coding. The Designer library includes widgets for adding filters, charts, grids, and galleries to various search apps. Mindbreeze also includes an export option which provides all the code needed to embed a search app into a website or application. For customers seeking a more customized integration, the Mindbreeze REST API allows search results to be returned as JSON giving you full control over their presentation. In many cases, customers with custom-built GSA results pages can keep the look of their existing frontend and swap out GSA for Mindbreeze on the backend. In fact, we recently had a customer do exactly this. They went from racking to go-live in less than a month.  Reason #4: Mindbreeze offers a solid combination of UI tools including a no-coding-required UI builder and a REST API for fully customized search applications.

Minimal development efforts or ongoing administration required

Coming from the easy deployment world of GSA, it was important we select a replacement that didn’t require complicated server farms, lengthy IT projects, or significant resource allocation. While we don’t encourage customers to completely forget about their search appliance, the set-it-and-forget-it mindset was prevalent among GSA customers for good reason. Once configured, it just worked. We needed a solution that offered comparably easy setup and maintenance. We didn’t set to out with a requirement to find another physical appliance, but the nature of our requirements made the Mindbreeze search appliance a natural choice. As a productized hardware-software package Mindbreeze setup is comparable to GSA and is considerably quicker than most other search solutions on the market. Even connectors can be run directly on the search appliance eliminating the need for additional application servers. High-availability and disaster-recovery architectures which automatically synchronize data between multiple appliances are also available similar to the mirroring options available with the GSA. And while we have found Mindbreeze to be more configurable than GSA in many ways, customers don’t need to understand indexing pipelines, relevancy algorithms, or machine learning to see great results. Adding connectors, configuring search apps, mapping synonyms, and viewing search analytics can all be done from the web-based Mindbreeze Management Center. Reason #5: The self-contained nature of Mindbreeze allows customers to get search up and running quickly and minimizes ongoing administration activities.

What about relevancy?

You might have noticed a few things conspicuously missing from our list of key requirements. These included strong relevancy, custom synonym dictionaries, search filters, and type-ahead suggestions. Mindbreeze offers all of these features. And so does everyone else. While these features can be critically important to a good search experience, they didn’t end up being important selection criteria because all the leading search tools have them. In many cases, Mindbreeze makes it quicker or easier to implement these features (see Reason #5) but the features themselves are not unique. I should also mention that these capabilities can be huge differentiators when comparing Mindbreeze to search options that come “built in” to content management systems or line of business applications, but those products are not the search tools we were comparing in this evaluation.

Conclusion

In the past seven years we’ve helped numerous customers buy, implement, and maintain their GSAs. Despite the disruption caused by the GSA’s end of life, we’re excited about the possibilities Mindbreeze has to offer. If your requirements are similar to ours, we believe that Mindbreeze offers the quickest, most mature, and smoothest migration path from GSA. As a Mindbreeze partner, we offer both resale and implementation services. If you have questions or would like to know more, please contact us or leave a comment below.

Time running out on your GSA?

Our expert team knows both GSA and Mindbreeze. We’ll help you understand your options and design a migration plan to fit your needs.

Contact Us

The post Replacing the Google Search Appliance: 5 Reasons Fishbowl Chose Mindbreeze appeared first on Fishbowl Solutions.

Categories: Fusion Middleware, Other

Using Adobe InDesign with Oracle Content Experience Cloud

5 Things I learned about Using Adobe Design Products with Oracle Content Experience Cloud

As a designer I am always a little leery when someone tells me they are going to ask me to change my process.  To my great relief moving from my desktop and WebCenter to Content Experience Cloud is not only easy but will make me faster.  Here are the first 5 things I have learned since making the switch.

From the Desktop to the Cloud
Working within the Cloud
Commenting in the Cloud

  1. Drag and Drop!  – Content Experience Cloud makes it easy to drag your exported package folder or image source files from your desktop into the cloud.   You can also save yourself a step and save directly to the cloud.
  2. Generating Content – If you work in an environment where one department generates the images and another might do the writing and a third does the final review and publish CEC will make it easy to collaborate.  Simply place the content from the different departments in the shared folder and BAM instant collaboration.  No more broken links and big file drops using a third party.
  3. Open your Adobe file directly – You don’t need to download the file before opening it up each time and relinking your image files.  Open directly from the cloud and immediately start working.
  4. Security – As previously mentioned you don’t need to use one of those third party’s to transfer your files.  You also can control who has access to the shared content at each step.  For example you don’t need to include all departments in the design phase.  Once it is ready for sharing the exported document can be saved into a production folder for publication. This eliminates the risk that a partially finished product would be published by mistake.
  5.  Shorten the Review Cycle – Shorten the review cycle by directing all stakeholders to the correct folder.  This will reduced the need to email each version to everyone each time.  Comments can be made directly within the folder.

Having the ability to work collaboratively within a cloud application is a big advantage for graphic designers.  The files we tend to use are usually large and sending them back and forth is a consistent challenge.  Without a cloud application teams are forced to export and package the project at each step and send to each other using a dropbox or similar application.  The next team member has to download the content to their computer make any edits, and then send it on to the next step.  Watch as I demonstrate how your team can use Oracles Content Experience Cloud with your Adobe software to cut out steps and make collaboration a breeze.

The post Using Adobe InDesign with Oracle Content Experience Cloud appeared first on Fishbowl Solutions.

Categories: Fusion Middleware, Other

Pivotal Cloud Foundry 1.12 on Google Cloud Platform with VM labels

Pas Apicella - Wed, 2017-10-04 23:20
Once PCF is installed on GCP it's worth noting that viewing the "Compute Engine" labels gives you as indication of what VM each CF service is associated with. The screen shots below show's this.



Categories: Fusion Middleware

The Fishbowl Team Wins the 2017 Modern CX Hackathon at Oracle Openworld

The Fishbowl hackathon team headed out to San Francisco on Friday September 29th with Chatbots on the brain.  Their goal was to develop a solution that would improve sales productivity and margin as well as to improve executive insights and information access by allowing 24/7 conversational access to a sales pipeline.  And so the sales assistant chatbot was born.

The team spent the following 2 days writing code, utilizing Oracle’s cloud based services, and preparing their presentation for the judges.

The solution was dubbed SalesBot – The Intelligent Chatbot that adds optimization and Machine Learning to data access.  SalesBot would enable staff to:

Prepare for Sales Calls

 

  • View Customer Order history
  • List Past Work engagements
  • See Purchased Products
Manage Day to Day workloads
  • Create service Requests
  • Update and query contacts
  • View support tickets
Query Pricing Datasets
  • Quote estimates based on historical pricing data
  • Optimize margins
  • Estimate time to failure of parts

Congratulations to our team of Andy Weaver, Danny LeSage, John Sim, Matt Hornung,  and Tom Johnson.  We will be applying what we learned by expanding our already existing chatbot Atlas.  For more information or to see a demo contact info@fishbowlsolutions.com 

 

The post The Fishbowl Team Wins the 2017 Modern CX Hackathon at Oracle Openworld appeared first on Fishbowl Solutions.

Categories: Fusion Middleware, Other

PTC Windchill Success Story: Measuring so they can Manage

AN EQUIPMENT MANUFACTURER LEVERAGES FISHBOWL’S LINKTUNER TO MEASURE WINDCHILL PERFORMANCE BEFORE, DURING AND AFTER A GLOBAL IMPLEMENTATION

A large global customer planned to consolidate their many PTC data management systems into one global Windchill system. End user adoption was going to be a critical factor in a successful deployment and the Creo+Windchill system performance would be a key factor to facilitate end user adoption.  The Windchill team wanted a simple straightforward repeatable method to measure the Creo+Windchill performance that would allow them to:

  • Know what the incumbent system performance was at the time.
  • Measure and performance tune the new system during pre-production activity
  • Monitor the performance on “Day 1”
  • Systematically benchmark and report system performance into the future

As each division was going through migration and Go Live, the customer would run benchmarks on their existing Creo+Windchill environment, run benchmarks on the future systems in the test/QA environments, and then they would run benchmarks during production Go Live.  They also run ongoing scheduled benchmark monitoring to insure system performance does not degrade.  Fishbowl’s LinkTuner gave them a simple process to repeat the exact same benchmark test again and again without loading cache and diminishing the test results.  It also performed the benchmarks on local Creo workstations so it perfectly emulated what the end user does every day (it doesn’t “fake” transactions at the server level).

As each division migrated and went live on the new global Windchill system, the team was confident the users would have a good experience on “Day 1”, and after all you only have one chance at making a good first impression.

Are you looking to go global or maybe go into the cloud?  Are you curious about what the end user performance experience will be like… and I mean really be like?

Get ahead of potential performance issues by testing and benchmarking performance with actual user processes and data with Fishbowl’s LinkTuner for PTC Windchill. Read below for a customer example of how leveraging LinkTuner enabled them to confidently roll out PTC Windchill to their worldwide locations.

RESULTS
  • The customer successfully deployed a global system that outperformed their expectations and high user acceptance scores
  • They consolidated systems for better efficiencies at many levels and processes.
  • LinkTuner regularly benchmarks and measures the Creo – Windchill performance standard from each global location, allowing the client to be proactive with their system administration

 

Contact  Rick Passolt for more information on LinkTuner

The post PTC Windchill Success Story: Measuring so they can Manage appeared first on Fishbowl Solutions.

Categories: Fusion Middleware, Other

Drive down WebCenter Content Storage Costs with Oracle Hierarchical Storage Manager (Oracle HSM) and Oracle Cloud Archive

Fishbowl’s worked with Oracle WebCenter Content customers that have stored as low as 7,000 documents in their content server and as high as 20 million. We are currently working with the customer that has the 20 million documents in their repository to discuss their options of upgrading to Oracle WebCenter Content 12c. The options being discussed include maintaining their on premise instances, or moving their instances to the Oracle Cloud leveraging Oracle Bare Metal.

As part of these cloud consulting engagements, we seek to understand their content management use cases and the content they are currently storing and managing. This customer is a large manufacturer. They store a variety of documents related to their industry including CAD drawings, but they also store business documents like invoices. The invoices are only accessed, on average, once per year but need to be retained for 7 years. They are stored on the same SAN disk array as the CAD drawings and other content, which are accessed more frequently and need to be presented to users quickly. This means they are paying the same per item storage cost to store invoices, CAD drawings, and other content.

A more efficient and economical storage strategy could be utilized with Oracle’s HSM solution. Oracle HSM software manages data between storage tiers to enable organizations to utilize the acquisition and operational cost differences between flash, disk, tape, devices, and the cloud. With Oracle HSM, large WCC environments like our 20 million item customer could store various content types automatically and transparently on the most cost effective storage medium based on retention policies, retrieval frequency and speed necessary. Such capabilities would better align the storage costs with organizational priorities as well as ease management overhead.

HSM could also alleviate any file storage cost concern of getting content off employee hard drives, file shares or other repositories into Oracle WebCenter Content. Content such as photographs used in a company branding or marketing campaign could be checked into WebCenter for long-term archival and directed to an economical storage medium via HSM. Not only does this ensure that high-value, expensive assets like professional photographs can be searched and found easily, it also enables them to be repurposed at a later time – alleviating the overall storage cost concern.

I’ve included below some more resources on Oracle HSM. The Oracle HSM team has even put together a storage cost calculator. Oracle HSM can also be used for video storage. How much storage costs could HSM save your organization?

http://www.oracle.com/us/media/calculator/tieredstorage/index.html

 

The post Drive down WebCenter Content Storage Costs with Oracle Hierarchical Storage Manager (Oracle HSM) and Oracle Cloud Archive appeared first on Fishbowl Solutions.

Categories: Fusion Middleware, Other

Oracle WebCenter Enterprise Capture Overview

Oracle WebCenter Enterprise Capture can help resolve many frustrations companies experience. Questionable data integrity, lengthy check-in processes, wasting of resources (time, paper, etc.) are common day-to-day frustrations in many companies.  Oracle WebCenter Enterprise Capture strives to remove some of this headache and much more, all packaged in a user-friendly, web-based interface. I’ve helped several customers work through the process from design to go-live, and hope to share my experience on document capturing solutions.

WebCenter Enterprise Capture is a document capturing tool that includes an initial review for the documents captured by the system. Images can be captured in four different ways: manual upload, scanner, shared directory, or email. All documents can then be automatically released to a commit process or enter a review state. When a document enters the review state, the user can go into the system and view the item and/or define metadata. Also, multiple metadata profiles can be configured so multiple document types can be scanned or uploaded.

Once a document has been reviewed and released this will move to a defined commit processor. There are four different commit profiles. These four commit profiles are WebCenter Content, WebCenter Content Imaging, Oracle Document Cloud Service, or Text File. The defined commit profiles allow content to be easily linked to Oracle products. This helps alleviate issues associated with creating a custom commit driver that will have to be maintained for custom solutions.

Government Use Case

A scenario that a government company may run into is that they are drowning in paper. They will have file rooms filled floor to ceiling with paper documents because of retention policy. Storing large amount of paper documents introduces issues for space as well as time-to-access. Many companies will agree that rooms that are storing documents could have a better use, and that those who spend time digging through those rooms to find those document would likely prefer to be anywhere else.

WebCenter Enterprise Capture can be a great solution for this issue. This allows incoming documents to be stored electronically, removing the necessity of storing a physical copy. In this scenario, WebCenter Enterprise Capture is used to capture all incoming documents. Documents can then be automatically checked into Oracle WebCenter Content, or another content management system. WebCenter Content server can be configured to meet retention policy standards. Also, this solution provides an easy search experience, so users can quickly search for and locate documents.  What once was a frustrating, time-consuming, and potentially sweat-inducing process is now done in the click of a button. 

Now with this solution comes another major benefit. When documents are stored as paper, companies run the risk of disaster recovery. Paper documents are vulnerable to damage in many ways. When documents are stored electronically they can be recovered or restored from backups to minimize total loss.

Construction Company Use Case

Companies may also find frustration with a complicated process to check-in documents. Every company is always looking for the easiest way to get data into a content server. Along with the complexity to get content into the server comes an issue of associating the metadata to the document. WebCenter Enterprise Capture can help resolve this frustration by taking advantage of database lookups and an automated check-in process.

In this scenario, all documents are associated to a unique reference number. This unique reference number is stored in a database that has all associated metadata values for that document. In this solution, an email profile is configured for WebCenter Enterprise Capture to watch for documents entering the system. The subject line will always contain the unique reference number. Once a document is pulled into WebCenter Enterprise Capture the database lookup is triggered to populate all metadata. If there are no errors, this document is released to the content server and checked-in.

This provides two major benefits. The first is that metadata will remain consistent because users do not have to manually type in all the metadata. The other is that by simply sending an email the document is checked in. This reduces the amount of time spent on checking in documents.  Moral of the story: the metadata is now in alignment with the database, the document will be easier to find because of increased data integrity, and the users spent less time getting the document stored correctly. Win-win-win.

Advantages Over Third Party Applications

The first major benefit to using WebCenter Enterprise Capture is that the system is in an upgrade-able state. When using Third Party scanning applications, there is always a high risk of not being able to patch or upgrade other Oracle software because these applications have not been certified or integrated with the new application version. This can also increase the complexity of your solutions and make upgrades grueling or–potentially–fail completely.

The second major benefit is being able to take advantage of Enterprise Capture commit profiles. These profiles are designed in a way to map all data within an interface. In a third-party application, this will need to be developed to be able to map all data. This will lead to customizations which take more effort/time to develop and maintain.

Overall, the time, effort, development, and customization for a third-party application is not as effective as WebCenter Enterprise Capture. WebCenter Enterprise Capture provides more reliability than third party applications.

Tips

When configuring WebCenter Enterprise Capture, it is best practice to think about using database lookups and choice lists. This will provide two benefits. The first being that users will be able to reduce the time to populate metadata fields. The second being that metadata will have greater consistency.

The email upload option in WebCenter Enterprise Capture is an option commonly used when data is being sent to a company externally. This currently only supports IMAP email configuration. If POP3 email configuration is being used, WebCenter Enterprise Capture will not be able to be configured with the email upload. This is an issue that Fishbowl Solutions has run into in the past. If it is not possible to change the email protocol, one option that can be configured is the directory upload. This will allow users to manually drop files off in a filesystem location, or if this was from a multifunctional scanner, a profile can be configured to drop off to the shared watch directory. These files are then ready for Capture.

Conclusion

Overall, WebCenter Enterprise Capture is a document capturing tool that can resolve business problems or help alleviate struggles with current configurations. This tool is very flexible on how documents can be captured and committed. By using an Oracle product, there is not a fear with patching or upgrading software compared to using third-party applications. When trying to resolve problems with document capture, metadata consistency, and easier check-in processes, this product should be considered as a viable solution.

WebCenter Enterprise Capture Overview

Oracle WebCenter Enterprise Capture can help resolve many frustrations companies are experiencing such as, removing unwanted paper, easier check-in process, data integrity, and many more. In my experience, I have found that WebCenter Enterprise Captures interface to be user friendly.

WebCenter Enterprise Capture is a document capturing tool that includes an initial review for the documents being captured. Images can be captured in four different ways manual upload, scanner, shared directory, or email. All documents then can be automatically released to a commit process or enter a review state. When a user is in the review state the document can be viewed and metadata can be defined. Also, Multiple metadata profiles can be configured so multiple document types can be scanned or uploaded.

Once a document has been reviewed and released this will move to a defined commit processor. There are four different commit profiles. These four commit profiles are WebCenter Content, WebCenter Content Imaging, Oracle Document Cloud Service, or Text File. The defined commit profiles allow content to be easily linked to Oracle Products. This helps alleviate issues associated with creating a custom commit driver that will have to be maintained in custom solutions.

Government Use Case

A scenario that a Government company may run into is that they are drowning in paper. They will have file rooms filled floor to ceiling with paper documents because of retention policy. Storing large amount of paper documents introduces issues for space. Many companies will agree that rooms that are storing documents could have a better use.

WebCenter Enterprise Capture can be a great solution for this issue. This allows incoming documents to be stored electronically. This prevents the issue of having to store documents as paper. In this scenario WebCenter Enterprise Capture is used to capture all incoming documents. This then will check items directly into the Content server for storage. WebCenter Content server can be configured to meet retention policy standards. Also, this solution will provide a benefit that will allows users to use search capabilities to locate documents. This will help alleviate time searching in a file rooms for documents and allow the users to just click a button to search.

Now with this solution comes another major benefit. When documents are stored as paper companies run the risk of disaster recovery. Paper documents are vulnerable to damage in many ways. When documents are stored electronically they can be recovered or restored from backups to minimize total loss.

Construction Company Use Case

Companies can run into a frustration with a complicated process to check in documents to the content server. Every company is always looking for the easiest way to get data into a content server. Along with the complexity to get content into the server comes an issue of associating the metadata to the document. WebCenter Enterprise Capture can help resolve this frustration by taking advantage of database lookups and an automated check-in process.

In this scenario, all documents are associated to a unique reference number. This unique reference number is stored in a database that has all associated metadata values for that document. In this solution, an email profile was configured for WebCenter Enterprise Capture to watch for documents entering the system. The subject line will always contain the unique reference number. Once a document is pulled into WebCenter Enterprise Capture the database lookup is triggered to populate all data. If there are no errors this document is released to the content server and check-in.

This provides two major benefits. The first is that data will remain very consistent because users do not have to manually type in all the metadata. The other is that simply by sending an email the document will be checked in. This reduces the amount of time spent on checking documents in. So, users reduce the time to check an item in and increases the ease-ability to find documents in the content server.

Advantages Over Third Party Applications

The first major benefit to using WebCenter Enterprise Capture is being in an upgradable state. When using Third Party scanning applications there is always a high risk of not being able to patch or upgrade other Oracle software because these applications have not been certified or integrated with the new application version. This can also increase the complexity of your solutions and make upgrades grueling and ultimately not work at all.

The second major benefit is being able to take advantage of Enterprise Capture commit profiles. These profiles are designed in a way to map all data in an interface. In a third-party application, this will need to be developed to be able to map all data. This will lead to customizations and more effort/time to develop.

Overall the time effort, development, and customization for a third-party application is not as effective as WebCenter Enterprise Capture. WebCenter Enterprise Capture provides more reliability than third party applications.

Tips

When configuring WebCenter Enterprise Capture it is always best practices to think about using Database Lookups and Choice Lists. This will provide two benefits. The first being the users will be able to reduce the time to populate metadata fields and the second being that metadata in a stored state will have improved consistency of data.

The email upload option in WebCenter Enterprise Capture is an option commonly used when data is being sent to a company externally. This currently only supports IMAP email configuration. If POP3 email configuration is being used WebCenter Enterprise Capture will not be able to be configured with the email upload. This is an issue the Fishbowl Solutions has ran into in the past. If it is not possible to change the Email protocol one option that can be configured to be used is the directory upload. This will allow users to manually drop those files off or if this was from a multifunctional scanner a profile can be configured to drop off to the shared watch directory for upload.

Conclusion

Overall, WebCenter Enterprise Capture is a document capturing tool that can resolve business problems or help alleviate struggles with current configurations. This tool is very flexible on how documents can be captured and committed. By using an Oracle product there is not a fear with patching or upgrading software compared to using third-party applications. When trying to resolve problems with document capture, metadata consistency, and easier check-in processes this product should be considered as a possible solution.

The post Oracle WebCenter Enterprise Capture Overview appeared first on Fishbowl Solutions.

Categories: Fusion Middleware, Other

Accelerated Mobile App Development with Oracle Mobile Cloud Service – Part 2

Part 2: Mobile App Development with MCS

In Part 1, we explored using Oracle’s Mobile Cloud Service as tool to provide the backend services needed to retrieve data from an Oracle EBS Pricing and Availability form. With our mobile backend and custom API’s created, the actual app development can now begin!

 

Creating a Native App

For the next step of my POC, I’ll be creating a simple iOS application that allows me to lookup a Pricing and Availability item and view its properties and warehouse locations. Before firing up Xcode, I need to click the “SDK Downloads” from the MCS Applications page and download the iOS SDK.

 

As I mentioned earlier, the SDK will allow me to make MCS API calls with one or two lines of code. In order to take advantage of it I need to add the static libraries and header files from the downloaded SDK to my project in Xcode and properly link them.

 

The SDK download also includes an “OMC.plist” file that will need to be added to my project. The OMC.plist will hold the settings that are needed to connect to our Pricing and Availability mobile backend. The Settings tab of the Pricing and Availability backend in MCS has several of the items we need. Since we’re using basic authentication, we need to get the Mobile Backend ID, Anonymous Key, and the Base URL of our MCS environment.

 

We’ll also need the application key we were provided earlier after creating our mobile client. After adding these items to the OCM.plist, the initial MCS setup of our project is complete.

 

When a user runs my app, the first thing they will need to do is login. I put together a basic login screen with username and password fields.

 

When a user taps the Login button I simply need to authenticate against my mobile backend with these three lines of code:

 

If no error is returned then the authentication is successful and I can dismiss my login screen. My user will then be presented with my search screen which simply contains a table view with a search bar at the top.

This is the point where we utilize the Pricing and Availability custom API that we previously configured. When a user enters a Pricing and Availability Item’s ID and taps the search button I’ll need to make a GET call to the /pricingandavailabilityitem/{id} endpoint in order to return the matching item. Once again, this can be handled with a few lines of code:

 

The response is then parsed and a result row is added to my table view.

 

Tapping on the result row will bring the user to my item details screen where the Pricing and Availability item’s properties are displayed. I also want to display the warehouse locations for my item on the details screen so I make a similar second call to the pricingandavailabilityitem/{id}/pricingandavailabilityitemlocation endpoint and populate the results in another table view.

 

At this point I have successfully achieved the goal of displaying EBS form information on a mobile device! As you can see, the amount of effort required to authenticate and retrieve the data was minimal, whereas without MCS those tasks would have consumed a large percentage of my time.

 

Creating a MAX App

While the iOS SDK may have made my app development seem fairly effortless, MCS actually provides an easier way for me to achieve my goal. On the MCS Applications page, there is a Mobile Apps section that takes you to the Mobile Application Accelerator (MAX) application.

 

With the MAX application, it is possible to quickly put together a mobile app with absolutely no coding involved. With its drag-and-drop web interface, non-technical business users can easily login and build their own mobile apps in minutes.

Let’s take a look at building the same POC as a MAX application. Clicking the “New Application” button will take you through a simple app creation wizard.

 

After providing your app name and choosing your screen layout you will be presented with a blank home screen where you can drag and drop UI elements onto various content areas. Just like the native app, my MAX app will first present the user with a search screen that will display Pricing and Availability Item search results. To handle this, I’ll be adding a list element onto my home screen and enabling its search option which will automatically add a search field to the top of it.

 

Next we’ll need to indicate what data will be populated in our list element. Clicking “Add Data” will allow you to map any UI element to a data source. Choosing a data source is as simple as selecting the Pricing and Availability Item resource from our custom API. Our MAX app will automatically use the appropriate API calls to retrieve our data. We can then drag and drop properties from our Pricing and Availability resource onto each of the four available search result row labels to be displayed. I chose to use the Item Description, Item Type, Unit Pricing, and Pricing currency fields.

 

Since our Pricing and Availability Item API call requires an ID parameter we indicate that the list element’s search field will be the source.

 

Our search page now has what it needs to lookup a Pricing and Availability Item.

 

In order to see the details of a Pricing and Availability item, we will need to provide an action on the list element’s action tab. After clicking the Actions tab, another drag and drop interface allows us to indicate that when a list item is tapped, we will be taken to a new Pricing and Availability item detail screen.

 

In addition to displaying the Pricing and Availability item properties, I also want the new Pricing Item Detail page to display the warehouse locations. To handle this, when creating my details screen I choose the “Screen with Top Tabs and Summary” page template and specify three separate tabs: Overview, Quantities, and Warehouses. For each of the tabs, I follow the same process of dragging UI elements onto the content areas and mapping a data source to them. My Overview tab gets a form UI element that displays my Pricing and Availability Item’s properties. The Warehouses tab gets a list element that displays a list of all warehouse locations for the pricing item.

For the Quantities tab, I wanted to demonstrate a nice feature of MCS with the use of a bar chart to easily view the item quantities at each warehouse. I simply drag a bar chart UI element onto the tab and map the data source to my Pricing and Availability Item Locations resource with the warehouses along the X-Axis and the quantities along the Y-axis.

 

With our app complete, testing it out is as easy as hitting the test button. An iOS or Android simulator will run right in your browser.

 

Testing on or publishing to a mobile device isn’t that much more complicated. Once you install Oracle’s Mobile Application Accelerator client app on your device, you can easily add your MAX apps as “apps within an app” via a QR code. Avoiding time consuming app publishing processes means business users can get the tools they need with a few clicks.

 

Compared to native app development, the MAX app was created in a fraction of the time, and as you can see, no coding was involved. As easy as it was to build my POC, MAX has its limitations. Screens can be easily setup to search, view, add, edit, and delete business objects, but beyond that, you might need to get creative. Developing the right custom API for my Pricing and Availability app could make it possible to submit an item purchase, but the overall user experience will be limited. For more flexibility, native and hybrid apps will still have their place.

 

Conclusion

Overall, my POC just scratches the surface of what MCS can do. With the platform API’s providing database & content storage capabilities, push notifications, offline syncing, and built-in analytics, most of the things mobile apps require are readily available without having to worry about backend hardware and software. Having the ability quickly to assemble these platform API calls into custom API’s that can be reused across many mobile backends means that MCS has the potential to easily bring many aspects of a business to mobile devices.

By utilizing the MCS SDK’s, many of the common tasks of mobile app development that had previously been significant technical hurdles now become minor steps handled with a few lines of code. Considering the amount of effort that some of these common tasks required in my previous mobile projects, I believe MCS could have cut my development time in half. Realistically, organizations could have a mobile app in production use within a matter of hours. Being able to realize such quick time to value with a mobile app is definitely a key value proposition of MCS, so if that is important to your organization I recommend you give MCS a try.

The post Accelerated Mobile App Development with Oracle Mobile Cloud Service – Part 2 appeared first on Fishbowl Solutions.

Categories: Fusion Middleware, Other

Pages

Subscribe to Oracle FAQ aggregator - Fusion Middleware