Remove all occurrences and references of binary installations

modules/ROOT/pages/architecture/architecture.adoc

@@ -117,7 +117,7 @@ Every Infinite Scale service uses {ocis-pkg-url}[ocis-pkg], which implements the
 
 ==== Go-Micro
 
-While the {go-micro-url}[go-micro] framework provides abstractions as well as implementations for the different components in a microservice architecture, it uses a more developer-focused runtime philosophy: It is used to download services from a repo, compile them on the fly and start them as individual processes. For Infinite Scale we decided to use a more admin-friendly runtime: You can download a single binary and start the contained Infinite Scale services with a single command: `ocis server`. This also makes packaging easier.
+While the {go-micro-url}[go-micro] framework provides abstractions as well as implementations for the different components in a microservice architecture, it uses a more developer-focused runtime philosophy: It is used to download services from a repo, compile them on the fly and start them as individual processes. For Infinite Scale we decided to use a more admin-friendly runtime: You can download a container that internally uses a single binary, which starts the contained Infinite Scale services with a single command: `ocis server`. This also makes packaging easier.
 
 ==== REVA and CS3
 

modules/ROOT/pages/conf-examples/search/configure-search.adoc

@@ -10,7 +10,7 @@
 
 {description} Using search is a good way to find documents based on various criteria. The search service will return results for documents the searcher is eligible to access. Read the description of the xref:{s-path}/search.adoc[search service] for more details.
 
-You can use basic search functionality without any configuration as it is preconfigured when using the default binary or container/orchestration deployment.
+You can use basic search functionality without any configuration as it is preconfigured when using the default container deployment.
 
 == Index Data
 
@@ -96,17 +96,6 @@ image::conf-examples/search/tika-welcome-screen.png[Tika welcome screen, width=4
 
 you can use the container. Finally, you can keep the image when planning to use a container based setup but remove the test container with `docker stop <ID>` and `docker rm <ID>` where ID is the container ID of Tika.
 
-===== Manual Based
-
-If using the container does not work in your environment, you need to use the server installation of Tika which requires at least Java version 8 installed, check with `java -version` and install java if required. After downloading the https://tika.apache.org/download.html[Tika server .jar] file, you can start the server with:
-
-[source,bash,subs="attributes+"]
-----
-java -jar tika-server-standard-{tika-version}.jar
-----
-
-It is then accessible via `\http://your-server:9998`. Check that the Tika server is automatically started like when using systemd - which is not covered here though you can take xref:depl-examples/small-scale.adoc#setup-the-systemd-service[Setup the systemd Service] from the _Small-Scale Deployment with systemd_ as setup reference.
-
 ==== Configure Search using the Tika Extractor
 
 As prerequisite, Tika needs to be accessible via `\http://your-server:9998` either using the manual installation or via docker. You can decide to let Tika run on the same or a separate server from where the search service runs. The following configuration assumes that all Infinite Scale services including the search service and Tika run on the same hardware.